A small filesystem MCP server used to demonstrate Proofmark attestation.
MCPpedia last refreshed this data
io.github.SamuelDharshi/proofmark-demo-server is an MCP server that a small filesystem MCP server used to demonstrate Proofmark attestation. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 58/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"io-github-samueldharshi-proofmark-demo-server": {
"args": [
"-y",
"proofmark-demo-server"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A small filesystem MCP server used to demonstrate Proofmark attestation.
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
npx -y 'proofmark-demo-server' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked proofmark-demo-server against OSV.dev.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in other
deja-vu: local memory over the session histories of forty-three coding agents.
MCP WordPress Remote proxy server
专门为 agent 打造的 agent 搜索工具,具备多语言搜索能力,覆盖中文/英文/学术/代码/购物/金融/新闻/百科。
Searchable football data provider documentation for AI coding agents. Like Context7 for football data.
MCP Security Weekly
Get CVE alerts and security updates for io.github.SamuelDharshi/proofmark-demo-server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
The trust gate between AI agents and the MCP servers they connect to.
x402 payments and audit on Hedera · identity on ENSv2 · uniqueness and spend authority from World
Live app · Check any server · On-chain console · Testing report · Page-by-page walkthrough · Sponsor feedback
An MCP server is not a library. When an agent connects to one, the server is handed the agent's shell, filesystem, credentials and payment rails. Thousands of MCP servers already exist, installed with one line such as npx -y some-server. Most of them come from people the user has never heard of.
Today the best assurance available is a signature showing that some GitHub account built the code. That leaves four gaps:
| Gap | What goes wrong |
|---|---|
| Tools change after approval | A server that was harmless yesterday quietly adds a read_env tool today. Nothing re-checks it. |
| Accounts are cheap | One person can run fifty GitHub accounts. A signature binds code to an account, not to anyone accountable. |
| Nothing revokes | If a maintainer's key leaks on Tuesday, every agent already connected keeps trusting it. |
| Nobody pays for checking | Every verification proposal assumes someone checks for free, forever. In practice nobody does. |
Before an agent connects to an MCP server, Proofmark:
A server is green only when its maintainer is backed by all three layers:
┌────────────────────┐ ┌──────────────────────┐ ┌──────────────────────┐
│ UNIQUE │ │ DOMAIN-VERIFIED │ │ BONDED │
│ World ID │ + │ GitHub gist or │ + │ 50 HBAR in a 2-of-2 │
│ one person, │ │ domain proof of the │ │ Hedera account, │
│ one claim │ │ registry namespace │ │ forfeited on malice │
└────────────────────┘ └──────────────────────┘ └──────────────────────┘
stops sockpuppets ties name to owner puts money at stake
World alone is deliberately not trusted for identity. A credential can be shared, so the namespace proof and the bond exist to cover that.
It is **not a code scanner