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.
Available components
Last scanned (11 days ago)
Scores higher than 0% of remote servers
Unreachable. Last reached 13 Oct 2026.
Deleted
This server was marked deleted in the MCP registry on 2026-10-13 14:11:24.034536+00.
Its details are retained for reference, and this page is not indexed.
The registry records this reason: Withdrawn from the public directory at the publisher request.
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 14 Oct 26 −60
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 13 Oct 26 +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.
- 11 Oct 26 +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.
- 9 Oct 26 58
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 14 Oct 2026 · Probed https://base-usdc-receivables-auditor-003.qqqa16521-dce.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=qqqa16521-dce.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 6 Oct 2026 | 4 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 53cee53d0a874eebf1af1fafee6f3699cb1 |
| SANs: *.qqqa16521-dce.workers.dev, qqqa16521-dce.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of base-usdc-receivables-auditor-003.qqqa16521-dce.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://base-usdc-receivables-auditor-003.qqqa16521-dce.workers.dev/mcp | HTTP error | 404 | |
| http (plaintext) | http://base-usdc-receivables-auditor-003.qqqa16521-dce.workers.dev/mcp | Inconclusive | 404 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_credit_balance Get credit balance ~34
Check the remaining prepaid credits for the bearer token configured on this MCP connection. This call is free and does not consume credits.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_payment_info Get prepaid credit purchase information ~37
Free instructions for buying this service's prepaid credits with direct native Base USDC. The funding transfer is separate from receivables being audited.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | – |
| assetDecimals | integer | yes | – |
| buyerPaysGas | boolean | yes | – |
| chainId | integer | yes | – |
| facilitatorRequired | boolean | yes | – |
| network | string | yes | – |
| packages | array | yes | – |
| purchasePath | string | yes | – |
| receiver | string | yes | – |
| reconciliationCostCredits | integer | yes | – |
| reconciliationCredits | integer | yes | – |
| redeemFlow | array | yes | – |
| scheme | string | yes | – |
| x402Compatible | boolean | yes | – |
No examples provided.
get_service_info Get receivables auditor information ~46
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | – |
| chainId | integer | yes | – |
| experiment | string | yes | – |
| network | string | yes | – |
| reconciliationCostCredits | integer | yes | – |
| reconciliationPolicy | object | yes | – |
| service | string | yes | – |
No examples provided.
reconcile_usdc_receivables Reconcile safe Base USDC receivables ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| expected | array | yes | – |
| fromBlock | string | yes | – |
| receiver | string | yes | – |
| toBlock | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
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.