Is the Subpay Document Reader MCP server down?

mcp-registry/ai.subpay/document-reader · v1.0.0

healthy
Last checked 2026-10-26 23:11 UTC · handshake 214ms

As of 2026-10-26 23:11 UTC, the Subpay Document Reader MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
3,806
outages (90d)
0
tools
3

Reads AIA G702/G703 pay applications and change orders from PDF to JSON. $0.04/page via x402.

Point your MCP client at this streamable-http endpoint: https://subpay.ai/mcp

Agent-readiness: B (80/100)

B (80/100): 0 error(s), 2 warning(s) across 3 tool(s); ~643 tokens of tool definitions.
Scores higher than 18% of 15,780 MCP servers Glimind has audited.
Its tool list costs an agent ~643 tokens per session — lighter than 85% of servers.
80 → 80 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints0
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability96

What to fix (4)

3 of 3 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: about, extract_document, request_capability

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: extract_document

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

In the last 30 days: 0 tool(s) removed and 1 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

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%2Fai.subpay%2Fdocument-reader/fixes

extract_document 1 change 
{
  "name": "extract_document",
  "description": "Reads construction pay applications — the AIA G702 Application and Certificate for Payment with its G703 Continuation Sheet, including Procore and Textura versions — and change orders, from PDF into structured JSON with arithmetic checks. Returns gross this period, retainage held and released, completed to date, contract sum, balance to finish and payment due for pay apps; for change orders, whether it is the subcontractor's request or the GC's executed change order, plus number, amount and date",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "document"
    ],
    "properties": {
      "gc": {
        "type": "string",
        "description": "General contractor name."
      },
      "document": {
        "type": "string",
        "description": "The PDF, base64-encoded (a data: URL prefix is fine). Max about 3 MB and 25 pages."
      },
      "fileName": {
        "type": "string",
        "description": "Original file name, if known."
      },
      "subcontractor": {
        "type": "string",
        "description": "Subcontractor company name — helps tell an RCO from a GC change order."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Read an AIA G702/G703 pay application or a change order"
}

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/ai.subpay/document-reader"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/ai.subpay/document-reader"}) 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%2Fai.subpay%2Fdocument-reader.svg)](https://glimind.com/server/mcp-registry%2Fai.subpay%2Fdocument-reader?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fai.subpay%2Fdocument-reader?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.subpay%2Fdocument-reader.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.subpay%2Fdocument-reader.svg
   :target: https://glimind.com/server/mcp-registry%2Fai.subpay%2Fdocument-reader?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:e6933ca21eb58428…, first seen 2026-10-17, included at leaf 6578 of 76,030. Version history · verify what your client received.

Tools (3)

Compare: most reliable knowledge servers · most reliable data 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 Subpay Document Reader MCP server down right now?

As of 2026-10-26 23:11 UTC, the Subpay Document Reader MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Subpay Document Reader MCP server provide?

Subpay Document Reader MCP server advertises 3 tools, including about, extract_document, request_capability.

How do I install Subpay Document Reader MCP server?

Point your MCP client at this streamable-http endpoint: https://subpay.ai/mcp

Is the Subpay Document Reader MCP server safe to connect to an AI agent?

Glimind scanned all 3 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 Subpay Document Reader 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