Is the Noseforleads Leads MCP server down?

mcp-registry/com.noseforleads/leads-mcp · v1.29.0

healthy
Last checked 2026-10-18 14:17 UTC · handshake 189ms

As of 2026-10-18 14:17 UTC, the Noseforleads Leads MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 4 minutes.

uptime (30d checks)
100%
checks observed
3,729
outages (90d)
6
tools
11

Finds, filters, and verifies local-business leads; every email carries a verification receipt.

Install Noseforleads Leads MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http noseforleads-leads-mcp-server https://api.noseforleads.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "noseforleads-leads-mcp-server": {
      "type": "http",
      "url": "https://api.noseforleads.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (83/100)

B (83/100): 0 error(s), 3 warning(s) across 11 tool(s); ~6,623 tokens of tool definitions.
Scores higher than 42% of 15,376 MCP servers Glimind has audited.
Its tool list costs an agent ~6,623 tokens per session — more than 65% of servers.
83 → 83 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions33
Safety hints100
Token cost85
Client compatibility100
Protocol100
Reliability85
Stability100

What to fix (3)

1 tool definition(s) exceed ~1,200 tokens each (largest: start_campaign, ~4,689).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~4,089 tokens every session. How to fix →

Tools: start_campaign · saves ~4,089 tokens/session

33 parameter(s) across 9 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: add_suppression, fetch_results, get_campaign_status, get_credits, list_campaigns and 4 more

Handshake + tools/list takes ~2,221 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.noseforleads/leads-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.noseforleads/leads-mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.noseforleads%2Fleads-mcp.svg)](https://glimind.com/server/mcp-registry%2Fcom.noseforleads%2Fleads-mcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.noseforleads%2Fleads-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.noseforleads%2Fleads-mcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.noseforleads%2Fleads-mcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.noseforleads%2Fleads-mcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:87d408912e10cd89…, first seen 2026-10-17, included at leaf 1513 of 22,260. Version history · verify what your client received.

Tools (11)

Compare: most reliable communication servers · most reliable data servers · most reliable other servers · most reliable finance servers · most reliable knowledge servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Noseforleads Leads MCP server down right now?

As of 2026-10-18 14:17 UTC, the Noseforleads Leads MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 4 minutes.

How many tools does Noseforleads Leads MCP server provide?

Noseforleads Leads MCP server advertises 11 tools, including add_suppression, fetch_results, get_campaign_status, get_credits, get_icp_pack.

How do I install Noseforleads Leads MCP server?

Point your MCP client at this streamable-http endpoint: https://api.noseforleads.com/mcp

Is the Noseforleads Leads MCP server safe to connect to an AI agent?

Glimind scanned all 11 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Noseforleads Leads MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.