SelfPaidPal — Autonomous DeFi Payments
NPM · SELFPAID-MCP
Zero-net-cost payments on Base Mainnet powered by automated Aave V3 & Morpho yield farming.
Available components
Last scanned (8 hours ago)
Scores higher than 50% of npm servers
Category Crypto and Web3
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
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 15 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 362 tokens (~120/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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
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 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +6
- Stability: unverified → 0.43 ▲ functional
- 20 Oct 26 67
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 npm/selfpaid-mcp@2.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
build_payment ~180
Generate ready-to-sign EVM transactions and EIP-5792 atomic batch calls for a zero-net-cost payment on Base (Chain ID 8453). Automatically supplies collateral into Aave V3 or Morpho to recover 100% of the principal + developer fee.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount of USDC to pay to the recipient (e.g. 25). |
| buffer | number | – | Safety buffer percentage (defaults to 8). |
| collateral | number | – | Collateral multiplier (defaults to 20). |
| protocol | string | – | Yield protocol to use ('auto', 'aave', or 'morpho'). Defaults to 'auto'. |
| recipient | string | yes | Ethereum address of the recipient receiving the payment (0x...). |
| sender | string | yes | Ethereum address of the payer executing the transactions (0x...). |
| Name | Type | Req | Description |
|---|---|---|---|
| batchCalls | array | yes | EIP-5792 atomic batch calls array for Smart Accounts and Agentic Wallets |
| chainId | number | yes | Target EVM Chain ID (8453 for Base) |
| success | boolean | yes | True if transaction generation succeeded |
| summary | object | yes | Detailed financial summary of the zero-cost payment plan |
| transactions | array | yes | Ordered array of 4 sequential EVM transactions for standard wallets |
No examples provided.
get_quote ~123
Calculate collateral requirements, developer fee, yield deposit, and estimated recovery days for a zero-net-cost USDC payment on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount of USDC to pay to the recipient (e.g. 10 or 25.5). |
| buffer | number | – | Safety buffer percentage (default 8 = 8%). |
| collateral | number | – | Collateral multiplier (default 20 = 20x the payment amount). |
| protocol | string | – | Yield protocol to use. 'auto' (recommended) automatically picks the higher yielding protocol. |
| Name | Type | Req | Description |
|---|---|---|---|
| amountToPay | string | yes | USDC amount delivered to recipient |
| bufferPercentage | number | – | Safety buffer percentage applied (e.g. 8) |
| collateralMultiplier | number | – | Collateral multiplier used (e.g. 20) |
| collateralTotal | string | yes | Base collateral plus safety buffer in USDC |
| estimatedAPY | number | yes | Active APY rate for the chosen protocol |
| estimatedRecoveryDays | number | yes | Estimated days until earned yield equals payment + fee |
| feeAmount | string | yes | 0.5% developer fee in USDC (min 0.1, max 50) |
| rates | object | – | Live APY comparison across protocols |
| selectedProtocol | string | yes | Yield protocol selected for capital recovery |
| totalRequiredAmount | string | yes | Total USDC needed upfront (payment + fee + yield deposit) |
| yieldDepositAmount | string | yes | USDC deposited into yield protocol to generate returns |
No examples provided.
get_rates ~59
Get real-time supply APYs across Aave V3 and Morpho on Base Mainnet. Automatically indicates the most profitable protocol for capital recovery.
| Name | Type | Req | Description |
|---|---|---|---|
| refresh | boolean | – | Force a live on-chain refresh rather than using cached rates (defaults to false). |
| Name | Type | Req | Description |
|---|---|---|---|
| aave | object | yes | Aave V3 supply yield on Base Mainnet |
| best | string | yes | Protocol with the highest yield |
| bestApy | number | yes | Highest supply APY currently available |
| isCached | boolean | – | Whether rates were served from in-memory cache |
| lastUpdated | string | – | ISO 8601 timestamp of last oracle update |
| morpho | object | yes | Morpho Vault supply yield on Base Mainnet |
No examples provided.
How do I install the SelfPaidPal — Autonomous DeFi Payments MCP server?
SelfPaidPal — Autonomous DeFi Payments runs locally as an npm package, launched with npx -y selfpaid-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · selfpaid-mcp
claude mcp add altoninelli-selfpaid -- npx -y selfpaid-mcp
What is the SelfPaidPal — Autonomous DeFi Payments MCP server?
SelfPaidPal — Autonomous DeFi Payments is an MCP server listed in the public MCP registry as io.github.altoninelli/selfpaid. Zero-net-cost payments on Base Mainnet powered by automated Aave V3 & Morpho yield farming. This page covers its npm package (selfpaid-mcp).
Is the SelfPaidPal — Autonomous DeFi Payments MCP server safe to use?
SelfPaidPal — Autonomous DeFi Payments scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 SelfPaidPal — Autonomous DeFi Payments MCP server expose?
SelfPaidPal — Autonomous DeFi Payments exposes 3 tools: get_rates, get_quote, build_payment. Their descriptions and schemas cost roughly 362 tokens of context every time the server is loaded.
Is the SelfPaidPal — Autonomous DeFi Payments MCP server still maintained?
SelfPaidPal — Autonomous DeFi Payments 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 SelfPaidPal — Autonomous DeFi Payments MCP server under?
SelfPaidPal — Autonomous DeFi Payments declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.