Skip to content

Glyt MCP server

Which MCP servers are Glyt's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to Glyt

Whose server it is
  • Registry namenet.glyt/glytverified in the MCP registry

The registry name sits under glyt.net. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools6
  • Server calls itselfglyt
  • Server version0.1.0
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 389 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.

Once connected

  • For "Get a named human to approve a specific agent action", the likely first call is request_approval.
  • Parameters are untyped or undescribed in 5 of 6 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 9, the first on 2026-10-26
  • INITE MCP score90 of 100answers 100 · definitions 67 · context 100 · connects 100
  • Answered100% of days9 of 9 daily checks
  • Median first answer426 ms
  • Space in an agent's context≈ 808 tokensthe definitions of all its tools (6), which an agent carries on every turn
  • Tool definitionsC · 67 of 100
  • Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a type: in 1 of 6
  • Parameters without a description: in 5 of 6
  • Not saying whether it only reads or can destroy: 6 of 6

What an agent can do with it

  • can do · Get a named human to approve a specific agent action
  • not sure · Attach an offline-checkable approval receipt to an action
  • not sure · Have a downstream service refuse actions lacking recent approval

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers6 tools · read 2026-10-26
  • discovery

    Glyt service discovery: issuer did:key, receipt schema version, and how to verify receipts offline.

  • verify_receipt

    Verify a Glyt receipt against the exact action you are about to run. Returns {valid, decision, acr, not_after, reasons}. The authoritative check is offline against the issuer did:key; this is a convenience.

  • get_receipt

    Fetch a signed receipt envelope by id.

  • request_approval

    Ask the operator behind this agent to approve a specific action. Requires a Colony token-exchange id_token (colony:operator) as `id_token`. Returns the request view; poll with check_approval. Nothing is approved without the human's…

  • check_approval

    Poll one of your approval requests. Requires the same `id_token`. Returns the request view, including the signed receipt once decided.

  • file_contest

    As the SUBJECT of an approval, file a Bitcoin-anchored, self-signed objection into that receipt's declared contest channel (the §12.3 upper bound). You sign the contest with your OWN ed25519 key and supply your OWN Touchstone-audience…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "glyt": {
      "type": "http",
      "url": "https://glyt.net/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http glyt https://glyt.net/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://glyt.net/mcp as a custom connector in the settings.

OpenAPI spec

6 paths, read 2026-10-26. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.