Built for human creators. Register a timestamp on Polygon proving you made something, the moment you did. Your file is never uploaded, watermarked, or altered: only its cryptographic fingerprint ever reaches spArxx.io, zero-knowledge by design. A human still provisions the account behind the connection. This is deliberate, since this registration only means something with a human behind it.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 6 tools
Each tool targets a distinct operation: create, read (get/list evidence), verify, and cost lookups. The only mild overlap is verify_certificate vs. get_evidence, since both surface receipt data, though their intended purposes and auth requirements are clearly described.
All six tools follow a clean verb_noun snake_case pattern (create_timestamp, get_balance, get_evidence, get_pricing, list_evidence, verify_certificate). The only wrinkle is descriptions referencing internal names like 'timestamp_register', but the actual tool names are fully consistent.
Six tools is well-scoped for a timestamping service covering the create-poll-verify workflow plus cost pre-checks. Each tool earns its place with no redundant surface.
Core lifecycle is covered: create a timestamp, list evidence, fetch a full receipt kit, verify proofs, and check pricing/balance. Logically immutable records need no delete/update, so the only minor gap is any explicit status-check tool separate from get_evidence.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.
