com.obeliskgate/trust-tools
REMOTE · OBELISKGATE.COM
Website security ratings, token verification, and tamper-evident ledger heads from Obelisk Gate.
Available components
Last scanned (5 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1087 tokens (~108/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: fail → pass ▲ functional
- Stability: pass → 0.97 functional
- New tool “agent_enrollment_guide” functional
- 26 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: pass → fail ▼ functional
- MCP protocol: fail → pass ▲ functional
- MCP protocol version: 2025-06-18 → 2026-07-28 functional
- New tool “pin_tool_manifest” functional
- 14 Oct 26 0
- Stability: 0.97 → pass security
- 13 Oct 26 0
- Stability: pass → 0.97 functional
- 5 Oct 26 0
- Tool “verify_agent_run_proof” rewrote its description, which is the text the model reads security
- Schema quality: 74 → 98 ▼ functional
- “verify_agent_run_proof” added an optional parameter “expected_audience” cosmetic
- “verify_agent_run_proof” added an optional parameter “run_proof_token” cosmetic
- “verify_agent_run_proof” reworded the description of “run_proof” cosmetic
- “verify_agent_run_proof” made “run_proof” optional cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://obeliskgate.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=obeliskgate.com | CN=YE1,O=Let's Encrypt,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5f1f56494f5a09d83002698a394eb2b27ec |
| SANs: obeliskgate.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of obeliskgate.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| obeliskgate.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'none'; script-src 'unsafe-inline'; style-src 'unsafe-inline'; style-src-attr 'unsafe-inline'; img-src 'self' data:; font-src 'self'; connect-src 'self'; form-action 'self'; frame-ancestors 'none'; base-uri 'none'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | geolocation=(), camera=(), microphone=(), payment=(), usb=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://obeliskgate.com/mcp | Verified | 200 | |
| http (plaintext) | http://obeliskgate.com/mcp | HTTPS enforced | 308 | https://obeliskgate.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
agent_enrollment_guide ~72
Read how an AI agent enrolls with this Obelisk Gate: the endpoints in order, the fields each takes, which key types this deployment can prove, whether enrollment is switched on, and the current account sign-up posture an approving owner needs. Read-only; no input, no state is changed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
explain_rating ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| narrate | boolean | – | S283 — also return `narrative`, a one-sentence model-written reading of the band (deterministic fields are always present). |
| rating | number | yes | A 0-100 Obelisk Rating, e.g. from scan_trust or get_org_rating. |
No output schema declared.
No examples provided.
gate_status ~36
Read the Gate's public liveness facts: issuer, served code revision, OIDC availability, and supported protocols. No posture internals.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_agent_proof ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| proof_id | string | yes | The opaque id from an /agent/<proof_id> link. |
No output schema declared.
No examples provided.
get_org_rating ~52
Read the public Obelisk Rating (0-100 score, trust band, and trend) for a registered organization by its slug.
| Name | Type | Req | Description |
|---|---|---|---|
| org | string | yes | The organization slug, e.g. acme. |
No output schema declared.
No examples provided.
pin_tool_manifest ~164
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.
| Name | Type | Req | Description |
|---|---|---|---|
| expected | – | – | Optional: the catalogueDigest string from an earlier pin, or an object of { toolName: digest } (optionally with catalogue). |
| tools | array | yes | The tools array exactly as the server's tools/list returned it. |
No output schema declared.
No examples provided.
scan_trust ~65
Run Obelisk's public trust scan on an https URL — TLS and security-header posture, scored as an Obelisk Rating. Read-only, SSRF-guarded.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The https URL to scan, e.g. https://example.com |
No output schema declared.
No examples provided.
transparency_head ~87
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_agent_run_proof ~266
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.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_agent_id | string | – | Optional expected agt_ subject. |
| expected_audience | string | – | Optional: require the run token's audience to equal this value. |
| run_proof | object | – | An obelisk-agent-run-proof-v2 envelope (a legacy v1 envelope is accepted and flagged unsalted-v1). Alone it is checked for consistency only; next to run_proof_token it must equal the signed copy. |
| run_proof_token | string | – | The run_proof_token returned by POST /api/agent-proof/run. The only input that can verify. |
No output schema declared.
No examples provided.
verify_token ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | A compact-serialized JWT issued by Obelisk (id_token or access token). |
No output schema declared.
No examples provided.
How do I install the com.obeliskgate/trust-tools MCP server?
com.obeliskgate/trust-tools is a hosted endpoint at https://obeliskgate.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · obeliskgate.com
claude mcp add --transport http com-obeliskgate-trust-tools 'https://obeliskgate.com/mcp'
What is the com.obeliskgate/trust-tools MCP server?
com.obeliskgate/trust-tools is an MCP server listed in the public MCP registry as com.obeliskgate/trust-tools. Website security ratings, token verification, and tamper-evident ledger heads from Obelisk Gate. This page covers its hosted endpoint (https://obeliskgate.com/mcp).
Is the com.obeliskgate/trust-tools MCP server safe to use?
com.obeliskgate/trust-tools scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.obeliskgate/trust-tools MCP server expose?
com.obeliskgate/trust-tools exposes 10 tools: scan_trust, verify_token, get_org_rating, verify_agent_run_proof, get_agent_proof, and 5 more. Their descriptions and schemas cost roughly 1,015 tokens of context every time the server is loaded.
Does the com.obeliskgate/trust-tools MCP server require authentication?
No. We connected to com.obeliskgate/trust-tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.obeliskgate/trust-tools MCP server still maintained?
com.obeliskgate/trust-tools is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.