marutap
com.marutap/marutapVersion 1.0.0Agent requests a purchase, the human taps approve, the agent gets a card scoped to it.
Status
Responds327 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:05 UTC
- Latency
- 327 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://mcp.marutap.com/mcpResponds327 msNo sign-in
Claude Code
claude mcp add --transport http marutap https://mcp.marutap.com/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: marutap
Remote MCP server URL: https://mcp.marutap.com/mcpCursor
{
"mcpServers": {
"marutap": {
"url": "https://mcp.marutap.com/mcp"
}
}
}VS Code
code --add-mcp '{"name":"marutap","type":"http","url":"https://mcp.marutap.com/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
7 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
cancel_subscriptionCancel a subscription mandate. Safe — canceling never spends money, and the merchant can
never charge again afterwards. | Yes | No | Yes | No |
get_payment_resultPoll 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) locked to this purchase — use it to complete checkout at
the merchant. If still "pending"/"claim_pending", call again.
For a claim (charge_id = the "clm_…" poll_id from request_payment): pass the
agent_secret you received. The first approved result also contains `connect_token` —
persist it and send it as the Authorization bearer on all future calls.
| No | Yes | No | No |
list_payment_requestsList 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,
expired) so you can tell which are still waiting and which the user has acted on.
For a pending request it also returns the `approval_url` (re-surface it to the user);
once a request is approved, call get_payment_result(charge_id) to fetch the card.
Args:
status: which to return — "open" (default, still-pending only) or "all".
limit: max requests to return (default 20, capped at 100), newest first.
| No | Yes | Yes | No |
list_subscriptionsList the user's subscription mandates and their status. | No | Yes | Yes | No |
record_orderReport 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).
| No | No | Yes | No |
request_paymentRequest 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 user's spending policy auto-approves this purchase (e.g. under their cap at an
allowlisted merchant), it returns `{auto_approved: true, status: "approved", card}` immediately
— no approval needed, just use the card.
Args:
amount: Total to charge, in major units (e.g. 18.50 dollars).
merchant: Human-readable merchant / store name shown on the approval screen.
line_items: Optional list of {"name": str, "quantity": int, "amount_cents": int}.
currency: ISO currency code, default "usd".
| No | No | No | Yes |
request_subscriptionSet 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` per period, and the
user can cancel anytime (after which the merchant can never charge again).
Args:
merchant: merchant to authorize (e.g. "Netflix").
cap: max amount per period in major units (e.g. 16.00).
interval: "weekly" | "monthly" | "yearly".
| No | No | No | Yes |
Details
- Registry status
- Active
- Published
- Sep 11, 2026
- Updated
- Sep 11, 2026
- Categories (suggested)
- Finance and paymentsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared