mcpbeat

Summit53 Revenue Engine MCP Server

io.summit53/mcp-server
answering

Summit53 Revenue Engine is answering right now. Last checked 4 min ago. 44 installs a week from npm. Last commit 15 Jul 2026.

Revenue Engine for scoped diagnosis, action planning, execution, and Figure-Eight value evidence.

Installs per day peak 140 · avg 12 · -29% w/w
a month agotoday
Uptime history 43 hours of history
43 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
1098 ms
Response time
average over 24h
44
Installs / week
npm and PyPI

Connect this server

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

run in your terminal
claude mcp add mcp-server --transport http https://api.summit53.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://api.summit53.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp-server]
url = "https://api.summit53.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://api.summit53.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://api.summit53.io/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://api.summit53.io/mcp streamable-http needs key 1339 ms 4 min ago

Summit53 Revenue Engine — questions

Answers built from our own checks of this server.

Why is there no tool list for Summit53 Revenue Engine?
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 Summit53 Revenue Engine 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 1098 ms. The bar chart above shows every period we have measured.
How do I connect Summit53 Revenue Engine?
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 Summit53 Revenue Engine need an API key?
Yes. Every time we knock, Summit53 Revenue Engine 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 Summit53 Revenue Engine?
It answers our handshake in 1098 ms on average, which is faster than 4% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Summit53 Revenue Engine?
The npm package @summit53/mcp-server was installed 44 times in the last week. Week over week that is -29%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Summit53 Revenue Engine open source?
Yes — it is published under the NOASSERTION licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.