satledger timestamp receipt

org.satledgerv0.15.2Updated Oct 11, 2026

RFC 3161 timestamps, paid per call over x402. No account; verifies offline against the authority.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant obtain RFC 3161 timestamp receipts from a remote authority, paid per call, and verify them offline.

What it does
This remote MCP server exposes an RFC 3161 timestamping service over streamable HTTP. An assistant can request a timestamp receipt for data, and the receipt can later be verified offline against the timestamp authority. Payment is handled per call rather than through an account.
When to use it
Useful when an assistant needs a verifiable proof that some data existed at a particular time, for example to timestamp a document hash, a commit, or a record. It fits workflows where a standards-based timestamp is preferred over a self-asserted date.
Requirements
A remote MCP client that supports streamable HTTP, pointed at the provider's endpoint. No account is declared, but each call is paid, so a payment method compatible with the per-call billing is needed. Network access to the endpoint is required.
Before you install
Each call costs money, so repeated or automated use can accumulate charges. Timestamp requests send the data or its hash to a third-party authority, which may be sensitive. Verify receipts offline before relying on them.

Installation

In SourceWeft

  1. Open satledger timestamp receipt in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "timestamp-receipt": {
      "type": "http",
      "url": "https://api.satledger.org/mcp"
    }
  }
}

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.15.2LatestOct 11, 2026