# io.github.leaderracom-hue/leaderra (remote · leaderra.ai)

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

- Trust score: 76/100 (medium)
- Change this week: +8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `leaderra.ai`: 76/100 (this document), [markdown](https://verifymcp.io/servers/leaderracom-hue-leaderra/api-mcp.md), [page](https://verifymcp.io/servers/leaderracom-hue-leaderra/api-mcp)

## Channel facts

- Endpoint: `https://leaderra.ai/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 299 tokens (~99/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http leaderracom-hue-leaderra https://leaderra.ai/api/mcp
```

### Codex

```toml
[mcp_servers.leaderracom-hue-leaderra]
url = "https://leaderra.ai/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "leaderracom-hue-leaderra": {
      "type": "remote",
      "url": "https://leaderra.ai/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add leaderracom-hue-leaderra --url https://leaderra.ai/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  leaderracom-hue-leaderra:
    url: "https://leaderra.ai/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "leaderracom-hue-leaderra": {
      "type": "http",
      "url": "https://leaderra.ai/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 75, +5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 68)

First indexed and scored.

## MCP tools (3)

### `find_leads` (~124 tokens)

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.

Input parameters:

- `count` (number): How many leads (1-25, default 10).
- `icp` (string, required): Who you sell to (industry, size, geo, role).
- `offer` (string, required): What you sell, in a sentence.

### `reveal_contact` (~74 tokens)

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.

Input parameters:

- `ref` (string, required): The `ref` from a find_leads row.

### `audit_ads` (~101 tokens)

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.

Input parameters:

- `accountId` (string): Adspirer ad_account_id (optional → demo).
- `days` (number): Lookback window in days (default 30).
- `roasTarget` (number): Target ROAS (default 2.5).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/leaderracom-hue-leaderra/api-mcp#diagnostics

## Score history

- 2026-08-03: 76
- 2026-08-02: 75
- 2026-08-01: 75
- 2026-07-31: 75
- 2026-07-30: 70
- 2026-07-29: 70
- 2026-07-28: 69
- 2026-07-27: 68
- 2026-07-26: 68

## Links

- Remote endpoint: https://leaderra.ai/api/mcp
- Authorisation metadata: https://leaderra.ai/.well-known/oauth-protected-resource/api/mcp
- Website: https://leaderra.ai/
- Changelog RSS feed: https://verifymcp.io/servers/leaderracom-hue-leaderra/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/leaderracom-hue-leaderra/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/leaderracom-hue-leaderra/api-mcp