Marutap MCP server

• Registry namecom.marutap/marutapverified in the MCP registry

The registry name sits under marutap.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-31
• Tools7
• Server calls itselfmarutap
• Protocol version2025-06-18

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

• Its tools do every use case we checked: approve agent purchases before any card is charged; cancel recurring subscriptions an agent set up.
• Checked on 3 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: 3 so far
• What an agent can do with it2 of 2 use cases
• Answeredmeasuring3 of the 7 daily checks it takes to print a share
• Median first answer130 ms
• Space in an agent's context≈ 1,256 tokensthe definitions of all its tools (7), which an agent carries on every turn
• Tool definitionsB · 86 of 100
• Typed results0 of 7 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 6 of 7

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 →

• request_payment

  Request the user's approval to pay for a purchase. Usually returns `{auto_approved: false, approval_url}` — show the approval_url to the user so they can review the total and approve with one tap, then call get_payment_result. If the…

• get_payment_result

  Poll for the outcome of a payment request. Long-polls up to wait_seconds. Returns status one of: pending, approved, settled, declined, expired, not_found, claim_pending. When approved, includes a single-use `card` (number, cvc, exp)…

• list_payment_requests

  List this agent's payment requests and whether each has been approved yet. Use this to see the state of every request you've made — not just poll one saved charge_id. Each item includes its `status` (pending, approved, settled, declined…

• record_order

  Report the merchant's order reference back after checkout, so the user can later reverse (refund) the purchase. `order_ref` is the merchant's payment id (e.g. a Stripe PaymentIntent).

• request_subscription

  Set up a recurring subscription mandate (e.g. Netflix at up to $16/month). Requires the user's explicit one-time approval — returns an approval_url. The mandate is merchant-locked and capped: the merchant can never charge more than `cap`…

• list_subscriptions

  List the user's subscription mandates and their status.

• cancel_subscription

  Cancel a subscription mandate. Safe — canceling never spends money, and the merchant can never charge again afterwards.