Where it fits
Compliance and finance teams that need deterministic identifier checks with verifiable receipts, plus anyone who has to validate a code402 receipt later.
- Verify a signed receipt JSON with the local x402_verify tool.
- Run an IBAN or VAT check against the hosted hcrb.in/mcp service.
- Run a revenue-module check and keep its signed receipt.
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with code402
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Investigates a question against high-trust primary sources and records the findings in a Markdown file inside the repo. Use it when a topic needs research, docs or API facts need gathering, or reading legwork should go to a background agent.
Show recorded token use, cache reads, and mode attribution for the current Claude Code session.
Improves application speed across the frontend, backend, database, and query layers. Reach for it when a performance target exists, a regression is suspected, Core Web Vitals or load times need work, N+1 queries need fixing, or profiling has exposed a bottleneck.
No skills found
Try a different search term or clear the filters.
Free receipt verifier (local stdio)
The package exposes one tool, x402_verify, which takes { raw_receipt } and validates the signature. Identifier checks run against the hosted hcrb.in/mcp endpoint, not this package.
npx -y @code402/verify-mcp@latestFollow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.
Endpoint and configuration
The installer uses the server name code402. If you add the endpoint by hand, keep the same name so the guide and your config match.
Check the connection
After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.
- 1Open the tool list.
Restart the client or start a new session. Confirm that
code402appears and that the tools match the provider documentation. - 2Run one small request.
Start with: Verify a signed receipt JSON with the local x402_verify tool. Check the result before you give the server more access.
- 3Check permissions.
Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.
We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
- The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
- Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Before you connect
- The provider can see the requests and data your agent sends through the server.
- Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
- Use project scope for repository-specific servers; use global scope for personal tools.
- Remove the server and revoke its token when you stop using it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.
Provider source
Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.
code402 repositoryhttps://github.com/89rat/code402-verify-mcp