Other · Remote MCP server
Marutap
Agent requests a purchase, the human taps approve, the agent gets a card scoped to it.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.marutap/marutap- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-11
- Updated
- 2026-09-11
- Publisher
- com.marutap
- Namespace
- Namespace verified by the MCP Registry via the domain marutap.com · how
- Website
- marutap.com
- Repository
- github.com/alexQueue/maruchit
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.marutap.com/mcp | Authorization (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- marutap · protocol 2025-06-18
- Tools discovered
- 7:
request_payment,get_payment_result,list_payment_requests,record_order,request_subscription,list_subscriptions,cancel_subscription - Checked on
- 2026-10-05
How to connect Marutap
Marutap is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.marutap.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| MarrowEvidence-grounded, graph-connected, correctable memory for agents. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |
| MarrowRuntime governance, proof, outcome closure, and fleet intelligence for MCP-compatible AI agents. | Local · stdio |
| MarsNMeAgent-agnostic memory backend that preserves continuity between humans and AI over time. | Local · HTTP |
| MartiniManage AI filmmaking projects, scenes, assets, and generations in Martini. | Remote · HTTPLive check: sign-in required |
| Marz Greta Lock NetworkEQ scoring plus a read-only Storelayer matcher and guarded self-install; no website credentials. | Remote · HTTPLive check: ✓ handshake |
| Marz Greta Lock NetworkHuman-likeness scoring of AI text vs 12 real personality profiles; free tools + x402 paid tier. | Remote · HTTPLive check: ✓ handshake |
| MascotlineOne mascot, locked once, drawn in any scene on demand and checked against its own identity. | Remote · HTTPLive check: sign-in required |
| MaskFlow PII proxyMask PII in outbound MCP tool-call arguments, unmask the results. Indian identifiers included. | Local · stdio |