io.github.IvanSFlowGit/paypilot-ach-returns-mcp
PYPI · PAYPILOT-ACH-RETURNS-MCP
Read-only decision table over ACH return codes: 17 codes, 5 decisions, rule shown.
Available components
Last scanned (7 hours ago)
Scores higher than 64% of PyPI servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (PolyForm-Noncommercial-1.0.0) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 311 tokens (~103/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 5 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +17
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.17 ▲ functional
- Package version: 0.1.0 → 0.1.1 functional
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 48
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 5 Nov 2026 · Analysed pypi/paypilot-ach-returns-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
explain ~74
Say which row fired for a code and why. ``family`` is populated only where the source table itself states one. The published rulebook is sold rather than free, so a family is never asserted from memory here; ``family_note`` says which of the two you are looking at.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
No output schema declared.
No examples provided.
list_decisions ~64
List the five decision rows and the codes that land on each. Seventeen codes, five answers. The row is the decision; the code is a cell inside one. ``default_row`` is where anything unlisted lands, and it is never row 1.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_return_code ~103
Decide one ACH return code. Returns the code, its decision row, whether the entry goes again, what has to change first, the wording for the customer, and whether a named person acts before anything automatic. An unknown code is NOT an error and is NOT null. It lands on the conservative row and comes back with ``matched`` false and a ``fallback_reason`` saying it fell through rather than matched.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
No output schema declared.
No examples provided.
How do I install the io.github.IvanSFlowGit/paypilot-ach-returns-mcp server?
io.github.IvanSFlowGit/paypilot-ach-returns-mcp runs locally as a PyPI package, launched with uvx paypilot-ach-returns-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · paypilot-ach-returns-mcp
claude mcp add ivansflowgit-paypilot-ach-returns-mcp -- uvx paypilot-ach-returns-mcp
What is the io.github.IvanSFlowGit/paypilot-ach-returns-mcp server?
io.github.IvanSFlowGit/paypilot-ach-returns-mcp is listed in the public MCP registry as io.github.IvanSFlowGit/paypilot-ach-returns-mcp. Read-only decision table over ACH return codes: 17 codes, 5 decisions, rule shown. This page covers its PyPI package (paypilot-ach-returns-mcp).
Is the io.github.IvanSFlowGit/paypilot-ach-returns-mcp server safe to use?
io.github.IvanSFlowGit/paypilot-ach-returns-mcp scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 io.github.IvanSFlowGit/paypilot-ach-returns-mcp server expose?
io.github.IvanSFlowGit/paypilot-ach-returns-mcp exposes 3 tools: lookup_return_code, list_decisions, explain. Their descriptions and schemas cost roughly 241 tokens of context every time the server is loaded.
Is the io.github.IvanSFlowGit/paypilot-ach-returns-mcp server still maintained?
io.github.IvanSFlowGit/paypilot-ach-returns-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.IvanSFlowGit/paypilot-ach-returns-mcp server under?
io.github.IvanSFlowGit/paypilot-ach-returns-mcp declares the PolyForm-Noncommercial-1.0.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.