Is the Davisvillelabs Payeeproof MCP server down?

mcp-registry/io.github.davisvillelabs/payeeproof · v0.1.0

healthy
Last checked 2026-10-24 20:28 UTC · handshake 177ms

As of 2026-10-24 20:28 UTC, the Davisvillelabs Payeeproof MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
100%
checks observed
4,409
outages (90d)
1
tools
1

Payment identity intelligence for AI agents.

Install Davisvillelabs Payeeproof MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http davisvillelabs-payeeproof-mcp-server https://payeeproof.davisvillelabs.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: A (93/100)

A (93/100): 0 error(s), 1 warning(s) across 1 tool(s); ~1,109 tokens of tool definitions.
Scores higher than 76% of 15,657 MCP servers Glimind has audited.
Its tool list costs an agent ~1,109 tokens per session — lighter than 75% of servers.
91 → 93 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints100
Token cost100
Client compatibility50
Protocol100
Reliability100
Stability100

What to fix (1)

1 tool name(s) contain "." or exceed 64 characters, which OpenAI-compatible function calling rejects (^[a-zA-Z0-9_-]{1,64}$).

Use "_" or "-" instead of "." and keep names to 64 characters, so clients built on OpenAI-style tool calling don't have to rename (or drop) them. How to fix →

Tools: payeeproof.check_payee

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.davisvillelabs%2Fpayeeproof/fixes

payeeproof.check_payee 1 change
{
  "name": "payeeproof_check_payee",
  "description": "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-",
  "inputSchema": {
    "type": "object",
    "required": [
      "target_url"
    ],
    "properties": {
      "operation": {
        "type": "string",
        "maxLength": 160,
        "description": "Optional target operation or tool name the caller expects to invoke."
      },
      "live_probe": {
        "type": "boolean",
        "description": "Whether PayeeProof may perform its bounded anonymous public probe. Only safe GET or HEAD probes are eligible."
      },
      "target_url": {
        "type": "string",
        "format": "uri",
        "description": "Public HTTPS target URL whose machine-payment identity should be checked. Default HTTPS port 443 only."
      },
      "expected_asset": {
        "type": "string",
        "description": "Optional expected public payment asset identifier or symbol."
      },
      "request_method": {
        "enum": [
          "GET",
          "HEAD",
          "POST",
          "PUT",
          "PATCH",
          "DELETE"
        ],
        "type": "string",
        "default": "GET",
        "description": "Method of the target operation. PayeeProof actively probes only GET or HEAD; state-changing methods require caller-observed 402 evidence."
      },
      "expected_domain": {
        "type": "string",
        "description": "Optional hostname the caller expects after URL normalization. Used for deterministic domain consistency checks."
      },
      "expected_pay_to": {
        "type": "string",
        "description": "Optional expected public payment destination. EVM addresses are normalized case-insensitively before comparison."
      },
      "expected_network": {
        "type": "string",
        "description": "Optional expected payment network identifier, such as a CAIP-2 network, for comparison with observed metadata."
      },
      "expected_currency": {
        "type": "string",
        "description": "Optional expected target pricing currency or stablecoin symbol when exposed by the target challenge."
      },
      "expected_protocol": {
        "enum": [
          "x402",
          "mpp"
        ],
        "type": "string",
        "description": "Optional machine-payment protocol the caller expects the target to advertise."
      },
      "observed_response": {
        "type": "object",
        "properties": {
          "link": {
            "type": "string",
            "description": "Observed public Link header when relevant to target discovery or canonical identity."
          },
          "location": {
            "type": "string",
            "description": "Observed public Location header from a redirect. PayeeProof records but does not follow redirects."
          },
          "http_status": {
            "type": "integer",
            "maximum": 599,
            "minimum": 100,
            "description": "Observed target HTTP status, normally 402 for payment-required evidence."
          },
          "observed_at": {
            "type": "string",
            "format": "date-time",
            "description": "ISO 8601 timestamp indicating when the caller observed the supplied target response metadata."
          },
          "content_location": {
            "type": "string",
            "description": "Observed public Content-Location header when relevant to canonical resource identity."
          },
          "payment_required": {
            "type": "string",
            "description": "Observed public PAYMENT-REQUIRED header value from an x402 response. This is challenge metadata, not a payment credential."
          },
          "www_authenticate": {
            "type": "string",
            "description": "Observed public WWW-Authenticate header value, such as an MPP Payment challenge. Do not include an authorization credential."
          }
        },
        "description": "Optional caller-observed public target response metadata. Required for state-changing target methods. Never include a payment credential, Authorization, Cookie, or response body.",
        "additionalProperties": false
      },
      "expected_price_cents": {
        "type": "integer",
        "minimum": 1,
        "description": "Optional expected target price in integer USD cents for comparison with observed public payment metadata."
      },
      "expected_service_name": {
        "type": "string",
        "maxLength": 160,
        "description": "Optional public service name the caller expects the target payment challenge or discovery metadata to identify."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "openWorldHint": true,
    "idempotentHint": false,
    "destructiveHint": false
  },
  "title": "Check payee"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.davisvillelabs/payeeproof"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.davisvillelabs/payeeproof"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.davisvillelabs%2Fpayeeproof.svg)](https://glimind.com/server/mcp-registry%2Fio.github.davisvillelabs%2Fpayeeproof?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.davisvillelabs%2Fpayeeproof?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.davisvillelabs%2Fpayeeproof.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.davisvillelabs%2Fpayeeproof.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.davisvillelabs%2Fpayeeproof?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:180a18361e0e3a97…, first seen 2026-10-17, included at leaf 4168 of 61,097. Version history · verify what your client received.

Tools (1)

Compare: most reliable security servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

FAQ

Is the Davisvillelabs Payeeproof MCP server down right now?

As of 2026-10-24 20:28 UTC, the Davisvillelabs Payeeproof MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.

How many tools does Davisvillelabs Payeeproof MCP server provide?

Davisvillelabs Payeeproof MCP server advertises 1 tool, including payeeproof.check_payee.

How do I install Davisvillelabs Payeeproof MCP server?

Point your MCP client at this streamable-http endpoint: https://payeeproof.davisvillelabs.com/mcp

Is the Davisvillelabs Payeeproof MCP server safe to connect to an AI agent?

Glimind scanned all 1 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Davisvillelabs Payeeproof MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve