# Base USDC Receivables Auditor (remote · base-usdc-receivables-auditor-003.qqqa16521-dce.workers.dev)

Dual-RPC Base USDC receivables reconciliation with safe finality and fail-ambiguous matching.

- Trust score: 0/100 (low)
- Registry status: deleted
- Liveness: dead
- Owner verified: no
- Last scored: 2026-10-14

> **Deleted**: this server was marked deleted in the MCP registry on 2026-10-13. Its details are retained for reference. The registry records this reason: "Withdrawn from the public directory at the publisher request."

## Components

- remote · `base-usdc-receivables-auditor-003.qqqa16521-dce.workers.dev`: 0/100 (this document), [markdown](https://verifymcp.io/servers/pghannmmn-base-usdc-receivables-auditor/base-usdc-receivables-auditor-003.md), [page](https://verifymcp.io/servers/pghannmmn-base-usdc-receivables-auditor/base-usdc-receivables-auditor-003)

## Channel facts

- Endpoint: `https://base-usdc-receivables-auditor-003.qqqa16521-dce.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-14.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 404.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-14 (score 0, −60)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Authorization: fail → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.17 → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-13 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-11 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-09 (score 58)

First indexed and scored.

## MCP tools (4)

### `get_service_info` (~46 tokens)

Get receivables auditor information

Free overview of the Base USDC Receivables Auditor, including dual-RPC safe-finality policy, fail-ambiguous matching, scan limits and the per-batch credit cost.

Output parameters:

- `asset` (string)
- `chainId` (integer)
- `experiment` (string)
- `network` (string)
- `reconciliationCostCredits` (integer)
- `reconciliationPolicy` (object)
- `service` (string)

### `get_payment_info` (~37 tokens)

Get prepaid credit purchase information

Free instructions for buying this service's prepaid credits with direct native Base USDC. The funding transfer is separate from receivables being audited.

Output parameters:

- `asset` (string)
- `assetDecimals` (integer)
- `buyerPaysGas` (boolean)
- `chainId` (integer)
- `facilitatorRequired` (boolean)
- `network` (string)
- `packages` (array)
- `purchasePath` (string)
- `receiver` (string)
- `reconciliationCostCredits` (integer)
- `reconciliationCredits` (integer)
- `redeemFlow` (array)
- `scheme` (string)
- `x402Compatible` (boolean)

### `get_credit_balance` (~34 tokens)

Get credit balance

Check the remaining prepaid credits for the bearer token configured on this MCP connection. This call is free and does not consume credits.

### `reconcile_usdc_receivables` (~126 tokens)

Reconcile safe Base USDC receivables

Scan a bounded Base Mainnet block range for native Circle USDC transfers into one receiver, require exact agreement from two public RPCs at safe finality, and compare them with up to 25 expected receivables. Returns matched, missing, underpaid, overpaid, wrong-sender, late, duplicate and needs-review exceptions without fuzzy guessing. Costs 10 credits; RPC or unsafe-range failures refund the charge.

Input parameters:

- `expected` (array, required)
- `fromBlock` (string, required)
- `receiver` (string, required)
- `toBlock` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/pghannmmn-base-usdc-receivables-auditor/base-usdc-receivables-auditor-003#diagnostics

## Score history

- 2026-10-14: 0
- 2026-10-13: 60
- 2026-10-12: 59
- 2026-10-11: 59
- 2026-10-10: 58
- 2026-10-09: 58

## Common questions

### What is the Base USDC Receivables Auditor MCP server?

Base USDC Receivables Auditor is an MCP server listed in the public MCP registry as io.github.PGhannmmn/base-usdc-receivables-auditor. Dual-RPC Base USDC receivables reconciliation with safe finality and fail-ambiguous matching. This page covers its hosted endpoint (https://base-usdc-receivables-auditor-003.qqqa16521-dce.workers.dev/mcp).

### Is the Base USDC Receivables Auditor MCP server safe to use?

Base USDC Receivables Auditor scores 0 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 Base USDC Receivables Auditor MCP server expose?

Base USDC Receivables Auditor exposes 4 tools: get_service_info, get_payment_info, get_credit_balance, reconcile_usdc_receivables. Their descriptions and schemas cost roughly 243 tokens of context every time the server is loaded.

### Does the Base USDC Receivables Auditor MCP server require authentication?

Its publisher declares no required credentials for Base USDC Receivables Auditor. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Base USDC Receivables Auditor MCP server still maintained?

Base USDC Receivables Auditor has been deleted from the MCP registry. We last reached this channel on 13 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://base-usdc-receivables-auditor-003.qqqa16521-dce.workers.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/pghannmmn-base-usdc-receivables-auditor/base-usdc-receivables-auditor-003.xml
- Changelog JSON feed: https://verifymcp.io/servers/pghannmmn-base-usdc-receivables-auditor/base-usdc-receivables-auditor-003.json
- HTML version of this page: https://verifymcp.io/servers/pghannmmn-base-usdc-receivables-auditor/base-usdc-receivables-auditor-003