Verifile

● Active

io.github.neubuot/verifile

Proof of existence for files and texts: anchor a SHA-256 on the Doichain and verify it later

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "verifile": {
      "url": "https://verifile.it/mcp"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http verifile https://verifile.it/mcp
VS Code
code --add-mcp '{"name":"verifile","type":"http","url":"https://verifile.it/mcp"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Other
Version
1.6.0
Registry
active
Published
11/18/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Looks healthy: Verifile is maintained, open source, hosted endpoint answering without a key.

Maintained
Active
Last commit 4 days ago (Nov 18, 2026), 4 open issues.
Official registry
Active
Published as io.github.neubuot/verifile in the official MCP registry, version 1.6.0.
Source
Open source, MIT
Public repository under the MIT licence, 0 stars, 0 forks.
Runs
Hosted by the publisher
Your client talks to verifile.it: prompts and tool arguments leave your machine for that host.
Credentials
None needed to connect
The hosted endpoint completed the Serverdex initialize + tools/list handshake with no key (checked Nov 22, 2026); individual tools may still ask for one.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 00:07 UTCStatus history & uptime →
● Working684 msprotocol 2025-06-18v1.6.0promptsresourcestools

The endpoint answered the MCP handshake as "Verifile" and listed 4 tools. Answering since Nov 18, 2026.

Context cost ≈ 1.2k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 4 tools.

Tools (4)

  • hash_text1 param

    Compute the SHA-256 digest of a short text (UTF-8) on the server, for example to anchor a statement or a message with anchor_proof. The text is sent to the server but not stored or logged. For files and for confidential texts compute the hash locally instead (sha256sum file, or Get-FileHash -Algorithm SHA256).

    Show parameters
    • textstringrequiredText to hash, encoded as UTF-8 exactly as given (whitespace and line breaks count), at most 40,000 characters
  • check_proof1 param

    Check whether a SHA-256 hash is anchored on the Doichain (name poe/<sha256>) and since when. Returns status (confirmed, pending, expired, unknown) and at the top level block height, block time, transaction and links of the first anchoring, which is the proof time. If the name was updated later or registered again after it expired (possibly by someone else), that registration is reported separately in latest_registration with its own holder and record, which are not part of the original proof. A confirmed or expired proof shows that a document with exactly this hash existed no later than the block time, not who submitted it.

    Show parameters
    • sha256stringrequiredSHA-256 digest of the document, 64 hexadecimal characters (a sha256: or 0x prefix is accepted)
  • anchor_proof4 params

    Anchor a SHA-256 hash on the Doichain as a tamper-evident timestamp (proof of existence, name poe/<sha256>). Free for users, limited per IP address and day (see get_anchoring_quota). Confirms with the next block, usually within 10 minutes, then check_proof returns block height and time. If the hash is already anchored or pending, the existing proof is returned instead of creating a second one. If an earlier proof of the hash has expired, it stays valid and is returned with expired true. Nothing is registered unless reanchor_expired is true. Only the hash and the optional note and file name become public, never the document itself. The operator of this server pays for the name and holds it. The proof shows that a document with this hash existed no later than the block time, not who submitted it.

    Show parameters
    • sha256stringrequiredSHA-256 digest of the document, 64 hexadecimal characters, computed from the actual file. Never guess it and never send the document
    • noteOptional public note (max 160 characters), stored on the blockchain forever. No personal data, no secrets
    • filenameOptional public file name (max 80 characters), stored forever. Only set it when the user explicitly wants the name public
    • reanchor_expiredbooleanOnly set to true when an earlier proof of this hash has expired and the user explicitly wants an additional, later registration. The original anchoring stays th
  • get_anchoring_quota

    How many proofs can still be anchored today (UTC day) within the free public quota for the caller's IP address. Hosted chat apps connect from their own servers, so their users share one quota. Callers that send their own API key in the X-API-Key header have no quota.

Checked by Serverdex with a plain initialize + tools/list call to verifile.it/mcp, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 18, 2026
Stars
0
Forks
0
Last push
Nov 18, 2026
License
MIT

Pythonai-agentsblockchainclaudedoichainllm-toolsmcpmcp-servermodel-context-protocolnamecoinnotaryproof-of-existencepythonstreamable-httptimestamping

From the README

Doichain MCP Server Tamper-evident timestamps for your AI agent. Prove that a document already existed at a given time: anchor its hash on the Doichain (proof of existence), verify proofs and read names, blocks and addresses. One URL, no account, no API key, no installation. Quick start · Tools · How it works · Limits · Security · Tool reference · Self-hosting · Deutsch Endpoint: https://doi-api.sendlabs.de/mcp · Streamable HTTP · stateless · no authentication required The Doichain is a public blockchain with a built-in name-value store (a Namecoin descendant, merge-mined with Bitcoin). This server makes it usable for any agent that speaks the Model Context Protocol: Claude, ChatGPT, Cursor, VS Code Copilot and many more. Ask your agent in plain language, it picks the right tool itself: "Anchor the hash of offer-2026.pdf on the Doichain." "Did this contract already exist before October 1?" "Are d/example or id/alice about to expire?" "How is the Doichain doing right now?" Opening the endpoint in a browser shows the landing page with setup instructions. Quick start Claude Code Check with claude mcp list. Without --scope user the server only applies to the current project. Claude (web and desktop) 1. Open Customize → Connectors and click +. 2. Choose Add custom connector, name it Doichain and paste https://doi-api.sendlabs.de/mcp. 3. In a chat, enable it via + → Connectors. Custom connectors also work on the free plan (one connector).…

Read the full README on GitHub →

Remotes

  • streamable-httphttps://verifile.it/mcp

The most-starred Other servers in the index, with their live-check result.

ServerStarsLast pushLive check
Labelhead Artist Momentum114,594Nov 2026Working
World Monitor91,002Nov 2026Needs sign-in
Tldraw51,470Nov 2026Working
OpenSEO28,515Nov 2026Needs sign-in
Windows MCP11,833Nov 2026Local / not checked

Verifile: questions people ask

Is Verifile a remote or a local MCP server?
According to its entry in the official MCP registry, Verifile ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does Verifile need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 22, 2026. Individual tools may still ask for a key when called.
Is Verifile safe to use?
Looks healthy: Verifile is maintained, open source, hosted endpoint answering without a key. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: Hosted by the publisher; credentials: None needed to connect. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is Verifile still maintained?
Active: the repository's last commit 4 days ago. Last push Nov 18, 2026, 0 GitHub stars, MIT licence. Read from GitHub on Nov 18, 2026.
What tools does Verifile expose?
4 tools as listed by the server itself during the live check, including hash_text, check_proof, anchor_proof, get_anchoring_quota. The full list with parameters is in the Live check section above.
How do I add Verifile to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
  1. DoichainProof of existence, names and chain data of the Doichain blockchain for AI agents
Browse all Other →

Add the badge to your site

Show visitors that Verifile is listed here — it’s also the link we check for a free listing.

Verifile — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-neubuot-verifile?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Verifile — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Verifile — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-neubuot-verifile?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/io-github-neubuot-verifile) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/io-github-neubuot-verifile) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/io-github-neubuot-verifile)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/io-github-neubuot-verifile"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-neubuot-verifile"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-neubuot-verifile"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).