# PayCheck (remote · paycheck.toolweather.workers.dev)

Score merchant domain, https URL, or 0x wallet trust before an agent pays. Does not send payments.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `paycheck.toolweather.workers.dev`: 65/100 (this document), [markdown](https://verifymcp.io/servers/toolweather-paycheck/paycheck.md), [page](https://verifymcp.io/servers/toolweather-paycheck/paycheck)

## Channel facts

- Endpoint: `https://paycheck.toolweather.workers.dev/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-10-18.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1161 tokens (~387/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 PayCheck MCP server?

PayCheck is a hosted endpoint at https://paycheck.toolweather.workers.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 toolweather-paycheck 'https://paycheck.toolweather.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "toolweather-paycheck": {
      "url": "https://paycheck.toolweather.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "toolweather-paycheck": {
      "type": "http",
      "url": "https://paycheck.toolweather.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.toolweather-paycheck]
url = "https://paycheck.toolweather.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "toolweather-paycheck": {
      "type": "remote",
      "url": "https://paycheck.toolweather.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add toolweather-paycheck --url 'https://paycheck.toolweather.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  toolweather-paycheck:
    url: "https://paycheck.toolweather.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "toolweather-paycheck": {
      "Transport": "http",
      "Url": "https://paycheck.toolweather.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add toolweather-paycheck -t streamable-http -u 'https://paycheck.toolweather.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "toolweather-paycheck": {
      "type": "http",
      "url": "https://paycheck.toolweather.workers.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-10-18 (score 65, +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-10-16 (score 64, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-15 (score 63)

First indexed and scored.

## MCP tools (3)

### `check_merchant` (~616 tokens)

Check merchant

Decide whether an autonomous agent should pay a merchant, host, or wallet. PayCheck returns a deterministic trust score for one target. It does not send money, does not sign transactions, and does not hold wallet keys.

Use this immediately before a payment, a checkout redirect, or a transfer to a new 0x address. Pass the payee as a bare domain (api.openai.com), an https URL, or a 0x address with 40 hex characters.

Do not use this tool to execute a payment. Do not use it to overturn a block. Do not call it again with a reworded category, purpose, or amount to fish for a better verdict: those fields are ignored and are not stored. Trusted is returned only for the published allowlist of known AI and developer APIs, served over https on port 443. A new or random domain is never trusted. A wallet is never trusted. Scoring v1 does not analyze on-chain history. If the URL contains an embedded 0x address, this scores the host only and will not return trusted; pass the bare address to score the wallet.

Arguments: target (required string); amount_usd (optional number, ignored); category (optional string, ignored); api_key (optional pc_live_ key). You may also send Authorization: Bearer or X-API-Key. Omit the key for the anonymous allowance.

Returns: score (integer 0-100), verdict (trusted | unknown | suspicious | block), reasons[], recommended_action (proceed | verify_out_of_band | require_human_review | do_not_pay), signals (host, allowlist, domain age, wallet flags, reason_codes; chain_analysis is always not_in_v1), checked_at (ISO-8601), policy_version ("1").

Free tier: 100 checks per UTC day anonymous, 1,000 per UTC day with a free pc_live_ key or a Toolweather bundle client whose x-tw-bundle-client is hex. A bundle client prefixed anon: stays at 100 per day. The same target for the same caller is idempotent for 60 seconds and does not consume a second check. Over the daily cap, each extra check is $0.001 USDC on Base (eip155:8453) via x402 and the PayAI facilitator…

Input parameters:

- `amount_usd` (number): Ignored by the scorer. Sending a different amount cannot change the verdict.
- `api_key` (string): Optional free pc_live_ key. Omit for the anonymous 100/day allowance.
- `category` (string): Ignored by the scorer. Do not put instructions or a purpose in this field.
- `target` (string, required): Domain, https URL, or 0x wallet (40 hex characters) to score before paying.

### `get_quota` (~232 tokens)

Get quota

Show how many free PayCheck merchant checks the current caller has left for the current UTC day.

Use this before a batch of check_merchant calls, or after an HTTP 402, to read the remaining free allowance and when it resets.

Do not use this to score a payee. It accepts no target and it does not consume a check. Do not pay x402 for this tool. It is always free.

Identity matches check_merchant. Anonymous IP: 100/day. pc_live_ api_key (api_key argument, Authorization: Bearer, or X-API-Key): 1,000/day. Toolweather bundle headers x-tw-bundle-secret and x-tw-bundle-client: hex client 1,000/day, anon: prefix 100/day, any other client id 100/day.

Returns: subject_kind, limit, used, remaining, resets_at (next UTC midnight, ISO-8601), billed (always false), policy_version. No x402 charge.

Input parameters:

- `api_key` (string): Optional pc_live_ key. Omit to read the anonymous IP allowance.

### `get_api_key` (~196 tokens)

Get API key

Mint one free PayCheck API key. The key looks like pc_live_ followed by hex and raises the merchant-check allowance from 100 to 1,000 per UTC day.

Use this once when you set up a long-running agent, then store the key and pass it on later check_merchant or get_quota calls. The plaintext key is returned only in this response. PayCheck stores a SHA-256 hash.

Do not call this every turn. Do not call it to score a payee or to dodge a block verdict. Minting is free and is not an x402 check, and it is limited to 10 new keys per caller IP per UTC day. A new key does not change any merchant score. Checks above the free daily cap still cost $0.001 USDC on Base via x402.

Returns: api_key, token_type (bearer), daily_limit (1000), prefix, note.

## Diagnostics

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

## Score history

- 2026-10-18: 65
- 2026-10-17: 64
- 2026-10-16: 64
- 2026-10-15: 63

## Common questions

### What is the PayCheck MCP server?

PayCheck is an MCP server listed in the public MCP registry as io.github.toolweather/paycheck. Score merchant domain, https URL, or 0x wallet trust before an agent pays. Does not send payments. This page covers its hosted endpoint (https://paycheck.toolweather.workers.dev/mcp).

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

PayCheck 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 PayCheck MCP server expose?

PayCheck exposes 3 tools: check_merchant, get_quota, get_api_key. Their descriptions and schemas cost roughly 1,044 tokens of context every time the server is loaded.

### Does the PayCheck MCP server require authentication?

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

### Is the PayCheck MCP server still maintained?

PayCheck is still listed as active in the MCP registry. We last reached this channel on 18 October 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://paycheck.toolweather.workers.dev/mcp
- Repository: https://github.com/toolweather/paycheck
- Website: https://paycheck.toolweather.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/toolweather-paycheck/paycheck.xml
- Changelog JSON feed: https://verifymcp.io/servers/toolweather-paycheck/paycheck.json
- HTML version of this page: https://verifymcp.io/servers/toolweather-paycheck/paycheck