Is the Obeliskgate Trust Tools MCP server down?

mcp-registry/com.obeliskgate/trust-tools · v1

healthy
Last checked 2026-10-26 19:02 UTC · handshake 230ms

As of 2026-10-26 19:02 UTC, the Obeliskgate Trust Tools MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 9 minutes.

uptime (30d checks)
99.9%
checks observed
4,930
outages (90d)
5
tools
9

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

Point your MCP client at this streamable-http endpoint: https://obeliskgate.com/mcp

Agent-readiness: B (80/100)

B (80/100): 0 error(s), 3 warning(s) across 9 tool(s); ~1,344 tokens of tool definitions.
Scores higher than 18% of 15,766 MCP servers Glimind has audited.
Its tool list costs an agent ~1,344 tokens per session — lighter than 65% of servers.
80 → 80 since 2026-10-17
no tool-poisoning patterns
Schemas84
Descriptions100
Safety hints11
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability96

What to fix (5)

9 of 9 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: explain_rating, gate_status, get_agent_proof, get_org_rating, pin_tool_manifest and 4 more

1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).

Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →

Tools: pin_tool_manifest

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: verify_agent_run_proof

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

In the last 30 days: 0 tool(s) removed and 1 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Auto-fix: 6 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.obeliskgate%2Ftrust-tools/fixes

explain_rating 1 change
{
  "name": "explain_rating",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "rating"
    ],
    "properties": {
      "rating": {
        "type": "number",
        "description": "A 0-100 Obelisk Rating, e.g. from scan_trust or get_org_rating."
      },
      "narrate": {
        "type": "boolean",
        "description": "S283 — also return `narrative`, a one-sentence model-written reading of the band (deterministic fields are always present)."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
gate_status 1 change
{
  "name": "gate_status",
  "description": "Read the Gate's public liveness facts: issuer, served code revision, OIDC availability, and supported protocols. No posture internals.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_agent_proof 1 change
{
  "name": "get_agent_proof",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "proof_id"
    ],
    "properties": {
      "proof_id": {
        "type": "string",
        "description": "The opaque id from an /agent/<proof_id> link."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.obeliskgate/trust-tools"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.obeliskgate/trust-tools"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.obeliskgate%2Ftrust-tools.svg)](https://glimind.com/server/mcp-registry%2Fcom.obeliskgate%2Ftrust-tools?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.obeliskgate%2Ftrust-tools?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.obeliskgate%2Ftrust-tools.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.obeliskgate%2Ftrust-tools.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.obeliskgate%2Ftrust-tools?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:d2d752f5215ead17…, first seen 2026-10-25, included at leaf 68283 of 74,904. Version history · verify what your client received.

Tools (9)

Compare: most reliable knowledge servers · most reliable other servers · most reliable security servers · most reliable retrieval servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Obeliskgate Trust Tools MCP server down right now?

As of 2026-10-26 19:02 UTC, the Obeliskgate Trust Tools MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 9 minutes.

How many tools does Obeliskgate Trust Tools MCP server provide?

Obeliskgate Trust Tools MCP server advertises 9 tools, including explain_rating, gate_status, get_agent_proof, get_org_rating, pin_tool_manifest.

How do I install Obeliskgate Trust Tools MCP server?

Point your MCP client at this streamable-http endpoint: https://obeliskgate.com/mcp

Is the Obeliskgate Trust Tools MCP server safe to connect to an AI agent?

Glimind scanned all 9 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Obeliskgate Trust Tools MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve