Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
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.
SHA-256 digest of the document, 64 hexadecimal characters, computed from the actual file. Never guess it and never send the document
Optional public note (max 160 characters), stored on the blockchain forever. No personal data, no secrets
Optional public file name (max 80 characters), stored forever. Only set it when the user explicitly wants the name public
Only 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 the proof time. The new registration adds a later timestamp and replaces the public note and holder of the name. Default false
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http verifile https://verifile.it/mcp
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.
| Argument | Type | Description |
|---|---|---|
| note | any | Optional public note (max 160 characters), stored on the blockchain forever. No personal data, no secrets |
| sha256* | string | SHA-256 digest of the document, 64 hexadecimal characters, computed from the actual file. Never guess it and never send the document |
| filename | any | Optional public file name (max 80 characters), stored forever. Only set it when the user explicitly wants the name public |
| reanchor_expired | boolean | Only 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 the proof time. The new registration adds a later timestamp and replaces the public note and holder of the name. Default false |
{
"type": "object",
"title": "anchor_proofArguments",
"required": [
"sha256"
],
"properties": {
"note": {
"anyOf": [
{
"type": "string",
"maxLength": 160
},
{
"type": "null"
}
],
"title": "Note",
"default": null,
"description": "Optional public note (max 160 characters), stored on the blockchain forever. No personal data, no secrets"
},
"sha256": {
"type": "string",
"title": "Sha256",
"maxLength": 100,
"description": "SHA-256 digest of the document, 64 hexadecimal characters, computed from the actual file. Never guess it and never send the document"
},
"filename": {
"anyOf": [
{
"type": "string",
"maxLength": 80
},
{
"type": "null"
}
],
"title": "Filename",
"default": null,
"description": "Optional public file name (max 80 characters), stored forever. Only set it when the user explicitly wants the name public"
},
"reanchor_expired": {
"type": "boolean",
"title": "Reanchor Expired",
"default": false,
"description": "Only 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 the proof time. The new registration adds a later timestamp and replaces the public note and holder of the name. Default false"
}
}
}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.
| Argument | Type | Description |
|---|---|---|
| sha256* | string | SHA-256 digest of the document, 64 hexadecimal characters (a sha256: or 0x prefix is accepted) |
{
"type": "object",
"title": "check_proofArguments",
"required": [
"sha256"
],
"properties": {
"sha256": {
"type": "string",
"title": "Sha256",
"maxLength": 100,
"description": "SHA-256 digest of the document, 64 hexadecimal characters (a sha256: or 0x prefix is accepted)"
}
}
}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.
No arguments.
{
"type": "object",
"title": "get_anchoring_quotaArguments",
"properties": {}
}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).
| Argument | Type | Description |
|---|---|---|
| text* | string | Text to hash, encoded as UTF-8 exactly as given (whitespace and line breaks count), at most 40,000 characters |
{
"type": "object",
"title": "hash_textArguments",
"required": [
"text"
],
"properties": {
"text": {
"type": "string",
"title": "Text",
"maxLength": 40000,
"description": "Text to hash, encoded as UTF-8 exactly as given (whitespace and line breaks count), at most 40,000 characters"
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 18, 2026.