Developer · Remote MCP server
Trust Tools
Website security ratings, token verification, and tamper-evident ledger heads from Obelisk Gate.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.obeliskgate/trust-tools- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-08-18
- Updated
- 2026-08-18
- Publisher
- com.obeliskgate
- Namespace
- Namespace verified by the MCP Registry via the domain obeliskgate.com · how
- Website
- obeliskgate.com/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://obeliskgate.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- obelisk-trust-tools 1 · protocol 2025-06-18
- Tools discovered
- 8:
scan_trust,verify_token,get_org_rating,verify_agent_run_proof,get_agent_proof,transparency_head,gate_status,explain_rating - Checked on
- 2026-10-05
How to connect Trust Tools
Trust Tools is a remote MCP server: there is nothing to install. Its endpoint is https://obeliskgate.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| TrueIconLets AI coding assistants search the icon packages actually installed in your project. | Local · stdio |
| TruesignalWraps the truesignal CLI as a single generic MCP tool for threat/connector status checks. | Local · stdio |
| Trunk Flaky TestsFlaky test detection, root cause analysis, and fix suggestions for development teams. | Remote · HTTPLive check: sign-in required |
| Trust Score APITrust scoring for domains, wallets, APIs. SSL+DNS+WHOIS+headers. Score 0-100. | Remote · SSELive check: ✗ no handshake |
| TrustablFind and fix reliability and safety gaps in agent code, across nine agent SDKs. | Local · stdio |
| TrusteedCTEM for your Trusteed tenant: security summary, findings, compliance gaps, and scans via OAuth. | Remote · HTTPLive check: sign-in required |
| Trustmodel MCPScore any AI for trust across 10 dimensions; evaluate, monitor & govern LLMs and agents. | Local · stdio |
| TrustNotchTamper-evident audit logs for AI agents: submit, fetch, and verify cryptographic proof bundles. | Local · stdio |