Trust Tools MCP Server

by obeliskgate Your server? Claim it

answering

Trust Tools is answering right now. Last checked 11 min ago. It exposes 9 tools.

Website security ratings, token verification, and tamper-evident ledger heads from Obelisk Gate.

Uptime history 76 days of history · worst day 0%

76 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

416 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 8

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 23 August 2026. No other catalogue keeps this.

25 Oct a tool appeared pin_tool_manifest

9 Oct a tool description was rewritten transparency_head

4 Oct a tool description was rewritten verify_agent_run_proof

4 Oct a tool changed the parameters it asks for verify_agent_run_proof

2 Sep a tool description was rewritten explain_rating

2 Sep a tool changed the parameters it asks for explain_rating

23 Aug 2 tools appeared get_agent_proof, verify_agent_run_proof

Nothing serious here today

Today is the operative word: we check Trust Tools every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add trust-tools --transport http https://obeliskgate.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://obeliskgate.com/mcp

~/.codex/config.toml

[mcp_servers.trust-tools]
url = "https://obeliskgate.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "trust-tools": {
      "url": "https://obeliskgate.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "trust-tools": {
      "type": "http",
      "url": "https://obeliskgate.com/mcp"
    }
  }
}

Available tools 9

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

verify

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 the run challenge, and which delegation hops matched the owner's registry when the token was signed. A bare run_proof envelope is only checked for internal consistency and is never reported as verified, because anyone can build one. Reports the envelope's commitment scheme: a legacy v1 envelope, whose hashes are unsalted, carries the warning unsalted-v1. Does not reveal or infer raw task data.

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.

agent

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.

explain

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, public-scope, never required). Pure function of the number — no data is read.

gate

gate_status

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

org

get_org_rating

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

pin_tool_manifest

Pin an MCP tool manifest before an agent trusts it. Returns a SHA-256 digest per tool and for the whole catalogue (canonical JSON, every field counts), hidden-text findings (Unicode tag, bidi and zero-width characters) and an injection signal per tool. Pass the digests you stored at approval as expected to detect a changed, added or removed tool. Up to 64 tools in a request body of at most 256 KB. Read-only and stateless; the injection score is one signal, not a guarantee.

scan

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.

transparency

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 proofs are published, so this cannot show a later head extends a saved one. Same data as /.well-known/obelisk-transparency.json.

Endpoints

URL	Transport	State	Latency	Checked
https://obeliskgate.com/mcp	streamable-http	answering	433 ms	11 min ago

Alternatives to Trust Tools

same job, measured the same way

Cybercentry Verification

by co-cybercentry

Twelve tools: token, wallet, contract and site security. Two free, the rest $1 in USDC over x402.

14 tools answering

AgentGraph Trust

by agentgraph-co

Security scanning and trust verification for AI agent tools.

310 installs/wk local only

PandaWard

by ratomirjovanovic

Local, evidence-based application security assessment with an evidence ledger and retests.

local only

HexScan Token Security

by hexscan

Honeypot detection & token risk scan for ERC-20s. Risk score 0-100, tax, source verification.

3 tools answering

Mozilla Observatory

by pipeworx-io

MDN HTTP Observatory — grade any website's HTTP security headers and get the specific fixes, from…

376 installs/wk 47 tools answering

XRPL Token Guard

by riehnbean

Read-only XRP Ledger token-risk, issuer-authenticity and wallet-security checks.

3 tools answering

Trent

by trent

Security reviews, threat models over a repo or website, and remediation tracking, in your editor.

answering

MobiLoop

by enessubass

Guarded AI mobile Appium testing, security scanning, verification, and fix-retest MCP tools.

local only

Trust Tools — questions

Answers built from our own checks of this server.

What can Trust Tools do?

It exposes 9 tools, read directly from the server on our last check. Among them: explain_rating, gate_status, get_agent_proof, get_org_rating, pin_tool_manifest, scan_trust and 3 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Trust Tools working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 416 ms. The bar chart above shows every period we have measured.

How do I connect Trust Tools?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Trust Tools need an API key?

No. Trust Tools completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Trust Tools?

It answers our handshake in 416 ms on average, which is faster than 30% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.