Leaderra is an MCP server with 3 tools an agent can call, among them audit_ads, find_leads, reveal_contact. It answers at https://leaderra.ai/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 22 October 2026, succeeded.
GTM data layer for AI agents: find scored B2B leads free, reveal verified email+mobile, audit ads.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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. Inputs: accountId, days, roasTarget |
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 Inputs: offer, icp, count |
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. Inputs: ref |
Every block below points at https://leaderra.ai/api/mcp. Pick your client and copy.
claude mcp add --transport http leaderra https://leaderra.ai/api/mcp
{
"mcpServers": {
"leaderra": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://leaderra.ai/api/mcp"]
}
}
}{
"mcpServers": {
"leaderra": {
"url": "https://leaderra.ai/api/mcp"
}
}
}{
"servers": {
"leaderra": {
"type": "http",
"url": "https://leaderra.ai/api/mcp"
}
}
}{
"context_servers": {
"leaderra": {
"url": "https://leaderra.ai/api/mcp"
}
}
}{
"mcpServers": {
"leaderra": {
"serverUrl": "https://leaderra.ai/api/mcp"
}
}
}{
"mcpServers": {
"leaderra": {
"url": "https://leaderra.ai/api/mcp"
}
}
}name: Leaderra
version: 0.0.1
schema: v1
mcpServers:
- name: Leaderra
type: streamable-http
url: https://leaderra.ai/api/mcp{
"mcpServers": {
"leaderra": {
"httpUrl": "https://leaderra.ai/api/mcp"
}
}
}{
"mcpServers": {
"leaderra": {
"type": "http",
"url": "https://leaderra.ai/api/mcp"
}
}
}{
"mcpServers": {
"leaderra": {
"url": "https://leaderra.ai/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fleaderra.ai%2Fapi%2Fmcp&type=streamable_http&id=leaderra&name=Leaderra
It answered our last check on 22 October 2026 in 542 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
3, as returned by the server's own tools/list on 15 September 2026: audit_ads, find_leads, reveal_contact.
It answered our last check on 22 October 2026 in 542 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://leaderra.ai/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.leaderracom-hue. Endpoint host: leaderra.ai. ARD identifier: urn:air:io.github.leaderracom-hue:mcp:leaderra.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.