io.github.minia2a/minia2a-mcp
NPM · MINIA2A-MCP · SCANNED SEP 24
MCP server for minia2a.uk — discover and call 1,600+ x402 pay-per-call APIs with USDC payments.
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 Security86
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- 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
- 32 of 104 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 5 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1036 tokens (~129/item across 8 items; 8 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 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.minia2a/minia2a-mcp server?
io.github.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 minia2a-minia2a-mcp -- npx -y minia2a-mcp
{
"mcpServers": {
"minia2a-minia2a-mcp": {
"command": "npx",
"args": [
"-y",
"minia2a-mcp"
]
}
}
} {
"servers": {
"minia2a-minia2a-mcp": {
"command": "npx",
"args": [
"-y",
"minia2a-mcp"
]
}
}
} codex mcp add minia2a-minia2a-mcp -- npx -y minia2a-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"minia2a-minia2a-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"minia2a-mcp"
],
"enabled": true
}
}
} openclaw mcp add minia2a-minia2a-mcp --command npx --arg -y --arg minia2a-mcp
mcp_servers:
minia2a-minia2a-mcp:
command: "npx"
args: ["-y", "minia2a-mcp"] {
"McpServers": {
"minia2a-minia2a-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"minia2a-mcp"
]
}
}
} assistant mcp add minia2a-minia2a-mcp -t stdio -c npx -a -y minia2a-mcp
{
"mcpServers": {
"minia2a-minia2a-mcp": {
"command": "npx",
"args": [
"-y",
"minia2a-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.
- 24 Sept 26 0
- Stability: 0.97 → pass security
- 23 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.
- 21 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.
- 19 Sept 26 −2
- Stability: pass → 0.83 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 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.
- 16 Sept 26 −1
- Stability: pass → 0.93 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
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 24 Sept 2026 · Analysed npm/minia2a-mcp@1.1.21
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. Aug 14 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 →
Dependencies 104 packages
| Packages resolved | 104 |
|---|---|
| Stale | 32 |
| 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_buy_credits ~123
Claim credits from a completed USDC transfer. Send USDC on a supported chain (Base, Algorand, etc.) to the minia2a platform wallet, then submit the transaction hash here to credit your wallet. V5 has no in-app balance purchase — top-ups are claimed from an on-chain transfer.
| Name | Type | Req | Description |
|---|---|---|---|
| agentName | string | – | Optional agent name |
| txHash | string | yes | The transaction hash of your USDC transfer to the platform wallet |
| wallet | string | yes | Your wallet address that sent the USDC |
No output schema declared.
No examples provided.
minia2a_call_service ~271
Call an x402 service on minia2a.uk. Three access paths: (1) omit everything for an anonymous IP trial (15 calls shared across the whole catalog); (2) pass privateKey (or set MINIA2A_PRIVATE_KEY) for your registered wallet's own 15 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). Note that wallet= on its own does NOT reach the wallet bucket; the signature is what does.
| Name | Type | Req | Description |
|---|---|---|---|
| params | object | – | JSON parameters to send to the service |
| privateKey | string | – | Private key of the registered 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 registered 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 ~135
Validate any x402 endpoint for Claude Code auto-mode readiness (Aug 14, 2026). Checks 9 signals: HTTP reachability, JSON content-type, 4 payment headers (x-402-amount/chain/token/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_credits ~70
Explain the V5 credit/trial model and report platform-level stats. Note: V5 has no per-wallet balance endpoint — credits decrement automatically when you call a service with ?wallet=<your-wallet>. Remaining trials are surfaced per-call via X-Trial-* headers or the 402 body.
Input schema present but exposes no named parameters.
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 ~116
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 name or description |
No output schema declared.
No examples provided.
minia2a_register ~203
Register for minia2a.uk with a self-custody wallet + EIP-191 signature and get 500 free credits (through Sep 1, 2026). 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. 15 free trial calls are shared globally across all services; 1 credit = 1 API call on most endpoints.
| 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.
What is the io.github.minia2a/minia2a-mcp server?
io.github.minia2a/minia2a-mcp is listed in the public MCP registry as io.github.minia2a/minia2a-mcp. MCP server for minia2a.uk, discover and call 1,600+ x402 pay-per-call APIs with USDC payments. This page covers its npm package (minia2a-mcp).
Is the io.github.minia2a/minia2a-mcp server safe to use?
io.github.minia2a/minia2a-mcp scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 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 io.github.minia2a/minia2a-mcp server expose?
io.github.minia2a/minia2a-mcp exposes 8 tools: minia2a_list_services, minia2a_get_service, minia2a_get_stats, minia2a_register, minia2a_credits, and 3 more. Their descriptions and schemas cost roughly 1,036 tokens of context every time the server is loaded.
Is the io.github.minia2a/minia2a-mcp server still maintained?
io.github.minia2a/minia2a-mcp is still listed as active in the MCP registry. We last reached this channel on 24 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.minia2a/minia2a-mcp server under?
io.github.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.