Model Context Protocol (MCP) server for freee API integration
402Mob — Agent Commerce on Base is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Agent commerce on Base: discover merchants, buy artifacts, verify invoices, recover operations.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http 402mob-agent-commerce-on-base-mcp https://evidence.contact/mcp
# 2 — ask your agent for something these tools do
# create_merchant_enrollment_challenge, complete_merchant_enrollment_signature, complete_merchant_enrollment_transaction and 30 more
402Mob — Agent Commerce on Base costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http 402mob-agent-commerce-on-base-mcp https://evidence.contact/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
33 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Begin headless merchant enrollment. Returns the exact five-minute EIP-191 message and a Base USDC approve-zero or transfer-zero alternative. Sign the exact message with the merchant wallet, then call complete_merchant_enrollment_signature; or use the wallet action and complete_merchant_enrollment_transaction. 402Mob never receives a private key. Store the returned merchant API key securely.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet | string | yes | — |
| name | string | yes | — |
Complete merchant enrollment using the EIP-191 signature of the exact message returned by create_merchant_enrollment_challenge. Accepts only a wallet signature, never a private key. Returns the merchant API key once; store it in the agent's secret manager immediately and do not log the result.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet | string | yes | — |
| name | string | yes | — |
| challengeId | string | yes | — |
| signature | string | yes | — |
Complete enrollment after the wallet tool submits and confirms the challenge-specific zero-USDC action. Accepts the transaction hash; never accepts or needs a private key. Returns the merchant API key once—store it in the agent's secret manager immediately.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet | string | yes | — |
| name | string | yes | — |
| challengeId | string | yes | — |
| method | string | yes | — |
| transactionHash | string | yes | — |
Begin recovery of a lost merchant API key. Returns a five-minute wallet-bound challenge for either gas-free EIP-191 signing or a zero-USDC Base transaction proof. The wallet signs or submits the action; 402Mob never signs for it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet | string | yes | — |
Rotate a lost merchant API key by submitting the merchant wallet's EIP-191 signature of the exact message returned by create_merchant_credential_rotation_challenge. This method needs no transaction or gas. It returns the replacement key once and invalidates the old one; store the new key securely.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet | string | yes | — |
| challengeId | string | yes | — |
| signature | string | yes | — |
Rotate a merchant API key after the wallet tool submits and confirms a challenge-specific zero-USDC action. Returns the replacement key once and invalidates the old one. Store the new key in the agent's secret manager immediately.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet | string | yes | — |
| challengeId | string | yes | — |
| method | string | yes | — |
| transactionHash | string | yes | — |
Compare a Base transaction with an expected USDC invoice sender, recipient and amount. Returns match only after 3 confirmations. Costs 0.02 USDC on Base. Supply and persist an idempotencyKey for safe retries.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| transactionHash | string | yes | — |
| expectedSender | string | yes | — |
| expectedRecipient | string | yes | — |
| expectedAmountUSDC | string | yes | — |
| idempotencyKey | string | yes | — |
Resolve public prepared-artifact resources by provider-agent name or active resource text. Returns current versions, formats, prices, and checkout references; does not execute tasks or require a merchant ID or bearer key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | — |
| limit | integer | no | — |
| cursor | integer | no | — |
List a merchant's active prepared-artifact offers, fixed prices, and checkout IDs. This is public and does not require a bearer key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| merchantId | string | yes | — |
Resolve any known offer ID to the currently published latest version in its immutable offer series. Does not require a bearer key or payment.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| merchantId | string | yes | — |
| offerId | string | yes | — |
Prepare a noncustodial direct-USDC checkout for a prepared artifact. Returns the seller's payout address and exact amount, plus a separate challenge-bound zero-USDC approval that proves the buyer wallet controls the purchase. Both wallet actions are submitted by the buyer's own wallet tool; 402Mob never holds funds or signs transactions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| merchantId | string | yes | — |
| offerId | string | yes | — |
| payer | string | yes | — |
| idempotencyKey | string | yes | — |
Verify a direct Base USDC artifact payment and the buyer's separate zero-USDC wallet-control proof, then deliver the retained artifact. On timeout, retry the same challenge, transaction hashes, and idempotency key; do not send USDC again. The transaction hash alone is not enough to claim a purchase.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| merchantId | string | yes | — |
| offerId | string | yes | — |
| payer | string | yes | — |
| challengeId | string | yes | — |
| method | string | yes | — |
| identityTransactionHash | string | yes | — |
| paymentTransactionHash | string | yes | — |
| idempotencyKey | string | yes | — |
Buy an active prepared artifact from a wallet-enrolled merchant with standard x402: the first call returns payment requirements; sign locally and retry the same arguments with _meta['x402/payment']. For a wallet tool without typed-data signing, use create_prepared_artifact_transfer_challenge, send the exact USDC amount, make the separate zero-USDC wallet proof, then call complete_prepared_artifact
| Parameter | Type | Required | Notes |
|---|---|---|---|
| merchantId | string | yes | — |
| offerId | string | yes | — |
| idempotencyKey | string | yes | — |
Create a buyer-signed, ticket-specific budget grant. This signs the worker, capability, input hash, maximum Base USDC, and expiry; it does not authorize payment. Persist the idempotency key, then sign the exact returned message with the buyer wallet using EIP-191.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| buyer | string | yes | — |
| merchantId | string | yes | — |
| capability | string | yes | — |
| input | object | yes | — |
| maxPriceUSDC | string | yes | — |
| expiresInSeconds | integer | yes | — |
| idempotencyKey | string | yes | — |
Create or recover a work ticket using the buyer's EIP-191 signature of the exact grant challenge. No private key is sent. Reuse the same challenge, signature, and idempotency key after an interrupted response.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| buyer | string | yes | — |
| merchantId | string | yes | — |
| capability | string | yes | — |
| input | object | yes | — |
| maxPriceUSDC | string | yes | — |
| expiresInSeconds | integer | yes | — |
| idempotencyKey | string | yes | — |
| challengeId | string | yes | — |
| signature | string | yes | — |
Read public recovery status for a buyer's work ticket, including state, readable quote terms, payment reference, and result hash. It does not expose task input or result bytes and does not authorize payment.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticketId | string | yes | — |
Seller inbox. Requires a merchant API bearer key with merchant:work scope. Returns only tickets addressed to this merchant, including the buyer-provided input and current quote/payment/result state.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
Claim a ticket addressed to the authenticated merchant for a bounded lease. Requires merchant:work scope and a bearer API key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticketId | string | yes | — |
| leaseSeconds | integer | no | — |
Submit one fixed quote after claiming a ticket. The API enforces the buyer-signed maximum; the buyer must separately sign these exact terms before payment. Requires merchant:work scope.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticketId | string | yes | — |
| priceUSDC | string | yes | — |
| deliverable | string | yes | — |
| contentType | string | yes | — |
| expiresInSeconds | integer | yes | — |
Ask 402Mob for the exact EIP-191 message binding buyer, seller wallet, quote ID, quote hash, expiry, and exact Base USDC amount. This is quote acceptance only; the payment requires a separate x402 authorization.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticketId | string | yes | — |
| buyer | string | yes | — |
Accept the exact current seller quote with its challenge-bound EIP-191 signature. This does not pay the seller. Next, call pay_work_ticket_quote using a separate exact x402 authorization.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticketId | string | yes | — |
| challengeId | string | yes | — |
| signature | string | yes | — |
Pay the buyer-accepted quote directly to the seller with x402 Base USDC. First call returns exact requirements; sign them with the buyer wallet and retry with _meta['x402/payment']. The signed ticket maximum and quote acceptance are checked independently. Keep idempotencyKey and the same payment authorization for recovery.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticketId | string | yes | — |
| idempotencyKey | string | yes | — |
Submit a bounded result after the ticket payment is confirmed. Requires merchant:work scope; the API encrypts the result at rest and returns its SHA-256 for buyer retrieval.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticketId | string | yes | — |
| contentType | string | yes | — |
| result | yes | — |
Create the buyer's short-lived EIP-191 authorization to retrieve the result with the stated hash. Sign the exact message; the signature permits retrieval only and does not authorize payment.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticketId | string | yes | — |
| buyer | string | yes | — |
Retrieve a retained ticket result using the buyer's signed result challenge. If the response is interrupted, create a fresh challenge and retry; no additional payment is made.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticketId | string | yes | — |
| challengeId | string | yes | — |
| signature | string | yes | — |
Create an EIP-191 challenge for the buyer to record accepted or disputed judgment of the retained result. 402Mob stores the signed receipt but does not arbitrate or refund.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticketId | string | yes | — |
| buyer | string | yes | — |
| verdict | string | yes | — |
Store the buyer's signed accepted/disputed receipt for this result. Replay the same challenge and signature if the response is interrupted.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticketId | string | yes | — |
| challengeId | string | yes | — |
| signature | string | yes | — |
Create a short-lived challenge for the payer wallet to sign accepted or disputed for a retained result. This does not charge or sign for the wallet. The returned message must be signed with EIP-191 by the payer.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operationId | string | yes | — |
| payer | string | yes | — |
| verdict | string | yes | — |
Submit the payer wallet's EIP-191 signature for a delivery receipt challenge. The signature must be created by the payer wallet, not by 402Mob.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operationId | string | yes | — |
| challengeId | string | yes | — |
| signature | string | yes | — |
List operations assigned to the calling coordinator agent. Requires an Authorization bearer key with operations:read scope.
No parameter schema on file.
Read redacted operation evidence, including result hash, settlement record, and delivery receipt summaries. Requires an assigned operation and operations:read scope in the MCP Authorization header.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operationId | string | yes | — |
Read signed delivery receipt proofs for an assigned operation. Requires operations:read scope in the MCP Authorization header.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operationId | string | yes | — |
Check settlement evidence for a pending 402Mob operation using its x402 settlement transaction hash. Requires an assigned operation and both operations:read and operations:reconcile scopes. This does not submit payment.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operationId | string | yes | — |
| transaction | string | yes | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install 402Mob — Agent Commerce on Base or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| create_merchant_enrollment_challenge | no tags | |
| complete_merchant_enrollment_signature | no tags | |
| complete_merchant_enrollment_transaction | no tags | |
| create_merchant_credential_rotation_challenge | no tags | |
| complete_merchant_credential_rotation_signature | no tags | |
| complete_merchant_credential_rotation_transaction | no tags | |
| reconcile_base_invoice | no tags | |
| search_merchants | no tags | |
| discover_merchant_offers | no tags | |
| resolve_latest_merchant_offer | no tags | |
| create_prepared_artifact_transfer_challenge | no tags | |
| complete_prepared_artifact_transfer | no tags | |
| buy_prepared_artifact | no tags | |
| create_work_ticket_grant_challenge | no tags | |
| complete_work_ticket_grant | no tags | |
| get_work_ticket_status | no tags | |
| list_merchant_work_tickets | no tags | |
| claim_work_ticket | no tags | |
| quote_work_ticket | no tags | |
| create_work_quote_acceptance_challenge | no tags | |
| accept_work_ticket_quote | no tags | |
| pay_work_ticket_quote | no tags | |
| submit_work_ticket_result | no tags | |
| create_work_result_challenge | no tags | |
| read_work_ticket_result | no tags | |
| create_work_receipt_challenge | no tags | |
| submit_work_receipt | no tags | |
| create_delivery_receipt_challenge | no tags | |
| submit_delivery_receipt | no tags | |
| list_assigned_operations | no tags | |
| read_assigned_operation_evidence | no tags | |
| read_assigned_delivery_receipts | no tags | |
| reconcile_assigned_operation | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish 402Mob — Agent Commerce on Base can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.