# Glyt (remote · glyt.net)

Human-in-the-loop approval for agent actions, with verifiable action-bound receipts.

- Trust score: 61/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `glyt.net`: 61/100 (this document), [markdown](https://verifymcp.io/servers/net-glyt-glyt/glyt.md), [page](https://verifymcp.io/servers/net-glyt-glyt/glyt)

## Channel facts

- Endpoint: `https://glyt.net/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 43/100
  - AI-judged instruction clarity (poor).
  - Tool/resource definitions use about 662 tokens (~110/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 78/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 33% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.net-glyt-glyt]
url = "https://glyt.net/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "net-glyt-glyt": {
      "type": "remote",
      "url": "https://glyt.net/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add net-glyt-glyt --url https://glyt.net/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  net-glyt-glyt:
    url: "https://glyt.net/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 59, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 56, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 55, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 54, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 53)

First indexed and scored.

## MCP tools (6)

### `discovery` (~27 tokens)

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

### `verify_receipt` (~91 tokens)

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.

Input parameters:

- `action` (object, required)
- `expected_agent_sub` (string)
- `receipt` (required): The receipt envelope object or its JSON string.
- `required_acr` (string)

### `get_receipt` (~25 tokens)

Fetch a signed receipt envelope by id.

Input parameters:

- `receipt_id` (string, required)

### `request_approval` (~111 tokens)

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 decision.

Input parameters:

- `action` (object, required)
- `callback_url` (string)
- `id_token` (string, required): A Colony token-exchange id_token audienced to Glyt.
- `stake_tier` (string)
- `summary` (string)

### `check_approval` (~51 tokens)

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

Input parameters:

- `id_token` (string, required)
- `request_id` (string, required)

### `file_contest` (~257 tokens)

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 id_token — Glyt writes it AS you, holding no secret. Sign JCS{v:1,recorder_id:<standing.anchor.contest.recorder>,event_type:"touchstone.contest",actor_sub:<your sub>,counterparty_sub:null,payload_hash:<target_digest>,client_ts:null}; target_digest is standing.anchor.attestation entry's payload_hash (from the inclusion endpoint). contestant_pubkey/contestant_sig are standard base64.

Input parameters:

- `contestant_pubkey` (string, required): Your ed25519 public key, standard base64.
- `contestant_sig` (string, required): Your signature over the contest signed_content, standard base64.
- `id_token` (string, required): Your Glyt-audience Colony id_token (authenticates you as the subject).
- `reason` (string, required)
- `receipt_id` (string, required)
- `touchstone_id_token` (string, required): Your Touchstone-audience Colony id_token (authenticates the contest write as you).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/net-glyt-glyt/glyt#diagnostics

## Score history

- 2026-08-03: 61
- 2026-08-02: 60
- 2026-08-01: 60
- 2026-07-31: 59
- 2026-07-30: 56
- 2026-07-29: 55
- 2026-07-28: 55
- 2026-07-27: 54
- 2026-07-26: 53

## Links

- Remote endpoint: https://glyt.net/mcp
- Website: https://glyt.net/
- Changelog RSS feed: https://verifymcp.io/servers/net-glyt-glyt/glyt/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/net-glyt-glyt/glyt/changelog.json
- HTML version of this page: https://verifymcp.io/servers/net-glyt-glyt/glyt