MCP & x402 Readiness Auditor
Pricing
from $10.00 / 1,000 mcp and x402 seller audits
MCP & x402 Readiness Auditor
Validate remote MCP tools and x402 seller discovery, pricing, and payment readiness before autonomous agents spend money.
Pricing
from $10.00 / 1,000 mcp and x402 seller audits
Rating
0.0
(0)
Developer
Dries Vd
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
2 days ago
Last modified
Categories
Share
What does MCP & x402 Buyer Readiness Monitor do?
MCP & x402 Buyer Readiness Monitor validates agent services before autonomous buyers spend money. Give it a seller URL and it performs a real MCP initialization handshake, discovers available tools, inspects the x402 discovery document, checks prices and payment networks, and returns a compact readiness score. Run it through Apify's API, connect it to workflows, schedule recurring checks, or monitor many vendors in one request.
The Actor is designed for AI-agent developers, marketplaces, procurement agents, and x402 sellers. It produces structured evidence—not vague claims—so downstream agents can decide whether a service is technically safe to attempt.
Why use MCP & x402 Buyer Readiness Monitor?
- Prevent wasted paid calls to broken or incomplete agent endpoints.
- Discover MCP tools and their input schemas automatically.
- Verify that x402 prices and blockchain networks are explicitly advertised.
- Monitor vendor readiness over time and detect regressions.
- Compare up to 20 sellers in a single API request.
- Feed normalized JSON into autonomous purchasing and routing workflows.
How to use MCP & x402 Buyer Readiness Monitor
- Start the Actor in Standby mode.
- Send a POST request to
/auditon its Standby URL. - Provide one
urlor an array namedurls. - Read the score, failed checks, discovered tools, prices, and recommendation.
- Schedule the same request when you need continuous vendor monitoring.
Input
{ "url": "https://agent-revenue-auditor.vandurmedries.workers.dev" }
For comparison, send {"urls":["https://seller-one.example","https://seller-two.example/mcp"]}. Only public HTTP(S) endpoints are accepted. A batch can contain at most 20 URLs.
Output
{"target": "https://seller.example","ready": true,"score": 100,"grade": "A","checks": { "mcpHandshake": true, "toolsDiscoverable": true, "x402Discovery": true, "explicitPrices": true, "paymentNetwork": true },"mcp": { "toolCount": 3, "latencyMs": 118 },"recommendation": "Ready for autonomous buyers."}
Results are also pushed to the default dataset. You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.
Data table
| Field | Meaning |
|---|---|
score | Readiness score from 0 to 100 |
checks | Five independently verifiable buyer checks |
tools | MCP tool names, descriptions, and schemas |
x402.endpoints | Advertised paid routes, prices, and networks |
latencyMs | Observed response time during this run |
checkedAt | ISO timestamp for monitoring and comparisons |
Pricing / Cost estimation
This Actor is optimized for inexpensive HTTP checks and does not launch a browser. One request can audit up to 20 sellers, making batch monitoring more cost-efficient than separate crawls. Actual Store pricing is shown before each run; network latency and the number of targets determine runtime.
Advanced options
Use a seller's origin URL when MCP is hosted at /mcp, or provide the full MCP URL. Schedule a daily batch to detect outages, removed tools, changed schemas, or price/network changes. Treat the result as technical due diligence—not as a guarantee that a seller's content or business claims are correct.
FAQ, disclaimers, and support
The monitor only accesses public endpoints and never signs payments. It does not purchase products or expose paid results. Some MCP services require authentication and will correctly score as unavailable to anonymous buyers. Respect every target's terms and access policies. For bugs, edge cases, or custom marketplace integrations, use the Actor's Issues tab.