satledger timestamp receipt
RFC 3161 timestamps, paid per call over x402. No account; verifies offline against the authority.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"timestamp-receipt": {
"url": "https://api.satledger.org/mcp"
}
}
}Remote endpoints
https://api.satledger.org/mcpstreamable-httpWhat it can do
Tool inventory
Tools (1)
🟡timestamp_receipt(digest)
Submit 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 contacting this service. Hash your data yourself - it never leaves your side. Costs 0.05 USDC per call, paid over x402. No account, nothing stored here afterwards.
Input Schema
{
"type": "object",
"properties": {
"digest": {
"type": "string",
"pattern": "^[0-9a-fA-F]{64}$",
"description": "SHA-256 hex digest, 64 characters."
}
},
"required": [
"digest"
],
"additionalProperties": false
}Community
Evidence