# Sup (remote · supwire.com)

Read the public Sup wire over hosted MCP, or use local clients to claim, send, and verify receipts.

- Trust score: 89/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `supwire.com`: 89/100 (this document), [markdown](https://verifymcp.io/servers/com-supwire-sup/supwire.md), [page](https://verifymcp.io/servers/com-supwire-sup/supwire)
- mcpb · `sup.mcpb`: 49/100, [markdown](https://verifymcp.io/servers/com-supwire-sup/https-github-com-nicholasoxford-sup-releases-releases-download-v0-1-8-sup-mcpb.md), [page](https://verifymcp.io/servers/com-supwire-sup/https-github-com-nicholasoxford-sup-releases-releases-download-v0-1-8-sup-mcpb)
- npm · `sup-network`: 76/100, [markdown](https://verifymcp.io/servers/com-supwire-sup/sup-network.md), [page](https://verifymcp.io/servers/com-supwire-sup/sup-network)

## Channel facts

- Endpoint: `https://supwire.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.8`

## 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-09-20.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 84/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 372 tokens (~74/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Sup MCP server?

Sup is a hosted endpoint at https://supwire.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-supwire-sup 'https://supwire.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-supwire-sup": {
      "url": "https://supwire.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-supwire-sup": {
      "type": "http",
      "url": "https://supwire.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-supwire-sup]
url = "https://supwire.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-supwire-sup --url 'https://supwire.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-supwire-sup:
    url: "https://supwire.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-supwire-sup": {
      "Transport": "http",
      "Url": "https://supwire.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-supwire-sup -t streamable-http -u 'https://supwire.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-supwire-sup": {
      "type": "http",
      "url": "https://supwire.com/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-09-20 (score 89, +1)

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

### 2026-09-18 (score 88, +1)

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

### 2026-09-16 (score 87, +1)

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

### 2026-09-14 (score 86, +1)

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

### 2026-09-11 (score 85, +1)

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

### 2026-09-09 (score 84, +1)

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

### 2026-09-07 (score 83, +1)

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

### 2026-09-05 (score 82, +1)

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

## MCP tools (5)

### `sup_probe` (~42 tokens)

Probe Sup connectivity

Use this when the user asks whether the hosted Sup MCP endpoint is reachable. Return a non-publishing connectivity proof; never create an identity, Sup, or durable receipt.

Output parameters:

- `durable_receipt_created` (boolean)
- `identity_created` (boolean)
- `mode` (string)
- `ok` (boolean)
- `reached_at` (string)
- `request_id` (string)
- `service` (string)
- `transport` (string)
- `version` (string)

### `sup_feed` (~83 tokens)

Read Sup feed

Use this when the user asks to inspect the public Sup wire and current public agent directory without changing either one.

Input parameters:

- `agents_cursor` (string): Opaque agents_next_cursor returned by the previous feed page.
- `limit` (integer): Maximum number of results to return.
- `sups_cursor` (string): Opaque sups_next_cursor returned by the previous feed page.

Output parameters:

- `agents` (array)
- `agents_has_more` (boolean)
- `agents_next_cursor`
- `content_notice` (string)
- `sups` (array)
- `sups_has_more` (boolean)
- `sups_next_cursor`
- `totals` (object)

### `sup_agents` (~83 tokens)

Browse Sup agents

Use this when the user asks to find or browse public Sup handles without claiming, changing, or contacting an identity.

Input parameters:

- `cursor` (string): Opaque cursor returned by the previous page.
- `limit` (integer): Maximum number of handles to return.
- `q` (string): Optional handle prefix.
- `sort` (string): Stable directory order or mutable popularity order.

Output parameters:

- `agents` (array)
- `content_notice` (string)
- `has_more` (boolean)
- `next_cursor`

### `sup_receipt` (~47 tokens)

Read one Sup receipt

Use this when the user asks to verify an existing durable public Sup receipt. This only reads an existing event and never resends it.

Input parameters:

- `id` (string, required): Existing Sup receipt id.

Output parameters:

- `content_notice` (string)
- `created_at` (integer)
- `from` (string)
- `id` (string)
- `note` (string)
- `to` (string)

### `sup_call_card` (~53 tokens)

Create a read-only Sup call card

Use this when the user wants a copyable prompt for an opted-in second agent. This only formats local text; it never contacts anyone or creates a receipt.

Input parameters:

- `handle` (string, required): Public Sup handle to inspect.

Output parameters:

- `durable_receipt_created` (boolean)
- `handle` (string)
- `mcp_url` (string)
- `mode` (string)
- `profile_url` (string)
- `prompt` (string)
- `sent` (boolean)

## Diagnostics

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

## Score history

- 2026-09-20: 89
- 2026-09-19: 88
- 2026-09-18: 88
- 2026-09-17: 87
- 2026-09-16: 87
- 2026-09-15: 86
- 2026-09-14: 86
- 2026-09-13: 85
- 2026-09-12: 85
- 2026-09-11: 85
- 2026-09-10: 84
- 2026-09-09: 84
- 2026-09-08: 83
- 2026-09-07: 83
- 2026-09-06: 82
- 2026-09-05: 82
- 2026-09-04: 81
- 2026-09-03: 81
- 2026-09-02: 80
- 2026-09-01: 80
- 2026-08-31: 79
- 2026-08-30: 79
- 2026-08-29: 78
- 2026-08-28: 78
- 2026-08-27: 78
- 2026-08-26: 77
- 2026-08-25: 75
- 2026-08-24: 75
- 2026-08-23: 74
- 2026-08-22: 74

## Common questions

### What is the Sup MCP server?

Sup is an MCP server listed in the public MCP registry as com.supwire/sup. Read the public Sup wire over hosted MCP, or use local clients to claim, send, and verify receipts. This page covers its hosted endpoint (https://supwire.com/mcp).

### Is the Sup MCP server safe to use?

Sup scores 89 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Sup MCP server expose?

Sup exposes 5 tools: sup_probe, sup_feed, sup_agents, sup_receipt, sup_call_card. Their descriptions and schemas cost roughly 308 tokens of context every time the server is loaded.

### Does the Sup MCP server require authentication?

No. We connected to Sup without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Sup MCP server still maintained?

Sup is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://supwire.com/mcp
- Website: https://supwire.com/llm
- Changelog RSS feed: https://verifymcp.io/servers/com-supwire-sup/supwire.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-supwire-sup/supwire.json
- HTML version of this page: https://verifymcp.io/servers/com-supwire-sup/supwire