mcpbeat Sign in

Attest MCP Remote MCP Server

answering

Attest MCP Remote is answering right now. Last checked 11 min ago. It exposes 8 tools. Last commit 19 Aug 2026.

Zero-install remote MCP server for proof-of-existence file attestation.

Uptime history 47 days of history · worst day 97%
47 days agonow
100.0%
Uptime 24h
91 of 91 checks
8
Tools
read from the server
835 ms
Response time
average over 24h
0
Stars
last commit 19 Aug 2026

Nothing serious here today

Today is the operative word: we check Attest MCP Remote every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add attest-mcp-remote --transport http https://attest-mcp-remote.it-e3f.workers.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "attest-mcp-remote": {
      "url": "https://attest-mcp-remote.it-e3f.workers.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.attest-mcp-remote]
url = "https://attest-mcp-remote.it-e3f.workers.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "attest-mcp-remote": {
      "url": "https://attest-mcp-remote.it-e3f.workers.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "attest-mcp-remote": {
      "url": "https://attest-mcp-remote.it-e3f.workers.dev/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

anchor
check_anchor
Check whether a work's SHA-256 fingerprint has an OpenTimestamps proof anchored in Bitcoin. The proof is created at attestation time and matures (pending → Bitcoin-confirmed) within a few hours.
attest
attest_hash
Attest a work: the service binds the SHA-256 fingerprint to a server-side timestamp and signs it (HMAC). Requires a credential (device flow via `authorize`, or an API key header). Optional declared metadata (title/author/year/notes) are normalized and BOUND by the signature — immutable after issuance, but they remain self-declared (they don't prove authorship). Compute the SHA-256 locally if you have code execution (`sha256sum <file>` / `shasum -a 256 <file>` / `certutil -hashfile <file> SHA256`). NEVER send file bytes or base64 through tool arguments: this server never receives files. If you cannot compute a hash locally, point the user to the website (https://attestazione.spaziogenesi.org, full privacy: hashing happens in the browser) or the Telegram bot @SGAttestBot.
authorize
authorize
Start the device-flow authorization to attest works in this session (up to 20 attestations, 24h). Returns a link the USER must open in a browser and approve (anti-bot check included). After the user approves, call `complete_authorization`. Not needed if the connection already carries an API key header, or for verification tools.
certificate
create_certificate_pdf
Generate and archive the certificate PDF for a fingerprint attested in this session with `attest_hash`. The PDF is cryptographically signed, anchored in Bitcoin (OpenTimestamps) and archived server-side; this tool returns the permanent links (the PDF itself is downloadable from its URL — it is never inlined here).
complete
complete_authorization
Complete the device-flow authorization after the user approved in the browser. Polls the service briefly; if approval hasn't happened yet, just call this tool again.
lookup
lookup_certificate
Look up whether a work's SHA-256 fingerprint has an attestation certificate in the public archive, and get its permanent links (public certificate page, PDF download, OpenTimestamps proof, browser verification). Trust model: this information is reachable only by whoever knows the fingerprint.
service
service_status
Health of the Spazio Genesi attestation service components: worker (attestation engine), archive (certificate storage), signer (PDF cryptographic signature), anchor (Bitcoin/OpenTimestamps calendars). Values: ok | degraded | down | n/d.
verify
verify_attestation
Verify the server HMAC signature of an attestation issued by the Spazio Genesi service. Confirms that the attestation string (fingerprint + timestamp) and any declared metadata are authentic and untampered. Note: this checks the SIGNATURE only. Whether a given file matches the fingerprint must be checked locally by re-hashing the file. If the certificate carried declared metadata (title/author/year/notes), they must be provided EXACTLY as printed for the signature to verify.

Endpoints

URLTransportStateLatencyChecked
https://attest-mcp-remote.it-e3f.workers.dev/mcp streamable-http answering 652 ms 11 min ago

Alternatives to Attest MCP Remote

same job, measured the same way
Attest MCP
by spazio-genesi

Free proof-of-existence attestation for digital files, MCP tools for the imgauth service.

61 installs/wk local only
Realssh MCP
by danielecr

MCP server for SSH remote command execution

36 installs/wk local only
Remote Filesystem
by pulsemcp

MCP server for remote filesystem operations on cloud storage (Google Cloud Storage).

120 installs/wk local only
Readyorai
by tedoneobichajavascript

Zero-cost MCP server for local code inspection and best-practice recommendations

32 installs/wk local only
Xero
by asklokesh

MCP server for Xero API integration

44 installs/wk local only
SUZURI MCP Server
by pepabo

Official remote MCP server for SUZURI.

answering
Hail
by hail-hq

Phone, SMS & email for AI agents — one remote MCP endpoint, OAuth login, zero install.

20 tools answering
PensionPro
by douglaslinsmeyer

MCP server for the PensionPro pension administration REST API.

79 installs/wk local only

Attest MCP Remote — questions

Answers built from our own checks of this server.

What can Attest MCP Remote do?
It exposes 8 tools, read directly from the server on our last check. Among them: attest_hash, authorize, check_anchor, complete_authorization, create_certificate_pdf, lookup_certificate and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Attest MCP Remote working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 835 ms. The bar chart above shows every period we have measured.
How do I connect Attest MCP Remote?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Attest MCP Remote need an API key?
No. Attest MCP Remote completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Attest MCP Remote?
It answers our handshake in 835 ms on average, which is faster than 13% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Attest MCP Remote open source?
Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.