mcpbeat Sign in

Sup MCP Server

by supwire Your server? Claim it
answering

Sup is answering right now. Last checked 11 min ago. 167 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 385 · avg 40 · -72% w/w
a month agotoday
Uptime history 10 days of history
10 days agonow
100.0%
Uptime 24h
91 of 91 checks
5
Tools
read from the server
493 ms
Response time
average over 24h
167
Installs / week
npm and PyPI

Nothing serious here today

Today is the operative word: we check Sup every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

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 11 min ago.

run in your terminal
claude mcp add sup --transport http https://supwire.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "sup": {
      "url": "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
{
  "mcpServers": {
    "sup": {
      "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 464 ms 11 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
Itsoc MCP
by ankit512

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

94 installs/wk local only
Pixelcheck
by xcodethink

Real eyes and hands on the web for AI agents. MCP-first. Local-first. Vendor-agnostic.

74 installs/wk local only
New Relic MCP Server
by meet-bhalodiya

Secure, self-hosted New Relic observability and administration tools for MCP clients

69 installs/wk local only
Thoth
by ahmedeid1

Read-only MCP over an agentic SLR workspace with per-claim citation verification

answering
Groundcheck
by beepboop2025

Verify claims, resolve FIGI identity, extract claims, and sign x402 delivery receipts over MCP.

55 installs/wk 5 tools answering
Inferrail
by domondi1

Read-only MCP tools over Inferrail's local receipt ledger: attributed spend and gateway health.

215 installs/wk local only
AgenticEmail
by agenticemail

Hosted email for AI agents: create inboxes, send, receive, and reply over MCP with scoped API keys

answering

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 91 of 91 checks got a reply (100.0%), average response time 493 ms. The bar chart above shows every period we have measured.
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 with the file path 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 fast is Sup?
It answers our handshake in 493 ms on average, which is faster than 35% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Sup?
The npm package sup-network was installed 167 times in the last week. Week over week that is -72%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.