com.marutap/marutap
REMOTE · MCP.MARUTAP.COM · SCANNED SEP 20
Agent requests a purchase, the human taps approve, the agent gets a card scoped to it.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cancel_subscription). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 856 tokens (~122/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the com.marutap/marutap MCP server?
com.marutap/marutap is a hosted endpoint at https://mcp.marutap.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.marutap.com
claude mcp add --transport http com-marutap-marutap 'https://mcp.marutap.com/mcp'
{
"mcpServers": {
"com-marutap-marutap": {
"url": "https://mcp.marutap.com/mcp"
}
}
} {
"servers": {
"com-marutap-marutap": {
"type": "http",
"url": "https://mcp.marutap.com/mcp"
}
}
} [mcp_servers.com-marutap-marutap] url = "https://mcp.marutap.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-marutap-marutap": {
"type": "remote",
"url": "https://mcp.marutap.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-marutap-marutap --url 'https://mcp.marutap.com/mcp' --transport streamable-http
mcp_servers:
com-marutap-marutap:
url: "https://mcp.marutap.com/mcp" {
"McpServers": {
"com-marutap-marutap": {
"Transport": "http",
"Url": "https://mcp.marutap.com/mcp"
}
}
} assistant mcp add com-marutap-marutap -t streamable-http -u 'https://mcp.marutap.com/mcp'
{
"mcpServers": {
"com-marutap-marutap": {
"type": "http",
"url": "https://mcp.marutap.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 0
- Schema quality: pass → fail ▼ functional
- New tool “list_payment_requests” functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Sept 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.marutap.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.marutap.com | CN=WE1,O=Google Trust Services,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | fc39d5b4b875f2d8136c221bf4fba0cb |
| SANs: mcp.marutap.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.marutap.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| marutap.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.marutap.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.marutap.com/mcp | HTTPS enforced | 301 | https://mcp.marutap.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cancel_subscription ~40
Cancel a subscription mandate. Safe — canceling never spends money, and the merchant can never charge again afterwards.
| Name | Type | Req | Description |
|---|---|---|---|
| mandate_id | string | yes | – |
No output schema declared.
No examples provided.
get_payment_result ~177
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) 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_secret | string | – | – |
| charge_id | string | yes | – |
| wait_seconds | integer | – | – |
No output schema declared.
No examples provided.
list_payment_requests ~183
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, 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
list_subscriptions ~18
List the user's subscription mandates and their status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
record_order ~68
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).
| Name | Type | Req | Description |
|---|---|---|---|
| charge_id | string | yes | – |
| order_ref | string | yes | – |
No output schema declared.
No examples provided.
request_payment ~216
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 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".
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | – |
| currency | string | – | – |
| line_items | – | – | – |
| merchant | string | yes | – |
No output schema declared.
No examples provided.
request_subscription ~154
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` 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".
| Name | Type | Req | Description |
|---|---|---|---|
| cap | number | yes | – |
| interval | string | – | – |
| merchant | string | yes | – |
No output schema declared.
No examples provided.
What is the com.marutap/marutap MCP server?
com.marutap/marutap is an MCP server listed in the public MCP registry as com.marutap/marutap. Agent requests a purchase, the human taps approve, the agent gets a card scoped to it. This page covers its hosted endpoint (https://mcp.marutap.com/mcp).
Is the com.marutap/marutap MCP server safe to use?
com.marutap/marutap scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.marutap/marutap MCP server expose?
com.marutap/marutap exposes 7 tools: request_payment, get_payment_result, list_payment_requests, record_order, request_subscription, and 2 more. Their descriptions and schemas cost roughly 856 tokens of context every time the server is loaded.
Does the com.marutap/marutap MCP server require authentication?
No. We connected to com.marutap/marutap without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.marutap/marutap MCP server still maintained?
com.marutap/marutap is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.