dev.forgesworn/402-mcp
NPM · 402-MCP · SCANNED SEP 20
AI agents discover, pay for, and consume any Lightning-gated API autonomously
Available components
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 Security97
- No malware found by supply-chain analysis.Pass
- A known CVE affects elliptic, but no fixed version has been published, so there is nothing to upgrade to. View diagnostics → Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 224 of 228 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to forgesworn/402-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 29 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1444 tokens (~131/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
How do I install the dev.forgesworn/402-mcp server?
dev.forgesworn/402-mcp runs locally as an npm package, launched with npx -y 402-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 · 402-mcp
claude mcp add dev-forgesworn-402-mcp -- npx -y 402-mcp
{
"mcpServers": {
"dev-forgesworn-402-mcp": {
"command": "npx",
"args": [
"-y",
"402-mcp"
]
}
}
} {
"servers": {
"dev-forgesworn-402-mcp": {
"command": "npx",
"args": [
"-y",
"402-mcp"
]
}
}
} codex mcp add dev-forgesworn-402-mcp -- npx -y 402-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-forgesworn-402-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"402-mcp"
],
"enabled": true
}
}
} openclaw mcp add dev-forgesworn-402-mcp --command npx --arg -y --arg 402-mcp
mcp_servers:
dev-forgesworn-402-mcp:
command: "npx"
args: ["-y", "402-mcp"] {
"McpServers": {
"dev-forgesworn-402-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"402-mcp"
]
}
}
} assistant mcp add dev-forgesworn-402-mcp -t stdio -c npx -a -y 402-mcp
{
"mcpServers": {
"dev-forgesworn-402-mcp": {
"command": "npx",
"args": [
"-y",
"402-mcp"
]
}
}
} 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.
- 20 Sept 26 −3
- Stability: pass → 0.80 functional
- 19 Sept 26 +1
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 −3
- Stability: pass → 0.80 functional
- 12 Sept 26 +1
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed npm/402-mcp@3.15.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | forgesworn/402-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/forgesworn/402-mcp/.github/workflows/ci.yml@refs/heads/main |
| Rekor log index | 1248685923 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a26b856875e3d733bc13a56164241c06ba03e6380801ad757a233a111fbee9a8ce193d2c88ea650ee204a6ba1e7e40bd3ab7f1e94e06e3d1959b13dc9 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-848j-6mx2-7j84 | CVE-2025-14505 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L | no |
Background: What a vulnerability scan can and cannot prove →
Dependencies 224 packages
| Packages resolved | 224 |
|---|---|
| Deprecated | 2 |
| Stale | 87 |
| No linked repository | 1 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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 →
l402-balance ~73
Check cached credit balance for a server. Returns the last known balance from the credential store without making a network request. The "stale" flag is true if the balance was last updated more than 5 minutes ago.
| Name | Type | Req | Description |
|---|---|---|---|
| origin | string | yes | The server origin (e.g. https://api.example.com) |
No output schema declared.
No examples provided.
l402-buy-credits ~95
Buy credits from a toll-booth server with volume discounts. Omit amountSats to discover available tiers. Provide amountSats to purchase a specific tier. Only works with toll-booth servers.
| Name | Type | Req | Description |
|---|---|---|---|
| amountSats | integer | – | Amount in sats to purchase. Omit to list available tiers. |
| method | string | – | Payment method override |
| url | string | yes | The toll-booth server URL |
No output schema declared.
No examples provided.
l402-config ~42
Introspect the MCP's payment capabilities: which wallets are configured, spending limits, and stored credential count. Call this first to understand what payment methods are available.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
l402-credentials ~42
List all stored L402 credentials. Shows origin, cached credit balance, and server type. Balance values are cached and may be stale; check lastUsed timestamp.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
l402-discover ~84
Probe an endpoint to discover its L402 pricing without committing to payment. Returns the cost in sats, available payment methods, and credit tiers (if toll-booth server). The challenge is cached so a subsequent l402-pay can reuse it.
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | – | HTTP method to use |
| url | string | yes | The URL to probe for L402 pricing |
No output schema declared.
No examples provided.
l402-fetch ~330
Fetch a URL with automatic payment handling (L402 Lightning + x402 on-chain). Manages credentials, pays automatically when autoPay is true and cost is within budget, and retries. For human wallets, returns a payment page URL or QR code. For x402 services, returns payment details (receiver address, network, asset, amount) — the user pays in their wallet and provides the transaction hash. Set autoPay to true for seamless access. When a 402 is returned with tiers, present the pricing options to the user and use l402-buy-credits to purchase their chosen tier. For widget hosts, call l402-fetch-preview first to show a payment confirmation dialog before spending.
| Name | Type | Req | Description |
|---|---|---|---|
| autoPay | boolean | – | Automatically pay if within MAX_AUTO_PAY_SATS budget |
| body | string | – | Request body (for POST/PUT) |
| headers | object | – | Additional request headers |
| method | string | – | HTTP method |
| pubkey | string | – | Service pubkey from l402-search results — used to share credentials across all transport URLs for the same service |
| txHash | string | – | Transaction hash from a completed x402 on-chain payment. When provided, retries the request with X-Payment header for server verification. |
| url | string | yes | The primary URL to request. When using search results, pass the first URL here and all URLs in the urls field. |
| urls | array | – | All transport URLs from l402-search results (clearnet, onion, HNS). When present, transports are tried in preference order with automatic fallback on connection failure. |
No output schema declared.
No examples provided.
l402-fetch-preview ~129
Preview payment requirements for a URL without spending any sats. Returns cost, protocol, and payment method so a confirmation dialog can be shown. Use this before l402-fetch to give the user a chance to approve or cancel payment. For widget hosts, the result drives a payment confirmation dialog.
| Name | Type | Req | Description |
|---|---|---|---|
| headers | object | – | Additional request headers |
| method | string | – | HTTP method |
| pubkey | string | – | Nostr pubkey for xcashu auth |
| url | string | yes | URL to preview payment requirements for |
| urls | array | – | Batch: multiple URLs to preview |
No output schema declared.
No examples provided.
l402-pay ~170
Confirm payment and store credentials. Call this after l402-fetch returns a 402 with a paymentHash — polls the payment server for settlement (up to 30s for human wallet), then stores the credential so the next l402-fetch succeeds. For human wallets, call this immediately after showing the payment URL to the user.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice | string | – | BOLT-11 invoice to pay. Optional if paymentHash matches a cached challenge from l402-discover. |
| macaroon | string | – | Macaroon from the L402 challenge. Optional if paymentHash matches a cached challenge. |
| method | string | – | Payment method override. Defaults to wallet priority: NWC > Cashu > human. |
| paymentHash | string | – | Payment hash to look up cached challenge from l402-discover. |
No output schema declared.
No examples provided.
l402-redeem-cashu ~90
Redeem Cashu ecash tokens directly on a toll-booth server, avoiding the Lightning round-trip. Handles the two-step flow automatically (create invoice then redeem token). Only works with toll-booth servers.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | Cashu token string to redeem (e.g. cashuAey...) |
| url | string | yes | The toll-booth server URL |
No output schema declared.
No examples provided.
l402-search ~199
Search for paid APIs and services. Use this when the user wants something that might be available as a paid service — jokes, data, AI, content, etc. Discovers services announced on Nostr and returns their URLs, pricing, and capabilities. Then use l402-fetch with the URL to access the service.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | integer | – | Maximum number of results to return (default 20) |
| paymentMethod | string | – | Filter by payment method (e.g. "l402", "cashu", "x402", "xcashu") |
| query | string | yes | Search query to match against service names, descriptions, and capabilities |
| relays | array | – | Nostr relay URLs to query (defaults to popular public relays) |
| timeout | integer | – | Relay subscription timeout in milliseconds (default 5000) |
| topics | array | – | Filter by topic tags (e.g. ["ai", "data"]) |
No output schema declared.
No examples provided.
l402-store-token ~95
Store an L402 token (macaroon:preimage) obtained from a payment page. Use this when a user pastes back a token from a toll-booth payment page. The token is stored as a credential so subsequent l402-fetch calls are authenticated.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | The L402 token in macaroon:preimage format |
| url | string | yes | The service URL this token is for |
No output schema declared.
No examples provided.
What is the dev.forgesworn/402-mcp server?
dev.forgesworn/402-mcp is listed in the public MCP registry as dev.forgesworn/402-mcp. AI agents discover, pay for, and consume any Lightning-gated API autonomously. This page covers its npm package (402-mcp).
Is the dev.forgesworn/402-mcp server safe to use?
dev.forgesworn/402-mcp scores 93 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 dev.forgesworn/402-mcp server expose?
dev.forgesworn/402-mcp exposes 11 tools: l402-config, l402-discover, l402-fetch, l402-pay, l402-credentials, and 6 more. Their descriptions and schemas cost roughly 1,349 tokens of context every time the server is loaded.
Is the dev.forgesworn/402-mcp server still maintained?
dev.forgesworn/402-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 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 dev.forgesworn/402-mcp server under?
dev.forgesworn/402-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.