PayeeProof
REMOTE · PAYEEPROOF.DAVISVILLELABS.COM · SCANNED SEP 28
Payment identity intelligence for AI agents.
Available components
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. How we score → Why this is hard to score →
Endpoint Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · payeeproof.davisvillelabs.com
claude mcp add --transport http davisvillelabs-payeeproof 'https://payeeproof.davisvillelabs.com/mcp'
{
"mcpServers": {
"davisvillelabs-payeeproof": {
"url": "https://payeeproof.davisvillelabs.com/mcp"
}
}
} {
"servers": {
"davisvillelabs-payeeproof": {
"type": "http",
"url": "https://payeeproof.davisvillelabs.com/mcp"
}
}
} [mcp_servers.davisvillelabs-payeeproof] url = "https://payeeproof.davisvillelabs.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"davisvillelabs-payeeproof": {
"type": "remote",
"url": "https://payeeproof.davisvillelabs.com/mcp",
"enabled": true
}
}
} openclaw mcp add davisvillelabs-payeeproof --url 'https://payeeproof.davisvillelabs.com/mcp' --transport streamable-http
mcp_servers:
davisvillelabs-payeeproof:
url: "https://payeeproof.davisvillelabs.com/mcp" {
"McpServers": {
"davisvillelabs-payeeproof": {
"Transport": "http",
"Url": "https://payeeproof.davisvillelabs.com/mcp"
}
}
} assistant mcp add davisvillelabs-payeeproof -t streamable-http -u 'https://payeeproof.davisvillelabs.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://payeeproof.davisvillelabs.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=davisvillelabs.com | CN=WE1,O=Google Trust Services,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 870a1e3497b03caa0ea6c57ddd52be74 |
| SANs: davisvillelabs.com, payeeproof.davisvillelabs.com, *.payeeproof.davisvillelabs.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of payeeproof.davisvillelabs.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| davisvillelabs.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://payeeproof.davisvillelabs.com/mcp | Verified | 200 | |
| http (plaintext) | http://payeeproof.davisvillelabs.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
payeeproof.check_payee Check payee ~471
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Public HTTPS target URL whose machine-payment identity should be checked. Default HTTPS port 443 only. |
| Name | Type | Req | Description |
|---|---|---|---|
| assessment | – | yes | – |
| checkedAt | string | yes | – |
| checks | array | yes | – |
| claimedIdentity | object | yes | – |
| deterministicDigest | string | yes | – |
| evidence | array | yes | – |
| historicalContinuity | object | yes | – |
| limitations | array | yes | – |
| normalizedPaymentFacts | object | yes | – |
| observedIdentity | object | yes | – |
| receiptEnvelope | – | – | – |
| recommendedMachineNextStep | object | yes | – |
| schemaVersion | – | yes | – |
| target | object | yes | – |
No examples provided.
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.