mcpbeat Sign in

Peaje MCP Server

answering

Peaje is answering right now. Last checked 10 min ago.

Your Peaje agent: tasks to get your site cited by AI, its score, and answers about your business.

Uptime history 6 days of history · worst day 99%
6 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
320 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Peaje missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

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

run in your terminal
claude mcp add peaje --transport http https://api.usepeaje.com/_owner/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.usepeaje.com/_owner/mcp
~/.codex/config.toml
[mcp_servers.peaje]
url = "https://api.usepeaje.com/_owner/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "peaje": {
      "url": "https://api.usepeaje.com/_owner/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "peaje": {
      "type": "http",
      "url": "https://api.usepeaje.com/_owner/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.usepeaje.com/_owner/mcp streamable-http sign-in 335 ms 10 min ago

Alternatives to Peaje

same job, measured the same way
KaiCalls
by kaicalls

A phone number for your business or your AI agent. Kai answers it and calls businesses for you.

answering
AI Index Network
by willians2018

Answers questions about a business using its indexed website content, with cited sources.

answering
Salt
by saltapp

Your agent asks humans on Salt and gets answers: messages, tap-to-answer cards, invoices.

86 installs/wk answering
Takibi Base
by takibibase

Ask your Takibi Base collections anything; get answers with cited passages and a support score.

answering
Ennodia
by cherninlab

Connects the AI agents you use: your agent hands a task to another and gets the answer back

176 installs/wk local only
Savi Tools
by getsavitools

Ask your AI assistant about your Savi Tools business: invoices, expenses, mileage, and more.

25 tools answering
Taskriz
by taskriz

Let your AI agent ask a person for a decision, a date or a photo, and get a structured answer back.

answering
BotPhone
by botphone

Give any AI agent a phone number. BotPhone answers your business line and reports every call back.

answering

Peaje — questions

Answers built from our own checks of this server.

Why is there no tool list for Peaje?
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 Peaje 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 320 ms. The bar chart above shows every period we have measured.
How do I connect Peaje?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form 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 Peaje?
No API key is involved. Peaje 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 Peaje?
It answers our handshake in 320 ms on average, which is faster than 47% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.