io.github.superlabs-x/bitpal
NPM · @BITPAL/MCP · 2 COMPONENTS
Non-custodial stablecoin checkout: search BitPal docs, API spec, webhooks and errors; test payments
Available components
Last scanned (12 hours ago)
Scores higher than 29% of npm 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 Security83
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 0 of 1 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- 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 8 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 572 tokens (~81/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 38% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 18 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.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +6
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: unverified → fail ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Dependency health: unverified → 1.00 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.4 → 0.1.5 functional
- 12 Nov 26 50
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 21 Nov 2026 · Analysed npm/@bitpal/mcp@0.1.5
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 1 package
| Packages resolved | 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 →
get_api_operation ~83
Get one BitPal REST API operation from the OpenAPI spec: parameters, request body schema, responses and errors ($refs expanded). Path may use placeholders ({id}) or real ids.
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | yes | – |
| path | string | yes | e.g. /v1/checkout/sessions or /v1/checkout/sessions/{id}/deposit-address |
No output schema declared.
No examples provided.
get_doc ~54
Get a full BitPal documentation page as Markdown. Pages: ai, api, errors, flows, lifecycle, links, overview, quickstart, reference, sdk, webhooks, x402.
| Name | Type | Req | Description |
|---|---|---|---|
| page | string | yes | – |
No output schema declared.
No examples provided.
get_error_code ~51
Explain a BitPal API error code (HTTP status, cause, fix). Omit code to list all documented codes.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | e.g. SELLER_WALLET_NOT_CONFIGURED |
No output schema declared.
No examples provided.
get_integration_guide ~74
Get the rules every BitPal integration must follow plus the docs for one integration flow: hosted (redirect), popup, headless (your own payment UI), payment_link, x402 (pay per API call) or webhooks. Read this first when asked to integrate BitPal.
| Name | Type | Req | Description |
|---|---|---|---|
| flow | string | yes | – |
No output schema declared.
No examples provided.
get_webhook_event ~88
Get a BitPal webhook event's payload schema (envelope {id, event, created_at, data} plus data fields). Events: checkout.session.created, checkout.session.deposit_detected, checkout.session.paid, checkout.session.settled, checkout.session.unresolved, checkout.session.expired, checkout.refund.recorded, x402.payment.resolved.
| Name | Type | Req | Description |
|---|---|---|---|
| event | string | yes | – |
No output schema declared.
No examples provided.
list_api_operations ~31
List every public BitPal REST API operation (method, path, summary), generated from the OpenAPI spec.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_docs ~84
Search BitPal developer documentation (checkout sessions, popup/headless, payment links, x402, webhooks, errors, chains). Returns the best-matching sections with links. Use before writing BitPal integration code.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | What you are looking for, e.g. "verify webhook signature python" or "late payment". |
No output schema declared.
No examples provided.
How do I install the io.github.superlabs-x/bitpal MCP server?
io.github.superlabs-x/bitpal runs locally as an npm package, launched with npx -y @bitpal/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 · @bitpal/mcp
claude mcp add superlabs-x-bitpal -- npx -y @bitpal/mcp
What is the io.github.superlabs-x/bitpal MCP server?
io.github.superlabs-x/bitpal is an MCP server listed in the public MCP registry as io.github.superlabs-x/bitpal. Non-custodial stablecoin checkout: search BitPal docs, API spec, webhooks and errors; test payments. This page covers its npm package (@bitpal/mcp).
Is the io.github.superlabs-x/bitpal MCP server safe to use?
io.github.superlabs-x/bitpal scores 60 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 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 io.github.superlabs-x/bitpal MCP server expose?
io.github.superlabs-x/bitpal exposes 7 tools: search_docs, get_doc, get_integration_guide, list_api_operations, get_api_operation, and 2 more. Their descriptions and schemas cost roughly 465 tokens of context every time the server is loaded.
Is the io.github.superlabs-x/bitpal MCP server still maintained?
io.github.superlabs-x/bitpal is still listed as active in the MCP registry. We last reached this channel on 21 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.superlabs-x/bitpal MCP server under?
io.github.superlabs-x/bitpal declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.superlabs-x/bitpal MCP server?
VerifyMCP ran 15 checks on io.github.superlabs-x/bitpal, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.superlabs-x/bitpal: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.