# trust-tools [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://obeliskgate.com/mcp  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/trust-tools

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

## Tools
Capabilities this server exposes over MCP:

- **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 the structural integrity, agent binding, delegation continuity, and commitments of an Obelisk action-scoped run proof. Does not reveal or infer raw task data.
- **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 — pin it and compare later to prove history only extends. Same data as /.well-known/obelisk-transparency.json.
- **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, public-scope, never required). Pure function of the number — no data is read.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: medium). Install path inferred — verify against the README before running it. Add as a URL/SSE server in your client:

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

## Documentation

## What trust-tools MCP server does

The trust-tools MCP server connects an MCP client to public trust and verification functions from Obelisk Gate. It covers website security posture, organization ratings, token authenticity, agent proof verification, transparency-ledger state, and public service status.

The server is suited to workflows that need evidence about an HTTPS site, organization, token, agent execution, or transparency history. Its verification tools report structured claims and validation results rather than exposing secrets or underlying task data.

## Tools and capabilities

- `scan_trust` runs a public trust scan against an HTTPS URL. The result covers TLS and security-header posture and includes an Obelisk Rating. The scan is read-only and SSRF-guarded.
- `verify_token` checks whether a JSON Web Token was issued by Obelisk Gate using ES256 and the expected issuer. It reports the token type, subject, assurance, and principal, without returning secrets.
- `get_org_rating` retrieves an organization’s public Obelisk Rating using its slug. The response includes a score from 0 to 100, a trust band, and a trend.
- `verify_agent_run_proof` checks the structural integrity, agent binding, delegation continuity, and commitments in an action-scoped run proof. It does not reveal or infer raw task data.
- `get_agent_proof` retrieves an agent’s public proof vector by opaque proof ID. Results contain independent claims with freshness and scope; they are not a scalar trust score or a claim that the subject is non-human.
- `transparency_head` reads the current signed head of Obelisk’s tamper-evident receipt ledger. A caller can retain the head and compare it later to establish that the history only extended.
- `gate_status` reports public liveness facts, including the issuer, served code revision, OIDC availability, and supported protocols.
- `explain_rating` interprets an Obelisk Rating number by returning its trust band, describing the public scan’s scoring, and identifying factors that typically change the score. The result is deterministic by default; `narrate:true` adds a cached, one-line model-written narrative.

## How it works

The trust-tools MCP server presents these operations as MCP tools. Several operations read public information, while the verification operations validate supplied tokens or proof material. `explain_rating` is a pure interpretation of the supplied number and does not read external data.

`transparency_head` provides the current ledger checkpoint, which can be pinned for a later comparison. `get_agent_proof` and `verify_agent_run_proof` serve different purposes: the former reads public claims by proof ID, while the latter validates the structure and continuity of a supplied run proof.

## Limitations and notes

The listed operations are narrowly scoped to public ratings, public status, verification, and trust evidence. Token verification never returns secrets, and agent-proof operations do not expose or infer raw task data. An agent proof is not presented as a single trust score or evidence that an agent is non-human.

`scan_trust` accepts HTTPS URLs and is read-only. `explain_rating` does not calculate a new rating or fetch source data; it explains a number. The available material does not specify installation commands, transport details, authentication requirements, or environment variables.

The trust-tools MCP server should therefore be evaluated for evidence and verification workflows rather than general website crawling, secret management, or task-data inspection.

_Full upstream README: https://allmcps.com/mcp/trust-tools/readme_