Back to directory

X-RAY

https://mcp.x-ray.me/x402/search_entities
● healthy model-context-protocol-mcp

The map of who is doing what in Web3: actors, their links and every public move.

Category
model-context-protocol-mcp
Chains
base, solana
Price
$0.0010 USDC / call

Quality grade

How grading works
B 61.9 / 100
Availability 20.0 / 20
Endpoint responded (HTTP 401)
Payability 15.0 / 15
  • ✓ Answers a real HTTP 402 challenge
  • ✓ Publishes a /.well-known/x402 descriptor
  • ✓ Payment address on record
  • ✓ Settlement network declared
  • ✓ Price declared
Demand 12.1 / 35
12 distinct payers, 158 USDC transfers in the last 30 days; the wallet is shared by 2 listings, so each is credited 1/2
Performance 2.2 / 10
Last probe answered in 1604 ms (full marks at 200 ms or less)
Readiness 12.6 / 15
Agent readiness 84/100
Owner verified 0.0 / 5
Nobody has claimed this listing yet
Endpoint last checked 19 h ago. On-chain activity last read 3 d ago. Availability and on-chain demand are both re-probed daily; the grade updates automatically on the next pass. This grade sets search order and leaderboards; the readiness score below is shown for reference only.

x402 readiness

B · 84/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, 61.9/100), which weighs availability, payability and on-chain demand. How the two differ

Valid payment requirements 10/10 Payment requirements carry a payee, a mainnet network and a price.
Live 402 challenge 20/25 Endpoint reachable; its 402 challenge was seen earlier (1604 ms).
x402 version n/a x402 version not observed yet.
Signed descriptor n/a No x402 standard defines a signed descriptor.
Uptime (30 days) 15/15 7/7 probes succeeded over 30 days (100%).
Resource declaration 8/10 36 paid resources; 36 sampled lack a description.
Verified identity 5/10 Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.
Freshness + modern flags 5/5 seen in a source within 7 days; declares x402.
Security declaration n/a Payment is the access control for an x402 resource.
Applicable criteria total 75 points, scaled to 100.
Responsiveness: Responsive (1604 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Payment evidence: x402_challenge — We sent a request and got a live HTTP 402 challenge. Also: x402_manifest. Qualifies the payment claim; adds no points.
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily probe of the paid endpoint, its payment requirements and 30-day probe history. Signed descriptor and security declaration are n/a for x402 (payment is the access control), as is an x402 version we have not observed; the remaining points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. It also feeds 15 points of the x402 quality grade.

Compared with peers

Against 10,082 reachable x402 APIs in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness
Higher than 67% of peers
This listing 84 · peer median 78
Latency
Faster than 5% of peers
This listing 1,604 ms · peer median 205 ms

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

  • Live 402 challenge −5 — Answer the paid path with a valid 402 challenge.
    Now: Endpoint reachable; its 402 challenge was seen earlier (1604 ms).
  • Verified identity −5 — Claim the listing and prove control of its domain.
    Now: Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.
  • Resource declaration −2 — Declare each paid resource with its input and output schema.
    Now: 36 paid resources; 36 sampled lack a description.

How many agent tools actually work · All statistics

Paid endpoints

36 resource(s) advertised by this origin. Each price below is that resource's own x402 price; the headline price is the range across them.

https://mcp.x-ray.me/x402/search_entities
https://mcp.x-ray.me/x402/get_actor
https://mcp.x-ray.me/x402/list_actors
https://mcp.x-ray.me/x402/get_scope
https://mcp.x-ray.me/x402/get_scope_metrics
https://mcp.x-ray.me/x402/list_scopes
https://mcp.x-ray.me/x402/compare
https://mcp.x-ray.me/x402/list_recent_events
https://mcp.x-ray.me/x402/get_company_events
https://mcp.x-ray.me/x402/get_company_metrics
https://mcp.x-ray.me/x402/hiring_trend
https://mcp.x-ray.me/x402/salary_stats
https://mcp.x-ray.me/x402/top_hiring_companies
https://mcp.x-ray.me/x402/company_hiring_activity
https://mcp.x-ray.me/x402/top_skills_for_company
https://mcp.x-ray.me/x402/top_skills_for_sector
https://mcp.x-ray.me/x402/vacancy_stats_by_blockchain
https://mcp.x-ray.me/x402/vacancy_stats_by_grade
https://mcp.x-ray.me/x402/vacancy_stats_by_sector
https://mcp.x-ray.me/x402/vacancy_stats_by_skill
https://mcp.x-ray.me/x402/list_narratives
https://mcp.x-ray.me/x402/get_narrative
https://mcp.x-ray.me/x402/get_landscape
https://mcp.x-ray.me/x402/get_landscape_brief
https://mcp.x-ray.me/x402/list_landscape_events
https://mcp.x-ray.me/x402/list_vacancies
https://mcp.x-ray.me/x402/search_vacancies
https://mcp.x-ray.me/x402/get_vacancy
https://mcp.x-ray.me/x402/vacancy_skills
https://mcp.x-ray.me/x402/list_skill_clusters
https://mcp.x-ray.me/x402/list_companies
https://mcp.x-ray.me/x402/get_company
https://mcp.x-ray.me/x402/list_blockchains
https://mcp.x-ray.me/x402/list_sectors
https://mcp.x-ray.me/x402/list_company_blockchains
https://mcp.x-ray.me/x402/list_company_sectors

How to call

cURL · x402-fetch / x402-axios will auto-handle 402
curl -sS -i -X GET https://mcp.x-ray.me/x402/search_entities  # expect HTTP 402 Payment Required (about 0.001 USDC/call)
MCP endpoint
https://mcp.x-ray.me/
/.well-known/x402.json
https://mcp.x-ray.me/.well-known/x402

Listed in

Directories this entry was found in.

mcp since 2026-11-06