mcpbeat Sign in

Site Rep MCP Server

answering

Site Rep MCP is answering right now. Last checked 11 min ago.

Read-only Site Rep handoff: agent brief, pending work, first-customer receipt with payment evidence.

Uptime history 21 days of history
21 days agonow
100.0%
Uptime 24h
91 of 91 checks
Tools
hidden behind auth
331 ms
Response time
average over 24h
API key or OAuth
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Site Rep MCP 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 site-rep --transport http https://siterep.net/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "site-rep": {
      "url": "https://siterep.net/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.site-rep]
url = "https://siterep.net/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "site-rep": {
      "url": "https://siterep.net/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "site-rep": {
      "url": "https://siterep.net/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://siterep.net/api/mcp streamable-http needs key 311 ms 11 min ago

Alternatives to Site Rep MCP

same job, measured the same way
Paybond MCP Server
by nonameuserd

Default trust layer for agentic payments: authorize agent spend, evidence, receipts, settlement.

272 installs/wk local only
US Brand Intelligence
by timzinin-api

Pay-per-call US brand evidence and signal workflows with free MCP discovery and x402 payments.

21 tools answering
VouchSpec Agent Skill Evidence
by mordiaky

Read-only discovery for exact-commit Agent Skill validation, x402 payment, and signed receipts.

answering
Hilt Pay Agent Commerce
by hilt

x402 V2 payment-to-access on Solana USDC with receipts, entitlements, atomic metering and webhooks.

9 tools answering
Hive Intelligence MCP
by hiveintelligence

Evidence-backed crypto due diligence with sources, freshness, and a runtime receipt on every call.

962 installs/wk 8 tools answering
Agon Protocol
by agonx402

MCP server for Agon Protocol state reads and prepare-only payment-channel actions.

138 installs/wk local only
Stripe
by stripe

MCP server integrating with Stripe - tools for customers, products, payments, and more.

answering
Ryvo Protocol
by ryvonetwork

MCP server for Ryvo Protocol state reads and prepare-only payment-channel actions.

76 installs/wk local only

Site Rep MCP — questions

Answers built from our own checks of this server.

Why is there no tool list for Site Rep MCP?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Site Rep MCP 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 331 ms. The bar chart above shows every period we have measured.
How do I connect Site Rep MCP?
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. You will need your own key or an OAuth login: it refuses anonymous clients.
Does Site Rep MCP need an API key?
Yes. Every time we knock, Site Rep MCP answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Site Rep MCP?
It answers our handshake in 331 ms on average, which is faster than 53% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.