Skip to content
MCPSTAMP
MCP server report

Lead Intelligence MCP server

ai.saifs/lead-intelligence

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

Measured facts

Score
85B
Sign-in
OAuth
Tools listed
Behind sign-in
Protocol version
None returned
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Not ready Blocked by Resource metadata "resource" equals the server URL.
ChatGPT app directory Not ready Blocked by issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT).
Gemini Connected Apps Unverified Nothing failed, but Supported protocol version negotiated, tools/list returns tools and inputSchema is an object schema could not run in a check without credentials.
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

2 checks to fix

  1. Fails

    Resource metadata "resource" equals the server URL

    auth_resource

    Blocks Claude.

    Measured resource https://lead-scoring-mcp.saifs.ai is not the server URL https://lead-scoring-mcp.saifs.ai/mcp

    Serve metadata whose "resource" is exactly https://lead-scoring-mcp.saifs.ai/mcp (Claude requires an exact match, path included), e.g. at /.well-known/oauth-protected-resource/mcp.

  2. Fails

    issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT)

    auth_chatgpt_metadata

    Blocks ChatGPT.

    Measured issuer "https://multiplewords.in/o" is not exactly the authorization_servers entry "https://multiplewords.in/o/"

    Use the exact metadata "issuer" string in the protected resource metadata authorization_servers list (no trailing-slash or case differences), and list token_endpoint_auth_methods_supported (for example ["none"] for public clients) in the au

12 checks passed, 13 did not run

Passed. Served over HTTPS, initialize over Streamable HTTP, GET answers SSE or 405, initialize latency, Sign-in method the store supports (OAuth or none), 401 carries WWW-Authenticate resource_metadata, Protected resource metadata (RFC 9728), Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields, PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), refresh_token grant advertised.

Not run. Supported protocol version negotiated, JSON or SSE response Content-Type, JSON-RPC error for unknown method, serverInfo name and version, Server instructions, tools capability declared, tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, readOnlyHint or destructiveHint on every tool, Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT), Human-readable title on every tool, Tool descriptions. The tools sit behind sign-in, and the check runs without credentials.

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 Lead Intelligence

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Flead-scoring-mcp.saifs.ai%2Fmcp)](https://www.mcpstamp.com/r/ai-saifs-lead-intelligence/)

HTML

<a href="https://www.mcpstamp.com/r/ai-saifs-lead-intelligence/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Flead-scoring-mcp.saifs.ai%2Fmcp" alt="McpStamp score" height="20"></a>
Registry entry

About this server

Analyze and score leads to identify high-potential prospects and prioritize sales outreach.
Registry name
ai.saifs/lead-intelligence
Remote URL
https://lead-scoring-mcp.saifs.ai/mcp
Version
1.0.1
Source
github.com/Saify-Technologies/saifs-ai-mcps-docs
Website
saifs.ai
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