x402check vs Agent Services (x402): compliance, company, procurement
x402check is an MCP server published by caiovicentino. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Agent Services (x402): compliance, company, procurement is an MCP server published by pcp183. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  x402check | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.3.3 Downloads/month (npm): 1 871 Downloads/week (npm): 425 Forks (GitHub): 2 Stars (GitHub): 12 Not marked · First seen |
Listed Version: 0.1.0 No figure published Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 0.3.3 Downloads/month (npm): 1 871 Downloads/week (npm): 425 Forks (GitHub): 2 Stars (GitHub): 12 Not marked · First seen |
Not listed |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | x402check | Agent Services (x402): compliance, company, procurement |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 12 | No figure on GitHub |
| Forks (GitHub) (differs) | 2 | No figure on GitHub |
| Last release (differs) | 2026-10-23 | Not published |
| Where it runs (differs) | On your machine (@x402check/mcp) | Remote server (agent-services-mcp-production.up.railway.app/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 2 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/caiovicentino/jev-risk-check-provider | github.com/pcp183/agent-services-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-17 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 46 h ago returned HTTP 404 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
x402check
Risk-check counterparties before an AI agent pays; pay x402 resources only after a verified allow
Agent Services (x402): compliance, company, procurement
27 pay-per-call agent tools (KYB, VAT, sanctions, tenders, data). Pays via x402; holds no funds.
How to run each
x402check As a local MCP server: npm package
claude mcp add --env "X402CHECK_CREDIT_TOKEN=<YOUR_X402CHECK_CREDIT_TOKEN>" --env "X402CHECK_PAYER_KEY=<YOUR_X402CHECK_PAYER_KEY>" --transport stdio x402check -- npx -y @x402check/mcpRequires: X402CHECK_CREDIT_TOKEN (secret), X402CHECK_PAYER_KEY (secret)
Agent Services (x402): compliance, company, procurement As a remote MCP server
claude mcp add --transport http agent-services-mcp https://agent-services-mcp-production.up.railway.app/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Agent Services (x402): compliance, company, procurement has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Agent Services (x402): compliance, company, procurement publish no settings it asks for, so we do not compare settings.
What it can do: x402check · What it can do: Agent Services (x402): compliance, company, procurement · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.