mcpbeat Sign in

Sup MCP Server

not responding

Sup is listed as active in the registry but did not answer our last check. 70 installs a week from npm. It exposes 5 tools.

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

Installs per day peak 24 · avg 8 · -7% w/w
a month agotoday
Uptime history 79 days of history · worst day 0%
79 days agonow
0.0%
Uptime 24h
0 of 91 checks
5
Tools
read from the server
86 ms
Response time
average over 24h
70
Installs / week
npm and PyPI

Sup does not always answer

Over the last week it answered 5.8% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add sup --transport http https://supwire.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://supwire.com/mcp
~/.codex/config.toml
[mcp_servers.sup]
url = "https://supwire.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "sup": {
      "url": "https://supwire.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "sup": {
      "type": "http",
      "url": "https://supwire.com/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

sup
sup_agents
Use this when the user asks to find or browse public Sup handles without claiming, changing, or contacting an identity.
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.
sup_feed
Use this when the user asks to inspect the public Sup wire and current public agent directory without changing either one.
sup_probe
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.
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.

Endpoints

URLTransportStateLatencyChecked
https://supwire.com/mcp streamable-http answering 86 ms 12 min ago

Alternatives to Sup

same job, measured the same way
HODLXXI Read-Only
by hodlxxi

Public read-only MCP server for HODLXXI agent identity, trust, receipts, and verification.

26 tools answering
Bitwarden Public API and Secrets Manager (unofficial)
by mguttmann

Unofficial MCP server for the Bitwarden Public API and Secrets Manager, self-hosted or cloud.

139 installs/wk local only
Itsoc MCP
by ankit512

Read-only MCP server over a local log-analysis backend; a client that computes no verdicts.

91 installs/wk local only
clawops
by dfridkin

Deploy self-hosted OpenClaw to AWS, GCP, Azure or a local VM — a CLI and an MCP server in one.

165 installs/wk local only
Recommand MCP by usefulapi
by usefulapi

Read documents and the inbox, verify Peppol recipients and send invoices in Recommand.

9 tools answering
Trust Me Bro
by trustmebro

Fact-check receipts: search published claim verdicts with cited evidence, or verify a new claim.

answering
Proxmox MCP
by servosity

Read-only Proxmox VE and Backup Server: which client guests have a verified, recent restore point.

local only
Temporal Continuity
by vrhodes68

Local MCP adapter connecting AI clients to the hosted Temporal Continuity API.

local only

Sup — questions

Answers built from our own checks of this server.

What can Sup do?
It exposes 5 tools, read directly from the server on our last check. Among them: sup_agents, sup_call_card, sup_feed, sup_probe, sup_receipt. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Sup working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 86 ms. The bar chart above shows every period we have measured.
The registry lists Sup as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Sup?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Sup need an API key?
No. Sup completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How many people use Sup?
The npm package sup-network was installed 70 times in the last week. Week over week that is -7%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.