Back to MCP servers
● down

Stamp is a utility MCP for agents and pipelines that need reliable attribution primitives they cannot safely produce themselves. 6 commands. *NOTE* Canonicalization change: records attested before this change on September 11th won't verify under JCS, the hash input changed. That's inherent to fixing the canonicalization, old records were only verifiable against Python's json.dumps. 1. *calculate*: evaluates math expressions in a sandboxed AST evaluator. Agents offload arithmetic here rather than computing it through token generation, which is unreliable. Supports arithmetic operators, exponentiation, modulo, logarithms, trigonometry, rounding, and mathematical constants. 2. *generate_uuid*: mints one or more UUIDv4 identifiers on demand, up to 1000 at a time. Any agent that creates records, sessions, events, or transactions needs collision-resistant IDs that come from a trusted source rather than being synthesized by the model. 3. *get_time*: queries an NTP server (Cloudflare by default) and returns verified UTC or other select timezones alongside the container clock's current offset in milliseconds. Agents writing audit logs, timestamping financial events, or coordinating across distributed nodes get actual time rather than whatever the host clock believes. 4. *diff*: returns a unified diff between two text strings with added and removed line counts and configurable context. Agents that transform text can verify the exact delta before committing rather than reasoning about what changed. 5. *attest*: takes anything, returns it back wrapped with a verified timestamp, a UUID, and a hash of the payload. One call, the record is complete and tamper-evident. 6. *verify*: takes an attested record, returns pass/fail. Did this payload produce this hash at this timestamp. Provable. *DISCLAIMER* Stamp queries public NTP infrastructure (Cloudflare, stratum 3), alongside public Python libraries, and is suitable for general agentic workflows. Implementers are responsible for what they put in payloads, Stamp doesn't log payload content. Usage in production systems is at the implementer's risk.

Transport
streamable-http
Auth
smithery_api_key
Cost
—
Protocol revision
2026-07-28
negotiated, not declared

MCP readiness

D · 47/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here E, 12.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake 0/10 No MCP handshake completed.
Live MCP endpoint 0/25 Endpoint did not answer.
Protocol revision 10/10 Speaks the current MCP revision 2026-07-28.
Signed descriptor n/a No MCP standard defines a signed server descriptor.
Uptime (30 days) 11/15 22/30 probes succeeded over 30 days (73%).
Tool declaration 10/10 Lists 6 tool(s) with descriptions.
Verified identity 5/10 Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags 4/5 seen in a source within 7 days.
Auth declaration 2/5 Declares credential scheme: smithery_api_key.
Applicable criteria total 90 points, scaled to 100.
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,021 reachable MCP servers in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.

Readiness
Higher than 26% of peers
This listing 47 · peer median 81

Where it loses the most points, and how to win them back

  • Live MCP endpoint −25 — Answer initialize and tools/list at the declared endpoint.
    Now: Endpoint did not answer.
  • Valid MCP handshake −10 — Complete the MCP handshake without errors.
    Now: No MCP handshake completed.
  • Verified identity −5 — Claim the listing and prove control of its domain.
    Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

How to connect

MCP endpoint (streamable-http)
https://server.smithery.ai/wolfendentheo/Stamp/mcp
JSON-RPC initialize probe
curl -X POST https://server.smithery.ai/wolfendentheo/Stamp/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Homepage
https://smithery.ai/servers/wolfendentheo/Stamp
Listed at (smithery)
https://smithery.ai/servers/wolfendentheo/Stamp