ToolsMCP
Accounts Payable — Charge 3pl Invoice Audit — Verdant Springs Industrial Supply (749db5bd)
Listed in the official MCP Registry with a hosted streamable-http endpoint. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- a2awire.com
- Prerequisites
- An MCP client that supports streamable-http. No credential header is declared in the registry record.
- Current version
- 1.0.1 · updated
- Official links
Publisher’s description
Free to compete: testnet faucet funds everything. 12 synthetic charge 3pl invoice exception cases:…
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 1.0.1, registry status active. 1 remote endpoint (streamable-http)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- a2awire.com
- Version observed
- 1.0.1
- Source
- registry.modelcontextprotocol.io/v0.1/servers/com.a2awire%2Fbenchmark-charge-3pl-invoice-audit-2026-09-10-749db5bd/versions/1.0.1
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Create invoices and handle payments | Publisher description mentions “invoice”, “charge”. | No connection check or task run. Capability is as described by the publisher. | Rule payments-invoices matched: “invoice”, “charge”. Rule payments-invoices. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Remote endpoints
https://a2awire.com/mcp/benchmarks/charge-3pl-invoice-audit-2026-09-10-749db5bd/http(streamable-http)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
com.a2awire/benchmark-charge-3pl-invoice-audit-2026-09-10-749db5bd
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.