# Rooms Agent Pay (sandbox preview) (remote · rooms-agent-pay-live.pages.dev)

Give your AI a budget, not your card: fund a room, set an approval line, AI hires over MCP. Sandbox.

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

## Components

- remote · `rooms-agent-pay-live.pages.dev`: 63/100 (this document), [markdown](https://verifymcp.io/servers/com-aurmada-rooms-agent-pay/rooms-agent-pay-live.md), [page](https://verifymcp.io/servers/com-aurmada-rooms-agent-pay/rooms-agent-pay-live)

## Channel facts

- Endpoint: `https://rooms-agent-pay-live.pages.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.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-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 70/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 628 tokens (~89/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 19/100
  - Stability check failed: schema churn in the 10 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 85% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "request_refund" implies "refund" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Rooms Agent Pay (sandbox preview) MCP server?

Rooms Agent Pay (sandbox preview) is a hosted endpoint at https://rooms-agent-pay-live.pages.dev/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-aurmada-rooms-agent-pay 'https://rooms-agent-pay-live.pages.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-aurmada-rooms-agent-pay": {
      "url": "https://rooms-agent-pay-live.pages.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-aurmada-rooms-agent-pay": {
      "type": "http",
      "url": "https://rooms-agent-pay-live.pages.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-aurmada-rooms-agent-pay]
url = "https://rooms-agent-pay-live.pages.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-aurmada-rooms-agent-pay": {
      "type": "remote",
      "url": "https://rooms-agent-pay-live.pages.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-aurmada-rooms-agent-pay --url 'https://rooms-agent-pay-live.pages.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-aurmada-rooms-agent-pay:
    url: "https://rooms-agent-pay-live.pages.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-aurmada-rooms-agent-pay": {
      "Transport": "http",
      "Url": "https://rooms-agent-pay-live.pages.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-aurmada-rooms-agent-pay -t streamable-http -u 'https://rooms-agent-pay-live.pages.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-aurmada-rooms-agent-pay": {
      "type": "http",
      "url": "https://rooms-agent-pay-live.pages.dev/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-11-21 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 16 to 19.

### 2026-11-19 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 9 to 13.

### 2026-11-17 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 6.

### 2026-11-12 (score 60, 0)

- [security regression] Stability: unverified → fail
- [security regression] A breaking change shipped without a version bump: still 0.2.0
- [security regression] Tool “sandbox_fund_with_test_card” was removed
- [functional improvement] Schema quality: 716 → 628
- [functional improvement] Tool coverage: 80% → 85%

### 2026-11-11 (score 60)

First indexed and scored.

## MCP tools (7)

### `create_room` (~148 tokens)

Open a Rooms Agent Pay room for a goal with a budget (USD) and an approval line. Returns one ready-to-pay link the human opens to fund it with PayPal or a card (SANDBOX: no real money). Unspent budget stays in the room as credit for the next hire.

Input parameters:

- `approval_line` (number): Hires above this USD amount wait for the owner's OK
- `cap` (number, required): Budget in USD to put in the room (minimum applies, e.g. 25)
- `email` (string): Funder email (optional; first room's fee is waived for a new email)
- `goal` (string, required): What the room should get done

### `room_status` (~38 tokens)

Room balance, spent, fees, refundable amount, hires and the latest transcript lines.

Input parameters:

- `room_id` (string, required): Room id from create_room

### `hire_specialist` (~109 tokens)

Hire a house specialist (research, copy or design) for a brief, paid from the room balance. Runs immediately and settles after verification, unless the price is over the approval line (then it waits for approve_hire).

Input parameters:

- `brief` (string, required): Exactly what to deliver
- `max_price` (number): Max USD for this hire
- `owner_key` (string, required): Owner key returned by create_room (keep it private)
- `room_id` (string, required): Room id from create_room

### `approve_hire` (~72 tokens)

Approve a hire that is over the approval line; it then runs and is paid from the room balance after verification.

Input parameters:

- `hire_id` (string, required)
- `owner_key` (string, required): Owner key returned by create_room (keep it private)
- `room_id` (string, required): Room id from create_room

### `decline_hire` (~62 tokens)

Decline a hire that is waiting for approval. No money moves.

Input parameters:

- `hire_id` (string, required)
- `owner_key` (string, required): Owner key returned by create_room (keep it private)
- `room_id` (string, required): Room id from create_room

### `close_room` (~62 tokens)

Close the current mission. The unspent balance stays in the room as credit for next time (no automatic refund).

Input parameters:

- `owner_key` (string, required): Owner key returned by create_room (keep it private)
- `room_id` (string, required): Room id from create_room

### `request_refund` (~76 tokens)

Owner asks for the refundable balance back (within the refund window of funding, minus the PayPal processing fee). Reviewed and approved manually by Rooms.

Input parameters:

- `owner_key` (string, required): Owner key returned by create_room (keep it private)
- `reason` (string)
- `room_id` (string, required): Room id from create_room

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-aurmada-rooms-agent-pay/rooms-agent-pay-live#diagnostics

## Score history

- 2026-11-21: 63
- 2026-11-20: 62
- 2026-11-19: 62
- 2026-11-18: 61
- 2026-11-17: 61
- 2026-11-16: 60
- 2026-11-15: 60
- 2026-11-14: 60
- 2026-11-13: 60
- 2026-11-12: 60
- 2026-11-11: 60

## Common questions

### What is the Rooms Agent Pay (sandbox preview) MCP server?

Rooms Agent Pay (sandbox preview) is an MCP server listed in the public MCP registry as com.aurmada.rooms/agent-pay. Give your AI a budget, not your card: fund a room, set an approval line, AI hires over MCP. Sandbox. This page covers its hosted endpoint (https://rooms-agent-pay-live.pages.dev/mcp).

### Is the Rooms Agent Pay (sandbox preview) MCP server safe to use?

Rooms Agent Pay (sandbox preview) scores 63 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 Rooms Agent Pay (sandbox preview) MCP server expose?

Rooms Agent Pay (sandbox preview) exposes 7 tools: create_room, room_status, hire_specialist, approve_hire, decline_hire, and 2 more. Their descriptions and schemas cost roughly 567 tokens of context every time the server is loaded.

### Does the Rooms Agent Pay (sandbox preview) MCP server require authentication?

No. We connected to Rooms Agent Pay (sandbox preview) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Rooms Agent Pay (sandbox preview) MCP server still maintained?

Rooms Agent Pay (sandbox preview) is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Rooms Agent Pay (sandbox preview) MCP server?

VerifyMCP ran 12 checks on Rooms Agent Pay (sandbox preview), covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Rooms Agent Pay (sandbox preview): Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://rooms-agent-pay-live.pages.dev/mcp
- Website: https://rooms-agent-pay-live.pages.dev/?utm_source=mcp-registry
- Changelog RSS feed: https://verifymcp.io/servers/com-aurmada-rooms-agent-pay/rooms-agent-pay-live.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-aurmada-rooms-agent-pay/rooms-agent-pay-live/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-aurmada-rooms-agent-pay/rooms-agent-pay-live.json
- HTML version of this page: https://verifymcp.io/servers/com-aurmada-rooms-agent-pay/rooms-agent-pay-live
