# PlainRouter (remote · plainrouter.com)

Inspect an approved ad account and first-party signal health, then propose policy-gated actions.

- Trust score: 80/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

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

## Channel facts

- Endpoint: `https://plainrouter.com/mcp/sandbox`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.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**: 63/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 4 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.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 534 tokens (~106/item across 5 items; 4 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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).
  - Supports UI / widget rendering.

## Install

### How do I install the PlainRouter MCP server?

PlainRouter is a hosted endpoint at https://plainrouter.com/mcp/sandbox, 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-plainrouter-mcp 'https://plainrouter.com/mcp/sandbox'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-plainrouter-mcp": {
      "type": "http",
      "url": "https://plainrouter.com/mcp/sandbox"
    }
  }
}
```

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-20 (score 80, +1)

- [functional regression] Schema quality: 93 → 106
- [cosmetic] “get_performance” added an optional parameter “account_id”
- [cosmetic] “get_account_state” added an optional parameter “account_id”
- [cosmetic] “get_signal_health” added an optional parameter “account_id”

### 2026-09-18 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 78, 0)

- [functional] MCP protocol: Implements a current MCP spec version (2026-07-28).
- [functional] MCP protocol version: 2025-11-25 → 2026-07-28
- [functional] Server version: 0.3.2 → 0.4.0

### 2026-09-16 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 76, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] The server changed its declared name: PlainRouter Sandbox → Plainrouter Sandbox
- [security] Tool “validate_sandbox_event” rewrote its description, which is the text the model reads

### 2026-09-11 (score 75, 0)

- [cosmetic] “get_signal_health” added an optional parameter “days”

### 2026-09-10 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (4)

### `get_account_state` (~66 tokens)

Sandbox Account State

Synthetic twin of the production tool. Returns an invented advertising account in the real response shape, marked "sandbox": true. Requires no account, API key, or OAuth flow.

Input parameters:

- `account_id` (integer): Advertising account ID. Required when the workspace has more than one active account.

### `get_signal_health` (~88 tokens)

Sandbox Signal Health

Synthetic twin of the production tool. Returns invented Signal health in the real response shape, marked "sandbox": true. Requires no account, API key, or OAuth flow.

Input parameters:

- `account_id` (integer): Advertising account ID. Required when the workspace has more than one active account.
- `days` (integer): Trailing window in days. One of 7, 30, 90.

### `get_performance` (~85 tokens)

Sandbox Performance

Synthetic twin of the production tool. Returns invented reconciliation evidence in the real response shape, marked "sandbox": true. Requires no account, API key, or OAuth flow.

Input parameters:

- `account_id` (integer): Advertising account ID. Required when the workspace has more than one active account.
- `days` (integer): Number of reporting days to compare, from 1 to 90.

### `validate_sandbox_event` (~150 tokens)

Validate Sandbox Event

Validate a synthetic, identity-free conversion event against the Plainrouter schema. Requires no account, API key, or OAuth flow. Nothing is stored and nothing is sent to an advertising provider. Use this to confirm the server is reachable and that an event payload is well formed before requesting credentials.

Input parameters:

- `action_source` (string): Where the synthetic event originated: website, app, or other.
- `event_id` (string): Optional synthetic idempotency key. Maximum 128 characters. One is derived when omitted.
- `event_name` (string, required): Synthetic event name, such as Purchase. Maximum 100 characters.
- `value_data` (object): Optional synthetic commerce data. Identity-bearing fields are rejected.

## Diagnostics

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

## Score history

- 2026-09-20: 80
- 2026-09-19: 79
- 2026-09-18: 79
- 2026-09-17: 78
- 2026-09-16: 78
- 2026-09-15: 77
- 2026-09-14: 77
- 2026-09-13: 76
- 2026-09-12: 76
- 2026-09-11: 75
- 2026-09-10: 75
- 2026-09-09: 74
- 2026-09-08: 74
- 2026-09-07: 73
- 2026-09-06: 73
- 2026-09-05: 72
- 2026-09-04: 72
- 2026-09-03: 71
- 2026-09-02: 71
- 2026-09-01: 70
- 2026-08-31: 70
- 2026-08-30: 69
- 2026-08-29: 69
- 2026-08-28: 68
- 2026-08-27: 68

## Common questions

### What is the PlainRouter MCP server?

PlainRouter is an MCP server listed in the public MCP registry as com.plainrouter/mcp. Inspect an approved ad account and first-party signal health, then propose policy-gated actions. This page covers its hosted endpoint (https://plainrouter.com/mcp/sandbox).

### Is the PlainRouter MCP server safe to use?

PlainRouter scores 80 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 PlainRouter MCP server expose?

PlainRouter exposes 4 tools: get_account_state, get_signal_health, get_performance, validate_sandbox_event. Their descriptions and schemas cost roughly 389 tokens of context every time the server is loaded.

### Does the PlainRouter MCP server require authentication?

No. We connected to PlainRouter without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the PlainRouter MCP server still maintained?

PlainRouter 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://plainrouter.com/mcp/sandbox
- Repository: https://github.com/plainrouter/sdk
- Website: https://plainrouter.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-plainrouter-mcp/mcp-sandbox.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-plainrouter-mcp/mcp-sandbox.json
- HTML version of this page: https://verifymcp.io/servers/com-plainrouter-mcp/mcp-sandbox