io.github.zekebuilds-lab/mcp-l402-gate
NPM · @POWFORGE/MCP-L402-GATE · SCANNED SEP 20
L402 Lightning paywall + DoI score gate for MCP tools: challenge, verify, score.
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 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 131 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 341 tokens (~113/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 Management93
- Stability observed for 28 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
- 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
How do I install the io.github.zekebuilds-lab/mcp-l402-gate server?
io.github.zekebuilds-lab/mcp-l402-gate runs locally as an npm package, launched with npx -y @powforge/mcp-l402-gate. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @powforge/mcp-l402-gate
claude mcp add zekebuilds-lab-mcp-l402-gate -- npx -y @powforge/mcp-l402-gate
{
"mcpServers": {
"zekebuilds-lab-mcp-l402-gate": {
"command": "npx",
"args": [
"-y",
"@powforge/mcp-l402-gate"
]
}
}
} {
"servers": {
"zekebuilds-lab-mcp-l402-gate": {
"command": "npx",
"args": [
"-y",
"@powforge/mcp-l402-gate"
]
}
}
} codex mcp add zekebuilds-lab-mcp-l402-gate -- npx -y @powforge/mcp-l402-gate
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"zekebuilds-lab-mcp-l402-gate": {
"type": "local",
"command": [
"npx",
"-y",
"@powforge/mcp-l402-gate"
],
"enabled": true
}
}
} openclaw mcp add zekebuilds-lab-mcp-l402-gate --command npx --arg -y --arg @powforge/mcp-l402-gate
mcp_servers:
zekebuilds-lab-mcp-l402-gate:
command: "npx"
args: ["-y", "@powforge/mcp-l402-gate"] {
"McpServers": {
"zekebuilds-lab-mcp-l402-gate": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@powforge/mcp-l402-gate"
]
}
}
} assistant mcp add zekebuilds-lab-mcp-l402-gate -t stdio -c npx -a -y @powforge/mcp-l402-gate
{
"mcpServers": {
"zekebuilds-lab-mcp-l402-gate": {
"command": "npx",
"args": [
"-y",
"@powforge/mcp-l402-gate"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
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/@powforge/mcp-l402-gate@0.1.4
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 →
l402_gate_challenge ~74
Request a fresh PoW challenge from the PowForge L402 gate. Returns {nonce, difficulty}. Find a `solution` such that SHA-256(nonce+solution) starts with `difficulty` leading hex zeros, then call l402_gate_verify with {nonce, solution}. Free tier — no payment required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
l402_gate_score ~92
Look up the Depth-of-Identity (DoI) score for a Nostr pubkey via the public PowForge oracle. Returns {composite, rank, depth, score_version}. Use the composite scalar against your own minScore policy. Pairs with l402_gate_verify for compose-able L402 + identity gating.
| Name | Type | Req | Description |
|---|---|---|---|
| pubkey | string | yes | 64-hex Nostr pubkey to score |
No output schema declared.
No examples provided.
l402_gate_verify ~175
Verify a gate access attempt. Three shapes: (a) {nonce, solution} verifies a PoW solve and returns a 5-min token; (b) {request_invoice: true} mints a fresh L402 bolt11 invoice for the Lightning-skip tier; (c) {payment_hash} polls for L402 payment and returns the token once paid. Returns {token, method, content} on success.
| Name | Type | Req | Description |
|---|---|---|---|
| nonce | string | – | PoW challenge nonce from l402_gate_challenge |
| payment_hash | string | – | Payment hash returned by request_invoice; poll until paid |
| request_invoice | boolean | – | Set true to mint an L402 invoice instead of solving the PoW |
| solution | string | – | Hex string such that SHA-256(nonce+solution) has required leading zeros |
No output schema declared.
No examples provided.
What is the io.github.zekebuilds-lab/mcp-l402-gate server?
io.github.zekebuilds-lab/mcp-l402-gate is listed in the public MCP registry as io.github.zekebuilds-lab/mcp-l402-gate. L402 Lightning paywall + DoI score gate for MCP tools: challenge, verify, score. This page covers its npm package (@powforge/mcp-l402-gate).
Is the io.github.zekebuilds-lab/mcp-l402-gate server safe to use?
io.github.zekebuilds-lab/mcp-l402-gate scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 io.github.zekebuilds-lab/mcp-l402-gate server expose?
io.github.zekebuilds-lab/mcp-l402-gate exposes 3 tools: l402_gate_challenge, l402_gate_verify, l402_gate_score. Their descriptions and schemas cost roughly 341 tokens of context every time the server is loaded.
Is the io.github.zekebuilds-lab/mcp-l402-gate server still maintained?
io.github.zekebuilds-lab/mcp-l402-gate 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 io.github.zekebuilds-lab/mcp-l402-gate server under?
io.github.zekebuilds-lab/mcp-l402-gate declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.