MCP.Market

Attest Remote MCP server

not responding
by SPAZIO-GENESI·io.github.SPAZIO-GENESI/attest-mcp-remote·v1.0.0
No reviews yet

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

D48/100grade D
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
D48/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Attest Remote yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Attest Remote tools (8, 1 write)

write = sends, deletes, buys or posts
  • attest_hashFree

    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.

  • authorizeFree

    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.

  • check_anchorFree

    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.

  • complete_authorizationFree

    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.

  • create_certificate_pdfwrite actionFree

    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).

  • lookup_certificateFree

    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_statusFree

    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_attestationFree

    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.

Public scan report

scanner v0.1.10 · 2026-10-25 · same rubric, same numbers if you re-run it

1 high
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote unreachable: HTTP 5000/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityno auth information5/15
  • Maintenancelast push 3 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

Findings (1)

  • highRemote endpoint did not respondreliability.unreachable

    HTTP 500

Overall 48/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Attest Remote compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
48/100
higher than 9% of 48,255 servers
Tools
8
the typical server has 7
Tools that change things
13%
typical: 0%. Fewer write tools means less an agent can break
Uptime
0%
of our recent checks; the typical remote server answers 100%
Response time
496 ms
faster than 30% of 30,031 servers

What its tools let an agent do: 7 read · 1 create

Install Attest Remote in Claude Code, Cursor or VS Code

claude mcp add --transport http attest-mcp-remote https://attest-mcp-remote.it-e3f.workers.dev/mcp
Add to Cursor

What the publisher says

From the Attest Remote repository's README, as published. We do not edit it. Read it on GitHub

attest-mcp-remote

Listed on the official MCP Registry as io.github.SPAZIO-GENESI/attest-mcp-remote.

Remote MCP server (Streamable HTTP) for the Spazio Genesi digital-work attestation service. Zero install: add the URL as a connector in your MCP client and start verifying and attesting.

No file ever transits — by design. MCP has no reliable client→server file channel, and this service doesn't want one: every tool works on the SHA-256 fingerprint of the work. Agents with code execution compute it locally (sha256sum ), so the file never leaves the machine it lives on — not even through this server. For local-file tooling use the stdio package @spazio-genesi/attest-mcp; for humans, the website (in-browser hashing, full privacy) or the Telegram bot @SGAttestBot.

Status

In production. Live at https://attest-mcp-remote.it-e3f.workers.dev/mcp. All 8 tools implemented, tested, and validated end-to-end against production, including a real zero-install run from claude.ai (connector by URL, human Turnstile approval, certificate PDF issued and archived).

Tools

Credentials: either the zero-config device flow above, or an Authorization: Bearer sgk… header on the connection (e.g. Claude Code: claude mcp add --transport http attest --header "Authorization: Bearer sgk…"). Self-service keys: https://imgauth.spaziogenesi.org/developer/keys

Develop

npm install
npm run dev            # wrangler dev (default port 8787)
node test/smoke.mjs http://127.0.0.1:8787

test/smoke.mjs drives the Streamable HTTP transport end-to-end (initialize → tools/list → tools/call) against real, public production data (read-only). test/smoke-auth.mjs covers the credentialed flow and is a local-only harness: it needs an isolated imgauth wrangler dev (own --persist-to state, SIGNER_URL emptied) because the user-approval step is simulated by writing the local D1 directly — see the header comment in the file.

⚠️ When bumping the version

This server is also advertised through an MCP Server Card published by the web interface, which repeats this server's name, version and endpoint:

https://attestazione.spaziogenesi.org/.well-known/mcp/server-card.json → file: imgauthweb/.well-known/mcp/server-card.json

That file is not generated from this repository, so a version bump here silently makes it wrong. When you change version in package.json and server.json, update serverInfo.version in the card too — same release, same day. (Publishing a card that misstates the version is the same class of problem as an openapi.json left behind: a descriptor that lies is worse than none.)

Security

Report vulnerabilities → /sicurezza/ (responsible disclosure policy, safe harbor for good-faith research) — this repo has no security.txt of its own (Worker with no static assets), but the policy covers the whole project, including this workers.dev service.

License

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-10-25downgradeB → Dscore 48: Remote endpoint did not respond

Attest Remote: common questions

Is Attest Remote MCP server safe?
Not recommended: it is graded D (48/100). Read the Attest Remote safety report
How do I install Attest Remote?
It runs remotely at attest-mcp-remote.it-e3f.workers.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Attest Remote need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Attest Remote maintained?
The last commit was 13 days ago (2026-10-22). The latest release is v1.0.0.
Is Attest Remote up?
0% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Attest Remote compare with other MCP servers?
safety score 48/100 (higher than 9% of 48,255 servers); tools 8 (the typical server has 7); tools that change things 13% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.