Back to directory

io.github.huwhitememes/tollbooth

https://agenttoll.dev/mcp
● healthy model-context-protocol-mcp

37 paid x402 MCP tools for OSINT, prediction markets, web intel, and agent security on Base USDC.

Category
model-context-protocol-mcp
Chains
—
Price
—

Quality grade

How grading works
B 60.6 / 100
Availability 20.0 / 20
Endpoint responded (HTTP 200)
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 14.0 / 35
19 distinct payers, 236 USDC transfers in the last 30 days; the wallet is shared by 2 listings, so each is credited 1/2
Performance 0.0 / 10
Last probe answered in 2805 ms (full marks at 200 ms or less)
Readiness 11.6 / 15
Agent readiness 77/100
Owner verified 0.0 / 5
Nobody has claimed this listing yet
Endpoint last checked 20 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 · 77/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, 60.6/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 19/25 Endpoint reachable; its 402 challenge was seen earlier (2805 ms); slow response -1.
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 32/32 probes succeeded over 30 days (100%).
Resource declaration 8/10 123 paid resources; 50 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 1/5 not seen in a source for over 30 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: Slow (2805 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, 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 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 50% of peers
This listing 77 · peer median 78
Latency
Faster than 4% of peers
This listing 2,805 ms · peer median 205 ms

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

  • Live 402 challenge −6 — Answer the paid path with a valid 402 challenge.
    Now: Endpoint reachable; its 402 challenge was seen earlier (2805 ms); slow response -1.
  • 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.
  • 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.

How many agent tools actually work · All statistics

Paid endpoints

123 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://agenttoll.dev/mcp
https://agenttoll.dev/mcp#scrape
https://agenttoll.dev/mcp#detect_stack
https://agenttoll.dev/mcp#extract_contacts
https://agenttoll.dev/mcp#score_lead
https://agenttoll.dev/mcp#check_agent_policy
https://agenttoll.dev/mcp#find_agent_resource
https://agenttoll.dev/mcp#validate_agent_manifest
https://agenttoll.dev/mcp#enrich_lead
https://agenttoll.dev/mcp#x402_market_radar
https://agenttoll.dev/mcp#x402_rank_audit
https://agenttoll.dev/mcp#mcp_safety_brief
https://agenttoll.dev/mcp#x402_seller_readiness_audit
https://agenttoll.dev/mcp#mcp_approval_pack
https://agenttoll.dev/mcp#insider_cluster_brief
https://agenttoll.dev/mcp#gov_contract_fit_brief
https://agenttoll.dev/mcp#regulatory_impact_brief
https://agenttoll.dev/mcp#polymarket_event_scan
https://agenttoll.dev/mcp#polymarket_market_scan
https://agenttoll.dev/mcp#cross_platform_arb_scan
https://agenttoll.dev/mcp#rebalance_arb_scan
https://agenttoll.dev/mcp#trending_markets
https://agenttoll.dev/mcp#odds_feed
https://agenttoll.dev/mcp#volume_analytics
https://agenttoll.dev/mcp#resolution_history
https://agenttoll.dev/mcp#kalshi_markets
https://agenttoll.dev/mcp#agent_threat_intel
https://agenttoll.dev/mcp#mcp_supply_chain_iocs
https://agenttoll.dev/mcp#agent_trifecta_score
https://agenttoll.dev/mcp#agent_security_policies
https://agenttoll.dev/mcp#geo_intervention_pulse
https://agenttoll.dev/mcp#flight_intel
https://agenttoll.dev/mcp#osint_research_pack
https://agenttoll.dev/mcp#scenario_verdict
https://agenttoll.dev/mcp#weather_bias_score
https://agenttoll.dev/mcp#supply_chain_stress
https://agenttoll.dev/mcp#regulatory_pulse
https://agenttoll.dev/mcp#attention_momentum
https://agenttoll.dev/mcp#sec_8k_velocity
https://agenttoll.dev/mcp#fred_surprises
https://agenttoll.dev/mcp#treasury_dts
https://agenttoll.dev/mcp#openrouter_models
https://agenttoll.dev/mcp#github_trending
https://agenttoll.dev/mcp#hn_frontpage
https://agenttoll.dev/mcp#usgs_quake
https://agenttoll.dev/mcp#openaq_air
https://agenttoll.dev/mcp#court_opinions
https://agenttoll.dev/mcp#court_docket
https://agenttoll.dev/mcp#federal_register
https://agenttoll.dev/mcp#patents_search

How to call

cURL · x402-fetch / x402-axios will auto-handle 402
curl -sS -i -X GET https://agenttoll.dev/mcp  # expect HTTP 402 Payment Required (price advertised in the 402 response)
MCP endpoint
https://agenttoll.dev/mcp
/.well-known/x402.json
https://agenttoll.dev/.well-known/x402

Listed in

Directories this entry was found in.

mcp since 2026-07-12 awesome-x402 since 2026-07-26 x402scan since 2026-09-13