Skip to content
MCPSTAMP
MCP server report

Nose for Leads MCP server

com.noseforleads/leads-mcp

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 89 of 100 (grade B), higher than 60.6% of the 33,003 registry servers that responded over HTTPS that day. Ready for MCP Registry. Not ready for Claude, ChatGPT and Gemini.

Measured facts

Score
89B
Sign-in
OAuth
Tools listed
11
Protocol version
2025-11-25
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Not ready Blocked by inputSchema is an object schema.
ChatGPT app directory Not ready Blocked by inputSchema is an object schema and Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT).
Gemini Connected Apps Not ready Blocked by inputSchema is an object schema.
Official MCP Registry Ready No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

5 checks to fix

  1. Fails

    inputSchema is an object schema

    tool_schema

    Blocks Claude, ChatGPT and Gemini.

    Measured 11/11 invalid: translate_icp, start_campaign, get_campaign_status, fetch_results, get_icp_pack and 6 more

    Give every tool an inputSchema with "type": "object" (use {"type":"object","properties":{}} for no arguments).

  2. Fails

    Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT)

    tool_open_world

    Blocks ChatGPT.

    Measured 7/11 tools miss an explicit hint: translate_icp, get_campaign_status, fetch_results, get_icp_pack, get_credits and 2 more

    Set readOnlyHint, destructiveHint and openWorldHint to explicit true/false on every tool (OpenAI app review requires all three).

  3. Fails

    Server instructions

    instructions

    Measured No instructions in the initialize result

    Add an "instructions" string to the initialize result: what the server covers, for whom, and its limits.

  4. Warning

    JSON-RPC error for unknown method

    jsonrpc_errors

    Measured HTTP 401 instead of a JSON-RPC error

    Route the method first and answer unknown methods with JSON-RPC error -32601 before the auth check, or return a JSON-RPC error body with the 401.

  5. Warning

    refresh_token grant advertised

    auth_refresh

    Measured grant_types_supported: ["authorization_code"]

    Issue refresh tokens and list "refresh_token" in grant_types_supported so users are not logged out hourly.

22 checks passed

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, GET answers SSE or 405, initialize latency, serverInfo name and version, tools capability declared, Sign-in method the store supports (OAuth or none), 401 carries WWW-Authenticate resource_metadata, Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields, issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), tools/list returns tools, Tool names are valid and portable, readOnlyHint or destructiveHint on every tool, Human-readable title on every tool, Tool descriptions.

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for Nose for Leads

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fapi.noseforleads.com%2Fmcp)](https://www.mcpstamp.com/r/com-noseforleads-leads-mcp/)

HTML

<a href="https://www.mcpstamp.com/r/com-noseforleads-leads-mcp/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Fapi.noseforleads.com%2Fmcp" alt="McpStamp score" height="20"></a>
Registry entry

About this server

Finds, filters, and verifies local-business leads; every email carries a verification receipt.
Registry name
com.noseforleads/leads-mcp
Remote URL
https://api.noseforleads.com/mcp
Version
1.0.0
Website
www.noseforleads.com/mcp-server-local-business-leads
Checked
2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade B servers

All grade B servers · All server reports · State of MCP readiness, November 2026