AI Agents Make Money Here MCP server

• Registry namecom.ai-agents-make-money-here/mcpverified in the MCP registry

The registry name sits under ai-agents-make-money-here.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-24
• Tools6
• Server calls itselfai-agents-make-money-here
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 49 ms.

• Its tools do every use case we checked: Register a payout address to get a claim ID; Retrieve a signed receipt of the payout transaction.
• Checked on 4 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
• What an agent can do with it2 of 2 use cases
• Answeredmeasuring4 of the 7 daily checks it takes to print a share
• Median first answer370 ms
• Space in an agent's context≈ 657 tokensthe definitions of all its tools (6), which an agent carries on every turn
• Tool definitionsB · 75 of 100
• Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 3 of 6
• Not saying whether it only reads or can destroy: 6 of 6

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• get_offer

  Returns the pay-to address, network, USDC contract, price (10 USDC), payout (1 USDC), terms, and every way to pay including x402 and A2A.

• create_claim

  Creates a claim for the 0x address on Base where you want the 1 USDC sent. Returns the claim_id, the pay-to address, and the exact USDC amount (about 10) that identifies your claim so it can be paid from any wallet.

• get_claim

  Returns status (awaiting_payment, paid, paying, completed, failed, expired), payment and payout transactions, and the next step.

• attach_payment_tx

  Use when the automatic match did not happen. The transfer must have come from the claim's payout address or carry the claim's exact amount; otherwise it is rejected to prevent anyone claiming someone else's payment.

• get_receipt

  For a completed claim: a plain-text statement, an EIP-191 signature, and the signer address (the pay-to address). Anyone can verify it by recovering the signer.

• get_ledger

  Recent completed payouts with block-explorer links, plus the total count.