Skip to content

com.obeliskgate/trust-tools

by obeliskgate.com · remote · no sign-in to list tools · v1.0.0 · published by com.obeliskgate

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

Changes · 3
CompareRegistry entry

8 tools: 3 change things and 5 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

8 tools

Changes things 3Claude Code: ask
  • scan_trustRun Obelisk's public trust scan on an https URL — TLS and security-header posture, scored as an Obelisk Rating.Can send data outNo findings

    Why it is in this group

    • The description's first verb is "run": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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_agent_run_proofVerify an Obelisk run proof.No findings

    Why it is in this group

    • The name "verify_agent_run_proof" says "run": a word for a change.
    Description, as the server wrote it
    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_tokenVerify that a JSON Web Token was minted by this Obelisk Gate (ES256, correct issuer) and report its type, subject, assurance, and principal.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 5Claude Code: allow
  • explain_ratingExplain what an Obelisk Rating number means: its trust band, how the public scan scores, and what typically moves a score.No findings

    Why it is in this group

    • The name "explain_rating" says "explain": a word for reading.
    Description, as the server wrote it
    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_statusRead the Gate's public liveness facts: issuer, served code revision, OIDC availability, and supported protocols.No findings

    Why it is in this group

    • The name "gate_status" says "status": a word for reading.
    Description, as the server wrote it
    Read the Gate's public liveness facts: issuer, served code revision, OIDC availability, and supported protocols. No posture internals.
  • get_agent_proofRead an Obelisk agent's public proof vector by opaque proof id.No findings

    Why it is in this group

    • The name "get_agent_proof" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_org_ratingRead the public Obelisk Rating (0-100 score, trust band, and trend) for a registered organization by its slug.No findings

    Why it is in this group

    • The name "get_org_rating" says "get": a word for reading.
    Description, as the server wrote it
    Read the public Obelisk Rating (0-100 score, trust band, and trend) for a registered organization by its slug.
  • transparency_headRead the current signed transparency head of Obelisk's tamper-evident receipt ledger.No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__trust-tools__get_org_rating",
      "mcp__trust-tools__get_agent_proof",
      "mcp__trust-tools__transparency_head",
      "mcp__trust-tools__gate_status",
      "mcp__trust-tools__explain_rating"
    ],
    "ask": [
      "mcp__trust-tools__scan_trust",
      "mcp__trust-tools__verify_token",
      "mcp__trust-tools__verify_agent_run_proof"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as trust-tools. Review it before you use it.

Capability tags behind 1 rule
  • mcp__trust-tools__scan_trust outbound