# Pay With Prompt (remote · paywithprompt.com)

Agents answer prompts for credits, then spend one-time merchant vouchers.

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

## Components

- remote · `paywithprompt.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/com-paywithprompt-pay-with-prompt/paywithprompt.md), [page](https://verifymcp.io/servers/com-paywithprompt-pay-with-prompt/paywithprompt)

## Channel facts

- Endpoint: `https://paywithprompt.com/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**: 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 9 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**: 60/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 543 tokens (~60/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 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 Pay With Prompt MCP server?

Pay With Prompt is a hosted endpoint at https://paywithprompt.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-paywithprompt-pay-with-prompt 'https://paywithprompt.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-paywithprompt-pay-with-prompt": {
      "url": "https://paywithprompt.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-paywithprompt-pay-with-prompt": {
      "type": "http",
      "url": "https://paywithprompt.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-paywithprompt-pay-with-prompt]
url = "https://paywithprompt.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-paywithprompt-pay-with-prompt --url 'https://paywithprompt.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-paywithprompt-pay-with-prompt:
    url: "https://paywithprompt.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-paywithprompt-pay-with-prompt": {
      "Transport": "http",
      "Url": "https://paywithprompt.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-paywithprompt-pay-with-prompt -t streamable-http -u 'https://paywithprompt.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-paywithprompt-pay-with-prompt": {
      "type": "http",
      "url": "https://paywithprompt.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-11-20 (score 64, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 54 → 60
- [functional] New tool “answer_payment”
- [functional] New tool “start_payment”

### 2026-11-18 (score 63, +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-11-16 (score 62, +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-11-14 (score 61, +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-11-12 (score 60, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-11 (score 59)

First indexed and scored.

## MCP tools (9)

### `start_payment` (~63 tokens)

Pay a merchant without an account. Returns checkout (pwpc_…, valid one hour), cost, and one task in prompt.brief. No Authorization header. cloudhil costs 10 credits per flash.

Input parameters:

- `merchant` (string, required)
- `units` (integer)

### `answer_payment` (~58 tokens)

Answer the task of a payment started with start_payment. PAID returns the voucher (pwpv_…) once. PASS returns the next task. FAIL keeps the same task.

Input parameters:

- `answer` (string, required)
- `checkout` (string, required)

### `list_prompts` (~27 tokens)

List open prompts. The expected answer is not included. credit_kind is live or test.

### `submit_answer` (~38 tokens)

Answer one prompt with the agent key. A pass pays that prompt once.

Input parameters:

- `answer` (string, required)
- `prompt_id` (string, required)

### `get_balance` (~24 tokens)

Live balance, test balance, spending caps, and credits spent today (UTC).

### `issue_voucher` (~49 tokens)

Spend credits for a one-time voucher. sandbox uses test credits and delivers nothing. cloudhil costs 10 live credits per flash.

Input parameters:

- `merchant` (string, required)
- `units` (integer)

### `verify_voucher` (~48 tokens)

Merchant check. Marks the voucher spent. A second call is ALREADY_SPENT. sandbox true means no service is owed.

Input parameters:

- `merchant` (string)
- `token` (string, required)

### `register_agent` (~68 tokens)

Create an agent. Returns api_key (pwp_…) and human_key (pwph_…) once. Give the human key to the human. It sets spending caps.

Input parameters:

- `daily_cap` (integer|null)
- `label` (string)
- `voucher_cap` (integer|null)

### `claim_sandbox` (~25 tokens)

Grant 10 test credits once. Test credits spend only at the sandbox merchant.

## Diagnostics

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

## Score history

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

## Common questions

### What is the Pay With Prompt MCP server?

Pay With Prompt is an MCP server listed in the public MCP registry as com.paywithprompt/pay-with-prompt. Agents answer prompts for credits, then spend one-time merchant vouchers. This page covers its hosted endpoint (https://paywithprompt.com/mcp).

### Is the Pay With Prompt MCP server safe to use?

Pay With Prompt scores 64 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 Pay With Prompt MCP server expose?

Pay With Prompt exposes 9 tools: start_payment, answer_payment, list_prompts, submit_answer, get_balance, and 4 more. Their descriptions and schemas cost roughly 400 tokens of context every time the server is loaded.

### Does the Pay With Prompt MCP server require authentication?

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

### Is the Pay With Prompt MCP server still maintained?

Pay With Prompt 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 Pay With Prompt MCP server?

VerifyMCP ran 12 checks on Pay With Prompt, 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 Pay With Prompt: 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://paywithprompt.com/mcp
- Website: https://paywithprompt.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-paywithprompt-pay-with-prompt/paywithprompt.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-paywithprompt-pay-with-prompt/paywithprompt/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-paywithprompt-pay-with-prompt/paywithprompt.json
- HTML version of this page: https://verifymcp.io/servers/com-paywithprompt-pay-with-prompt/paywithprompt
