mcpbeat

Leaderra MCP Server

io.github.leaderracom-hue/leaderra
not responding

Leaderra is listed as active in the registry but did not answer our last check. It exposes 3 tools.

GTM data layer for AI agents: find scored B2B leads free, reveal verified email+mobile, audit ads.

Uptime history 39 hours of history · worst hour 0%
39 hours agonow
0.0%
Uptime 24h
0 of 91 checks
3
Tools
read from the server
19 ms
Response time
average over 24h
open, no key
Access
streamable-http

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 leaderra --transport http https://leaderra.ai/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "leaderra": {
      "url": "https://leaderra.ai/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.leaderra]
url = "https://leaderra.ai/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "leaderra": {
      "url": "https://leaderra.ai/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "leaderra": {
      "url": "https://leaderra.ai/api/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

audit
audit_ads
Audit a connected Meta ad account (via Adspirer): scores each ad, flags wasted spend, and returns prioritized actions. Spends 5 credits. Omit accountId to audit the demo account.
leads
find_leads
Find scored, in-market B2B leads (hot-signal) for an offer + ICP. Returns a list with a fit score and a call brief, but WITHOUT contacts — call reveal_contact with a row's `ref` to get email/phone. Searching is FREE: credits are only spent on reveals.
reveal
reveal_contact
Reveal a verified email + mobile for a lead `ref` returned by find_leads. Spends 12 credits (email 2 + mobile 10); fully refunded if nothing verifiable is found — you are never charged on a miss.

Endpoints

URLTransportStateLatencyChecked
https://leaderra.ai/api/mcp streamable-http answering 19 ms 10 min ago

Leaderra — questions

Answers built from our own checks of this server.

What can Leaderra do?
It exposes 3 tools, read directly from the server on our last check. Among them: audit_ads, find_leads, reveal_contact. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Leaderra working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 19 ms. The bar chart above shows every period we have measured.
The registry lists Leaderra as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Leaderra?
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.
Does Leaderra need an API key?
No. Leaderra completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.