# PayeeProof (remote · payeeproof.davisvillelabs.com)

Payment identity intelligence for AI agents.

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `payeeproof.davisvillelabs.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/davisvillelabs-payeeproof/payeeproof.md), [page](https://verifymcp.io/servers/davisvillelabs-payeeproof/payeeproof)

## Channel facts

- Endpoint: `https://payeeproof.davisvillelabs.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-28.

- **Endpoint Security**: 69/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.
  - 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**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 501 tokens (~501/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

PayeeProof is a hosted endpoint at https://payeeproof.davisvillelabs.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 davisvillelabs-payeeproof 'https://payeeproof.davisvillelabs.com/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "davisvillelabs-payeeproof": {
      "type": "http",
      "url": "https://payeeproof.davisvillelabs.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-28 (score 68, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 65)

First indexed and scored.

## MCP tools (1)

### `payeeproof.check_payee` (~471 tokens)

Check payee

Paid $0.01 public machine identity and payment-destination consistency assessment. Use immediately before an autonomous machine payment to compare the requested HTTPS endpoint, claimed service expectations, HTTP 402 challenge, resource binding, public discovery metadata, and prior PayeeProof observations. PayeeProof never authorizes the target payment, never forwards target payment credentials, and actively probes only anonymous public GET/HEAD requests under a bounded SSRF-safe contract; state-changing target methods require caller-observed 402 evidence. Missing evidence can remain unknown. This is not KYC, AML, sanctions screening, fraud certification, legal identity verification, legal advice, or a delivery guarantee.

Input parameters:

- `expected_asset` (string): Optional expected public payment asset identifier or symbol.
- `expected_currency` (string): Optional expected target pricing currency or stablecoin symbol when exposed by the target challenge.
- `expected_domain` (string): Optional hostname the caller expects after URL normalization. Used for deterministic domain consistency checks.
- `expected_network` (string): Optional expected payment network identifier, such as a CAIP-2 network, for comparison with observed metadata.
- `expected_pay_to` (string): Optional expected public payment destination. EVM addresses are normalized case-insensitively before comparison.
- `expected_price_cents` (integer): Optional expected target price in integer USD cents for comparison with observed public payment metadata.
- `expected_protocol` (string): Optional machine-payment protocol the caller expects the target to advertise.
- `expected_service_name` (string): Optional public service name the caller expects the target payment challenge or discovery metadata to identify.
- `live_probe` (boolean): Whether PayeeProof may perform its bounded anonymous public probe. Only safe GET or HEAD probes are eligible.
- `observed_response` (object): Optional caller-observed public target response metadata. Required for state-changing target methods. Never include a payment credential, Authorization, Cookie, or response body.
- `operation` (string): Optional target operation or tool name the caller expects to invoke.
- `request_method` (string): Method of the target operation. PayeeProof actively probes only GET or HEAD; state-changing methods require caller-observed 402 evidence.
- `target_url` (string, required): Public HTTPS target URL whose machine-payment identity should be checked. Default HTTPS port 443 only.

Output parameters:

- `assessment`
- `checkedAt` (string)
- `checks` (array)
- `claimedIdentity` (object)
- `deterministicDigest` (string)
- `evidence` (array)
- `historicalContinuity` (object)
- `limitations` (array)
- `normalizedPaymentFacts` (object)
- `observedIdentity` (object)
- `receiptEnvelope`
- `recommendedMachineNextStep` (object)
- `schemaVersion`
- `target` (object)

## Diagnostics

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

## Score history

- 2026-09-28: 68
- 2026-09-27: 65

## Common questions

### What is the PayeeProof MCP server?

PayeeProof is an MCP server listed in the public MCP registry as io.github.davisvillelabs/payeeproof. Payment identity intelligence for AI agents. This page covers its hosted endpoint (https://payeeproof.davisvillelabs.com/mcp).

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

PayeeProof scores 68 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 PayeeProof MCP server expose?

PayeeProof exposes 1 tool: payeeproof.check_payee. Their descriptions and schemas cost roughly 471 tokens of context every time the server is loaded.

### Does the PayeeProof MCP server require authentication?

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

### Is the PayeeProof MCP server still maintained?

PayeeProof is still listed as active in the MCP registry. We last reached this channel on 28 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://payeeproof.davisvillelabs.com/mcp
- Website: https://payeeproof.davisvillelabs.com/
- Changelog RSS feed: https://verifymcp.io/servers/davisvillelabs-payeeproof/payeeproof.xml
- Changelog JSON feed: https://verifymcp.io/servers/davisvillelabs-payeeproof/payeeproof.json
- HTML version of this page: https://verifymcp.io/servers/davisvillelabs-payeeproof/payeeproof