# com.marutap/marutap (remote · mcp.marutap.com)

Agent requests a purchase, the human taps approve, the agent gets a card scoped to it.

- Trust score: 65/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.marutap.com`: 65/100 (this document), [markdown](https://verifymcp.io/servers/com-marutap-marutap/mcp.md), [page](https://verifymcp.io/servers/com-marutap-marutap/mcp)

## Channel facts

- Endpoint: `https://mcp.marutap.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cancel_subscription).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-marutap-marutap 'https://mcp.marutap.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-marutap-marutap": {
      "url": "https://mcp.marutap.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-marutap-marutap": {
      "type": "http",
      "url": "https://mcp.marutap.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-marutap-marutap]
url = "https://mcp.marutap.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-marutap-marutap": {
      "type": "remote",
      "url": "https://mcp.marutap.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-marutap-marutap --url 'https://mcp.marutap.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-marutap-marutap:
    url: "https://mcp.marutap.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-marutap-marutap": {
      "Transport": "http",
      "Url": "https://mcp.marutap.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-marutap-marutap -t streamable-http -u 'https://mcp.marutap.com/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 65, +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.

### 2026-09-17 (score 64, +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.

### 2026-09-16 (score 63, 0)

- [functional regression] Schema quality: pass → fail
- [functional] New tool “list_payment_requests”

### 2026-09-15 (score 63, +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.

### 2026-09-13 (score 62, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-12 (score 61)

First indexed and scored.

## MCP tools (7)

### `request_payment` (~216 tokens)

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".

Input parameters:

- `amount` (number, required)
- `currency` (string)
- `line_items`
- `merchant` (string, required)

### `get_payment_result` (~177 tokens)

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.

Input parameters:

- `agent_secret` (string)
- `charge_id` (string, required)
- `wait_seconds` (integer)

### `list_payment_requests` (~183 tokens)

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.

Input parameters:

- `limit` (integer)
- `status` (string)

### `record_order` (~68 tokens)

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).

Input parameters:

- `charge_id` (string, required)
- `order_ref` (string, required)

### `request_subscription` (~154 tokens)

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".

Input parameters:

- `cap` (number, required)
- `interval` (string)
- `merchant` (string, required)

### `list_subscriptions` (~18 tokens)

List the user's subscription mandates and their status.

### `cancel_subscription` (~40 tokens)

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

Input parameters:

- `mandate_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-marutap-marutap/mcp#diagnostics

## Score history

- 2026-09-20: 65
- 2026-09-19: 65
- 2026-09-18: 64
- 2026-09-17: 64
- 2026-09-16: 63
- 2026-09-15: 63
- 2026-09-14: 62
- 2026-09-13: 62
- 2026-09-12: 61

## Common questions

### 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.

## Links

- Remote endpoint: https://mcp.marutap.com/mcp
- Repository: https://github.com/alexQueue/maruchit
- Website: https://marutap.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-marutap-marutap/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-marutap-marutap/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-marutap-marutap/mcp