mcpbeat Sign in

Corpole MCP Server

answering

Corpole is answering right now. Last checked 2 min ago.

Requirements authority for AI coding agents: binding requirements and acceptance criteria.

Uptime history 19 days of history
19 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
424 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Corpole 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 2 min ago.

run in your terminal
claude mcp add requirements --transport http https://corpole.com/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "requirements": {
      "url": "https://corpole.com/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.requirements]
url = "https://corpole.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "requirements": {
      "url": "https://corpole.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "requirements": {
      "url": "https://corpole.com/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://corpole.com/api/mcp streamable-http sign-in 227 ms 2 min ago

Alternatives to Corpole

same job, measured the same way
Kibi MCP
by looted

MCP server for Kibi's requirements, traceability, and proof workflows in coding agents.

2 298 installs/wk local only
CrawlConsole
by crawlconsole

Backlink Analysis MCP for AI Agents: authority, referring domains, and competitor link gaps.

31 installs/wk answering
Touchstone
by savecharlie

Verifiable text/code/measurement tools for agents, each reproducing a named authority.

40 installs/wk local only
Milestone by Ouroboros Apps
by lahutchins91

Freelance project milestones and acceptance criteria for AI assistants

15 tools answering
Cleotic
by generaldataworks

AI brand visibility, competitor mentions and citation evidence for agents. Cleotic account required.

answering
SearchAtlas
by search-atlas-group

SearchAtlas AI Agent — SEO, content, PPC, authority building, and site management

128 installs/wk local only
MCP Gateway
by titus-civic

Identity, authorization, audit trails, and revocable permissions for AI agents accessing MCP tools.

answering
Agent Release Auditor
by veyndrasystems

Deterministic release gate for AI-written code and coding agents.

62 installs/wk local only

Corpole — questions

Answers built from our own checks of this server.

Why is there no tool list for Corpole?
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 Corpole working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 424 ms. The bar chart above shows every period we have measured.
How do I connect Corpole?
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 sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Corpole?
No API key is involved. Corpole answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Corpole?
It answers our handshake in 424 ms on average, which is faster than 32% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.