Obelisk MCP server

• Registry namecom.obeliskgate/trust-toolsverified in the MCP registry

The registry name sits under obeliskgate.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-24
• Tools8
• Server calls itselfobelisk-trust-tools
• Server version1
• Protocol version2025-06-18

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 67 ms.

• Its tools do none of the product's use cases we checked: add passkey sign-in to a web app; let AI agents and MCP clients act under scoped OAuth tokens.
• Checked on 3 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
• What an agent can do with it0 of 2 use cases
• Answeredmeasuring3 of the 7 daily checks it takes to print a share
• Median first answer226 ms
• Space in an agent's context≈ 1,244 tokensthe definitions of all its tools (9), which an agent carries on every turn
• Tool definitionsB · 81 of 100
• Typed results0 of 9 toolsdeclared outputSchema: results come typed, read once

• Parameters without a type: in 1 of 9
• Not saying whether it only reads or can destroy: 9 of 9

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• scan_trust

  Run Obelisk's public trust scan on an https URL — TLS and security-header posture, scored as an Obelisk Rating. Read-only, SSRF-guarded.

• verify_token

  Verify that a JSON Web Token was minted by this Obelisk Gate (ES256, correct issuer) and report its type, subject, assurance, and principal. Never returns secrets.

• get_org_rating

  Read the public Obelisk Rating (0-100 score, trust band, and trend) for a registered organization by its slug.

• verify_agent_run_proof

  Verify an Obelisk run proof. Pass run_proof_token, the token Obelisk signs at POST /api/agent-proof/run: the tool checks Obelisk's signature against its published keys, that the named agent is active now with the same key that answered…

• get_agent_proof

  Read an Obelisk agent's public proof vector by opaque proof id. Returns independent claims with freshness and scope; never a scalar trust score or a claim of non-humanness.

• transparency_head

  Read the current signed transparency head of Obelisk's tamper-evident receipt ledger. Save headAnchorHash with anchorCount and compare later: the count must never go down, and the head at a saved count must not change. No consistency…

• gate_status

  Read the Gate's public liveness facts: issuer, served code revision, OIDC availability, and supported protocols. No posture internals.

• explain_rating

  Explain what an Obelisk Rating number means: its trust band, how the public scan scores, and what typically moves a score. Deterministic by default; pass narrate:true for an additional one-line model-written narrative (cached…