Home / MCP registry index / com.synthexforge.x402/paid-agent-services
Synthex Forge — x402 Paid Agent Services
com.synthexforge.x402/paid-agent-services in the official MCP registry.
Endpoint https://x402.synthexforge.com/mcp. Source: github.com/hermeschoosenone-debug/synthex-x402.
The registry describes it as: Paid agent services settled in USDC on Base via x402. Signed, verifiable, and free to verify.
We read its 123 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
api_ebook_download bio_catalogue rates_reference signed_research_get social_search a2a_escrow a2a_settlement reputation_lookup trusted_route_lookup agent_handoff agent_run audit_evidence_package bestex_evidence bio_audit_receipts bio_audit_verify bio_compliance_query bio_labassets_reconcile bio_labcyber_events bio_outbreak_events bio_provenance_verify bio_research_reviews bio_risk_assess bio_trust_providers bio_verification_checks bio_workflows budget_preflight bureau_audit bureau_receipt_check bureau_reputation compliance_check containment_register contract_term_extract corpus_anchor counterparty_score credentials_issue data_c2pa_verify data_freshness data_signed_snapshot data_validate decision_attest delivery_attest dispute_ruling edge_prior edge_replication forensics_ingest forensics_query attested_financial_evidence finance_precision fund_tearsheet governance_reserve governance_settle identity_agent_attest identity_control_proof index_x402 invoice_ocr latency_benchmark licence_check mandate_compliance market_calendar market_history and 63 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-synthexforge-x402-paid-agent-services)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.
Related
| The Stall ai.intuitek.the-stall/the-stall | 200 tools, nothing matched 2026-10-22 |
| SAP MCP Server ai.oobeprotocol.sap.mcp/sap-mcp | 200 tools, nothing matched 2026-10-22 |
| Citiview Agent Market com.citiviewgroup.mcp/agent-market | 200 tools, nothing matched 2026-10-26 |
| ScorpTech x402 API com.it.scorptech/x402 | 200 tools, nothing matched 2026-10-26 |
| Apex Edge — x402-paid machine services dev.pages.nonsynthetic/apex-edge | 200 tools, nothing matched 2026-10-23 |
| io.github.praneeth12098/x402-factory io.github.praneeth12098/x402-factory | 200 tools, nothing matched 2026-10-26 |