satledger timestamp receipt
by FastDrop
RFC 3161 timestamps, paid per call over x402. No account; verifies offline against the authority.
RFC 3161 timestamps, paid per call over x402. No account; verifies offline against the authority. Official MCP Registry: org.satledger/timestamp-receipt@0.15.3. Remote endpoint: https://api.satledger.org/mcp
Problem it solves
Discoverable MCP server listed in the official MCP Registry.
How it's different
Remote MCP endpoint ingested from the official registry and probed by FastDrop.
Ingested from the official MCP Registry
FastDrop pulled this entry from the official MCP Registry as org.satledger/timestamp-receipt and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed
and the description is not theirs.
If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.
Claim this listingTools this endpoint exposes
Read directly from the endpoint on 11 Oct 2026. Not supplied by the maker.
timestamp_receiptSubmit a SHA-256 digest and receive a Time-Stamp Authority's signed RFC 3161 token over it: evidence that the data you hashed existed at that time, verifiable against the authority without trusting or
Is this tool yours?
Claim this listing and we’ll verify ownership before handing it over.
Sign in to claim this listingSimilar launches
Matched on shared tags and the tools their MCP servers actually expose.
Shares tags: MCP server
Shares tags: MCP server
Shares tags: MCP server
Shares tags: MCP server
Shares tags: MCP server
Shares tags: MCP server
Reviews
Sign in to leave a review.
No reviews yet.
Comments
Sign in to join the discussion.
No comments yet - start the discussion.