Other · Local MCP server
x402check
Risk-check counterparties before an AI agent pays; pay x402 resources only after a verified allow.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.caiovicentino/x402check- Version
- 0.3.0
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-30
- Updated
- 2026-09-30
- Publisher
- caiovicentino (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/caiovicentino) · how
- Website
- x402check.xyz
- Repository
- github.com/caiovicentino/jev-risk-check-provider (folder packages/mcp)
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @x402check/mcp | 0.3.0 | stdio |
How to connect x402check
x402check runs locally from a Node.js package published to the npm registry: @x402check/mcp version 0.3.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @x402check/mcp@0.3.0. It reads these environment variables: X402CHECK_CREDIT_TOKEN (secret), X402CHECK_PAYER_KEY (secret), X402CHECK_BUDGET_USD, X402CHECK_PINNED_KEYS and X402CHECK_MAX_PAYMENT_USD; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"x402check": {
"command": "npx",
"args": [
"-y",
"@x402check/mcp@0.3.0"
],
"env": {
"X402CHECK_CREDIT_TOKEN": "<secret>",
"X402CHECK_PAYER_KEY": "<secret>",
"X402CHECK_BUDGET_USD": "<value>",
"X402CHECK_PINNED_KEYS": "<value>",
"X402CHECK_MAX_PAYMENT_USD": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| X402 Tools MCPMelis x402 Tools - 22 pay-per-call APIs for AI agents. No accounts, no API keys. USDC on Base. | Local · stdio |
| x402 Universal PayerPay any x402 endpoint on the open web: auto-paying bridge with Bazaar discovery and spend caps. | Local · stdio |
| x402-marketLet AI agents pay-per-call for any HTTP API via x402 on Base mainnet. One tool: pay_and_call. | Local · stdio |
| x402-vend - WebIntelPay-per-call web & EU business intelligence for AI agents (x402 USDC on Base). 11 tools. | Remote · HTTPLive check: ✓ handshake |
| x402receiptsRecord x402 agent purchases as reconciled, auditable receipts; verify any receipt on the ledger. | Local · stdio |
| X402stationX402station.io: independent risk-signal layer for x402 endpoints before agents pay. | Local · stdio |
| X402watchWash-filtered intelligence for x402: categories, services, wash analysis, trends. | Remote · HTTPLive check: ✓ handshake |
| X4CodeSenseX4: Foundations scripts: checks, schema elements, expression types, scripts, cues and texts. | Local · stdio |