mcpbeat Sign in

Peec Ai MCP Server

answering

Peec Ai is answering right now. Last checked moments ago.

Uptime history 48 days of history · worst day 98%
48 days agonow
100.0%
Uptime 24h
92 of 92 checks
Tools
hidden behind auth
150 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Peec Ai 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 0 min ago.

run in your terminal
claude mcp add mcp --transport http https://api.peec.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://api.peec.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://api.peec.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://api.peec.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://api.peec.ai/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://api.peec.ai/mcp streamable-http sign-in 226 ms 0 min ago

Alternatives to Peec Ai

same job, measured the same way
Day Ai
by day-ai
answering
Otter Ai
by otter-ai
answering
Lawve Ai
by lawve-ai
answering
V
Fiscal Ai
by fiscal-ai
answering
Windsor Ai
by windsor-ai
answering
V
Clarity Ai
by clarity-ai
6 tools answering
Pendo
by pendo
answering
Aiera
by aiera
answering

Peec Ai — questions

Answers built from our own checks of this server.

Why is there no tool list for Peec Ai?
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 Peec Ai 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 150 ms. The bar chart above shows every period we have measured.
How do I connect Peec Ai?
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 Peec Ai?
No API key is involved. Peec Ai 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 Peec Ai?
It answers our handshake in 150 ms on average, which is faster than 77% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.