io.github.leaderracom-hue/leaderra
REMOTE · LEADERRA.AI · SCANNED AUG 3
GTM data layer for AI agents: find scored B2B leads free, reveal verified email+mobile, audit ads.
Available components
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. How we score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 299 tokens (~99/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · leaderra.ai
claude mcp add --transport http leaderracom-hue-leaderra https://leaderra.ai/api/mcp
[mcp_servers.leaderracom-hue-leaderra] url = "https://leaderra.ai/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"leaderracom-hue-leaderra": {
"type": "remote",
"url": "https://leaderra.ai/api/mcp",
"enabled": true
}
}
} openclaw mcp add leaderracom-hue-leaderra --url https://leaderra.ai/api/mcp --transport streamable-http
mcp_servers:
leaderracom-hue-leaderra:
url: "https://leaderra.ai/api/mcp" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +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.
- 31 Jul 26 +5
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +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.
- 28 Jul 26 +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.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 68
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://leaderra.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=leaderra.ai | CN=YR1,O=Let's Encrypt,C=US | 4 Jul 2026 | 2 Oct 2026 | RSA 2048 | SHA256-RSA | 58e1f4561fcfe10c0b22f2e0c8f1e07adfc |
| SANs: leaderra.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of leaderra.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| leaderra.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://www.google-analytics.com https://cal.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://www.google-analytics.com https://www.googletagmanager.com; font-src 'self' data:; connect-src 'self' https://llfzyttsupapkishmnxc.supabase.co wss://llfzyttsupapkishmnxc.supabase.co https://www.google-analytics.com https://analytics.google.com https://www.googletagmanager.com; frame-src 'self' https://js.stripe.com https://cal.com https://*.cal.com; frame-ancestors 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://leaderra.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://leaderra.ai/api/mcp | HTTPS enforced | 308 | https://leaderra.ai/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
audit_ads ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | — | Adspirer ad_account_id (optional → demo). |
| days | number | — | Lookback window in days (default 30). |
| roasTarget | number | — | Target ROAS (default 2.5). |
No output schema declared.
No examples provided.
find_leads ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | — | How many leads (1-25, default 10). |
| icp | string | yes | Who you sell to (industry, size, geo, role). |
| offer | string | yes | What you sell, in a sentence. |
No output schema declared.
No examples provided.
reveal_contact ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ref | string | yes | The `ref` from a find_leads row. |
No output schema declared.
No examples provided.