Back to MCP servers

com.x402supply/entity-resolve

https://entity-resolve.x402supply.com/mcp

● healthy

Fuzzy entity resolution and dedupe for names, addresses, and company records. $0.008/call via x402.

Transport

streamable-http

Auth

—

Cost

—

Protocol revision

2025-11-25

negotiated, not declared

MCP readiness

B · 79/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B+, 92.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	25/25	Endpoint answers the MCP initialize handshake (311 ms).
Protocol revision	8/10	Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	30/30 probes succeeded over 30 days (100%).
Tool declaration	5/10	Lists 1 tool(s) with descriptions.
Verified identity	7/10	Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
Freshness + modern flags	1/5	not seen in a source for over 30 days; declares x402 or machine-readable pricing.
Auth declaration	0/5	How to authenticate is not stated.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (311 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Payment evidence: agent_card — The listing's own card or descriptor declares payment. Also: catalog_listing. Qualifies the payment claim; adds no points.

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 40% of peers; This listing 79 · peer median 81
Latency: Faster than 52% of peers; This listing 311 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Tool declaration −5 — Declare every tool with a description and input schema.
Now: Lists 1 tool(s) with descriptions.
Auth declaration −5 — State how to authenticate (an auth scheme, or that none is needed).
Now: How to authenticate is not stated.
Freshness + modern flags −4 — Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days; declares x402 or machine-readable pricing.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

mcp-registry since 2026-07-15 ↗ wellknown since 2026-09-23 ↗ agenstry since 2026-10-22 ↗ capkey since 2026-10-26 ↗

How to connect

MCP endpoint (streamable-http)

https://entity-resolve.x402supply.com/mcp

JSON-RPC initialize probe

curl -X POST https://entity-resolve.x402supply.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://x402supply.com