PayeeProof

io.github.davisvillelabsPublished by GitHub account davisvillelabsv0.1.0Updated Oct 27, 2026

Payment identity intelligence for AI agents.

The publisher's own server: Proof Holdings

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

PayeeProof is a remote MCP server that lets an assistant run a paid consistency check on a machine payee before sending an autonomous payment.

What you can do
Check a payee before paying: run a paid assessment of a requested HTTPS endpoint, comparing claimed service expectations, the HTTP 402 challenge, resource binding, public discovery metadata and prior PayeeProof observations.
When to use it
Use it immediately before an autonomous machine payment, when an agent needs a public identity and payment-destination consistency assessment of the payee it is about to pay.
Requirements
A remote streamable HTTP endpoint; no packages, environment variables or headers are declared. The check itself costs $0.01 per call.
Before you install
Each check is a paid call at $0.01, so repeated use spends money. It is an assessment of public metadata only, not a guarantee that a payee is trustworthy; treat the result as one input before an autonomous payment.

Installation

In SourceWeft

  1. Open PayeeProof in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.davisvillelabs%2Fpayeeproof/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "payeeproof": {
      "type": "http",
      "url": "https://payeeproof.davisvillelabs.com/mcp"
    }
  }
}

Tools

1

payeeproof.check_payee

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.

Parametersoperationlive_probetarget_urlrequiredexpected_assetrequest_methodexpected_domainexpected_pay_toexpected_networkexpected_currencyexpected_protocolobserved_responseexpected_price_cents+1 more

Version history

1
  1. v0.1.0LatestSep 27, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Proof integrations