Local MCP capabilities provider for Expo
Nothing to run from here
Attest Remote is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
8
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Zero-install remote MCP server for proof-of-existence file attestation.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http attest-remote-mcp https://attest-mcp-remote.it-e3f.workers.dev/mcp
# 2 — ask your agent for something these tools do
# service_status, check_anchor, verify_attestation and 5 more
Attest Remote costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SGAll 2 servers
@spazio-genesi2 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http attest-remote-mcp https://attest-mcp-remote.it-e3f.workers.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sha256 | string | yes | SHA-256 fingerprint of the work: 64 hexadecimal characters. Compute the SHA-256 locally if you have code execution (sha256sum <file> / shasum -a 256 <file> / certutil -hashfile <file> SHA256). N |
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/yea
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sha256 | string | yes | SHA-256 fingerprint of the work: 64 hexadecimal characters. Compute the SHA-256 locally if you have code execution (sha256sum <file> / shasum -a 256 <file> / certutil -hashfile <file> SHA256). N |
| attestazione | string | yes | The attestation string exactly as printed on the certificate: "SHA-256:<hash>@<ISO timestamp>Z" |
| hmac | string | yes | The server HMAC signature exactly as printed on the certificate (base64, 44 characters ending with '='). |
| titolo | string | no | Declared title, exactly as printed (only if the certificate shows it). |
| autore | string | no | Declared author, exactly as printed (only if the certificate shows it). |
| anno | string | no | Declared year/version, exactly as printed (only if the certificate shows it). |
| note | string | no | Declared notes, exactly as printed (only if the certificate shows them). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sha256 | string | yes | SHA-256 fingerprint of the work: 64 hexadecimal characters. Compute the SHA-256 locally if you have code execution (sha256sum <file> / shasum -a 256 <file> / certutil -hashfile <file> SHA256). N |
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.
No parameter schema on file.
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.
No parameter schema on file.
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 h
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sha256 | string | yes | SHA-256 fingerprint of the work: 64 hexadecimal characters. Compute the SHA-256 locally if you have code execution (sha256sum <file> / shasum -a 256 <file> / certutil -hashfile <file> SHA256). N |
| name | string | no | File name (descriptive only, shown on the certificate). |
| size | integer | no | File size in bytes (descriptive only). |
| type | string | no | MIME type (descriptive only). |
| titolo | string | no | Declared title of the work (bound by the signature). |
| autore | string | no | Declared author (bound by the signature). |
| anno | string | no | Declared year/version (bound by the signature). |
| note | string | no | Declared notes (bound by the signature). |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sha256 | string | yes | SHA-256 fingerprint of the work: 64 hexadecimal characters. Compute the SHA-256 locally if you have code execution (sha256sum <file> / shasum -a 256 <file> / certutil -hashfile <file> SHA256). N |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Attest Remote or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Attest Remote can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.