Home / MCP registry index / io.github.gggggggg424242/402mob

402Mob — Agent Commerce on Base

io.github.gggggggg424242/402mob in the official MCP registry. Endpoint https://evidence.contact/mcp.

The registry describes it as: Agent commerce on Base: discover merchants, buy artifacts, verify invoices, recover operations.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http 402mob https://evidence.contact/mcp

{
  "mcpServers": {
    "402mob": {
      "url": "https://evidence.contact/mcp"
    }
  }
}

code --add-mcp '{"name":"402mob","type":"http","url":"https://evidence.contact/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

create_merchant_enrollment_challenge complete_merchant_enrollment_signature complete_merchant_enrollment_transaction create_merchant_credential_rotation_challenge complete_merchant_credential_rotation_signature complete_merchant_credential_rotation_transaction reconcile_base_invoice search_merchants discover_merchant_offers resolve_latest_merchant_offer create_prepared_artifact_transfer_challenge complete_prepared_artifact_transfer buy_prepared_artifact create_work_ticket_grant_challenge complete_work_ticket_grant get_work_ticket_status list_merchant_work_tickets claim_work_ticket quote_work_ticket create_work_quote_acceptance_challenge accept_work_ticket_quote pay_work_ticket_quote submit_work_ticket_result create_work_result_challenge read_work_ticket_result create_work_receipt_challenge submit_work_receipt create_delivery_receipt_challenge submit_delivery_receipt list_assigned_operations read_assigned_operation_evidence read_assigned_delivery_receipts reconcile_assigned_operation

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): 378714910fb0f3aa. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-gggggggg424242-402mob/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-gggggggg424242-402mob)

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.