trust-tools
Server Details
Website security ratings, token verification, and tamper-evident ledger heads from Obelisk Gate.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 10 tools
Each tool targets a distinct resource or operation: guides, explanations, status reads, proof reads, ratings, manifest pinning, URL scanning, ledger reads, and two different token verification types. The descriptions clearly separate overlapping-sounding areas such as get_agent_proof versus verify_agent_run_proof and explain_rating versus get_org_rating.
All names use snake_case and are readable, but the set mixes verb_noun patterns (get_agent_proof, verify_token, scan_trust) with noun_phrase patterns (gate_status, transparency_head, agent_enrollment_guide). The deviation is minor and does not impair recognition.
Ten tools is well-scoped for a trust and verification server, and each tool covers a distinct part of the workflow without obvious redundancy.
The surface covers enrollment guidance, ratings, proofs, verification, URL scanning, manifest pinning, and transparency. Minor gaps exist, such as no listing/search tools and no published consistency proofs for the transparency ledger, but these are explicitly scoped limitations rather than severe workflow blockers.
Available Tools
10 toolsagent_enrollment_guideAInspect
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.
Inputs: no named parameters.
explain_ratingAInspect
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.
Inputs: rating (required), narrate.
gate_statusAInspect
Read the Gate's public liveness facts: issuer, served code revision, OIDC availability, and supported protocols. No posture internals.
Inputs: no named parameters.
get_agent_proofAInspect
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.
Inputs: proof_id (required).
get_org_ratingAInspect
Read the public Obelisk Rating (0-100 score, trust band, and trend) for a registered organization by its slug.
Inputs: org (required).
pin_tool_manifestAInspect
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.
Inputs: tools (required), expected.
scan_trustAInspect
Run Obelisk's public trust scan on an https URL — TLS and security-header posture, scored as an Obelisk Rating. Read-only, SSRF-guarded.
Inputs: url (required).
transparency_headAInspect
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.
Inputs: no named parameters.
verify_agent_run_proofAInspect
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.
Inputs: run_proof, run_proof_token, expected_agent_id, expected_audience.
verify_tokenAInspect
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.
Inputs: token (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Read-only XRP Ledger token-risk, issuer-authenticity and wallet-security checks.
Security grades, SSL/TLS, headers and uptime for your domains, plus a CI deploy gate.
Attested risk scores for stablecoins, DeFi protocols and wallets, with receipts.
Safety checks before you sign, pay or install: contract, token and package scans, phishing, OFAC.
Related MCP Servers
- FlicenseNot gradedqualityBmaintenancePassive website security and trust auditor that checks for security, SEO, AI surface, email, and other exposures, producing a score and remediation plan.-
- AlicenseAqualityCmaintenanceGive AI agents cryptographically signed proof of web observations: Ed25519-signed proof packets (HTTP status, page title, body SHA-256, DNS, TLS) for any public URL.1MIT
- AlicenseBqualityBmaintenanceSigned receipts for agent actions and a read-only-allowlist decision gate, as an MCP server. Ed25519, plus ML-DSA-65 when the post-quantum backend is available. gate_decision returns ALLOW, DENY or ESCALATE from action names and does not observe or block anything. verify_receipt takes expected_kid to pin which key signed. Seven tools.1650 PyPIApache 2.0
- AlicenseAqualityCmaintenanceEnables precise measurement of live HTTP and WebSocket services while maintaining an append-only, evidence-based ledger of claims that agents can query with explicit timestamps, staleness indicators, and instructions for re-verification.6BSD Zero Clause
Glama MCP Gateway
Add one secure layer between your agents and this server.