uk.minia2a/minia2a-mcp
NPM · MINIA2A-MCP
minia2a.uk — x402 pay-per-call APIs for AI agents, USDC on Base, 5 free trials per wallet.
Available components
Last scanned (11 hours ago)
Scores higher than 51% 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 Security69
- 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
- Install-script check failed: the install command fetches or executes arbitrary code (inline_eval,inline_url). An install hook runs on every machine, in CI, and on transitive installs, whether or not you ever run the server. View diagnostics → Fail
- 31 of 119 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 12 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1044 tokens (~174/item across 6 items; 6 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 2 Nov 26 0
- Stability: 0.97 → pass security
- 1 Nov 26 0
- Stability: pass → 0.97 functional
- 29 Oct 26 0
- Dependency health: partial → 0.89 functional
- 27 Oct 26 0
- Dependency health: 0.89 → partial functional
- 24 Oct 26 +10
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 −12
- Malware scan: pass → unverified ▼ security
- Stability: fail → pass ▲ security
- Package version: 1.2.10 → 1.2.12 functional
- 21 Oct 26 +26
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.89 ▲ functional
- 20 Oct 26 −26
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Dependency health: 0.89 → unverified ▼ functional
- Package version: 1.2.9 → 1.2.10 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 5 Nov 2026 · Analysed npm/minia2a-mcp@1.2.12
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 →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | dangerous | node -e "console.log('\n\\x1b[36m🔌 minia2a MCP ready!\\x1b[0m 1,600+ services for your AI agent. Auto-mode ready.\n\\x1b[33m📡 Browse catalog:\\x1b[0m https://minia2a.uk/catalog\n\\x1b[33m💰 Sell your own API:\\x1b[0m https://minia2a.uk/register\n\\x1b[33m📦 Client SDK:\\x1b[0m npm i minia2a\n')" |
Background: Why install scripts are a supply-chain risk →
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 119 packages
| Packages resolved | 119 |
|---|---|
| Stale | 31 |
| 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 →
minia2a_call_service ~447
Call an x402 service on minia2a.uk. Three access paths: (1) omit everything for the paid 402 path (sign a wallet for 5 free trial calls — no registration); (2) pass privateKey (or set MINIA2A_PRIVATE_KEY) for your wallet's own 5 trials — the key never leaves this process, it only signs the per-call trial message; (3) when both are exhausted the endpoint returns HTTP 402 with a machine-readable accepts[] array — pay in USDC and retry with a PAYMENT-SIGNATURE header (x402 V2). Set autoPay:true together with privateKey to have a 402 paid automatically in USDC on Base and the call retried — the wallet must hold USDC or the call still returns payment_required (never charges silently). Note that wallet= on its own does NOT reach the wallet bucket; the signature is what does. Service parameters go INSIDE `params`; a top-level key that is not one of the five declared names is rejected by name rather than dropped.
| Name | Type | Req | Description |
|---|---|---|---|
| autoPay | boolean | – | When true and a privateKey is available, a 402 Payment Required response is paid automatically in USDC on Base via x402 and the call retried. Default false — you get a payment_required response inste… |
| params | object | – | JSON parameters to send to the service. These are the service's OWN parameter names (e.g. {"ext":"json"} for x402-mime-type), nested here — not flattened onto the top level. |
| privateKey | string | – | Private key of your wallet, used locally to sign the trial message (EIP-191). Never transmitted — only the resulting signature is sent. Falls back to the MINIA2A_PRIVATE_KEY env var. |
| serviceId | string | yes | The service ID (e.g., 'x402-gas') or full endpoint path |
| wallet | string | – | Your self-custody wallet address (0x...). Without privateKey this alone does not draw on the wallet's trial bucket. |
No output schema declared.
No examples provided.
minia2a_check_endpoint ~139
Validate any x402 endpoint for autonomous-agent (Claude Code auto-mode) readiness. Checks 9 signals: HTTP reachability, JSON content-type, payment challenge (canonical PAYMENT-REQUIRED header or legacy x-402-* headers), payment amount, network, recipient, trial info, registration path, and /api/agent-ready handshake. Returns a score (0-100%) with per-check PASS/FAIL detail. Use this before calling a paid endpoint to verify it works with autonomous agents.
| Name | Type | Req | Description |
|---|---|---|---|
| endpointUrl | string | yes | The endpoint URL to validate (e.g., 'https://minia2a.uk/x402/gas') |
No output schema declared.
No examples provided.
minia2a_get_service ~71
Get detailed information about a specific x402 service on minia2a.uk, including its price, endpoint URL, input schema, and usage instructions. Use this before calling a service to understand what it needs.
| Name | Type | Req | Description |
|---|---|---|---|
| serviceId | string | yes | The service ID or name to get details for |
No output schema declared.
No examples provided.
minia2a_get_stats ~47
Get current platform statistics for minia2a.uk — total services, registered agents, transaction volume, uptime, and more. Useful for understanding the marketplace's scale and health.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
minia2a_list_services ~142
List available x402 services on minia2a.uk — the micropayment marketplace for AI agents. Returns service name, description, price, and endpoint for each service. Use this to discover what capabilities are available before calling them.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category (e.g., 'crypto', 'utility', 'data', 'ai') |
| limit | number | – | Max number of results to return (default 20) |
| search | string | – | Search term to filter services by id, name, or description. Hyphens and underscores are treated as spaces, so 'crypto-price' and 'crypto_price' both match. |
No output schema declared.
No examples provided.
minia2a_register ~198
Register a self-custody wallet on minia2a.uk to publish your own services (EIP-191 signature). Registration is for publishing — it is NOT required for trials: any wallet signed in minia2a_call_service already gets 5 free trial calls. If you don't provide a wallet+signature, this tool generates a fresh wallet, signs 'minia2a register: <your-wallet>' with EIP-191, registers it, and returns the private key — store it, the platform never holds it.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | A name for your agent (e.g., 'my-trading-bot') |
| signature | string | – | EIP-191 signature of 'minia2a register: <wallet>'. Required if you supply a wallet. |
| wallet | string | – | Your existing self-custody wallet address (0x...). Omit to have a fresh wallet generated for you. |
No output schema declared.
No examples provided.
How do I install the uk.minia2a/minia2a-mcp server?
uk.minia2a/minia2a-mcp runs locally as an npm package, launched with npx -y minia2a-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 · minia2a-mcp
claude mcp add uk-minia2a-minia2a-mcp -- npx -y minia2a-mcp
What is the uk.minia2a/minia2a-mcp server?
uk.minia2a/minia2a-mcp is listed in the public MCP registry as uk.minia2a/minia2a-mcp. minia2a.uk, x402 pay-per-call APIs for AI agents, USDC on Base, 5 free trials per wallet. This page covers its npm package (minia2a-mcp).
Is the uk.minia2a/minia2a-mcp server safe to use?
uk.minia2a/minia2a-mcp scores 75 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares an install script we flagged as high risk. 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 uk.minia2a/minia2a-mcp server expose?
uk.minia2a/minia2a-mcp exposes 6 tools: minia2a_list_services, minia2a_get_service, minia2a_get_stats, minia2a_register, minia2a_call_service, minia2a_check_endpoint. Their descriptions and schemas cost roughly 1,044 tokens of context every time the server is loaded.
Is the uk.minia2a/minia2a-mcp server still maintained?
uk.minia2a/minia2a-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 uk.minia2a/minia2a-mcp server under?
uk.minia2a/minia2a-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.