aibtcdev/aibtc-mcp-server (aibtcdev/aibtc-mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 60 out of 100, grade C. It declares 358 tools. No publisher has claimed this listing.

C
Caution
60/100

aibtcdev/aibtc-mcp-server

Bitcoin-native MCP server for AI agents: BTC/STX wallets, DeFi yield, sBTC peg, NFTs, and x402 payments.

aibtcdev/aibtc-mcp-server· npm: @aibtc/mcp-server· 9.5K installs· listed on npm

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Sandbox Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

aibtcdev

Source: npm · also listed on PulseMCP, Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Tool descriptions don’t match what handlers do
1 tool describes read intent but its handler mutates — arxiv_search (line 88: entryRegex.exec(xml))
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 8 credentials: ARC_CREDS_PASSWORD, HIRO_API_KEY, JINGSWAP_API_KEY, MAGIC_EDEN_API_KEY, OPENROUTER_API_KEY, PILLAR_API_KEY, SPONSOR_API_KEY, UNISAT_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configAIBTC_CAMPAIGN_API_URL
configAPI_URLDefault x402 API base URL https://x402.biwas.xyz
configARC_CREDS_DIR
🔐 secretARC_CREDS_PASSWORD
configCLIENT_MNEMONIC(Optional) Pre-configured mnemonic -
configDEPLOY_SHA
configGITHUB_SHA
🔐 secretHIRO_API_KEY(Optional) Hiro API key for higher rate limits -
🔐 secretJINGSWAP_API_KEY
configJINGSWAP_API_URL
🔐 secretMAGIC_EDEN_API_KEY
configNETWORK"": "mainnet"
🔐 secretOPENROUTER_API_KEYexport =sk-or-...
configOPENROUTER_MODEL
🔐 secretPILLAR_API_KEY
configPILLAR_API_URL
configPILLAR_DEFAULT_REFERRAL
configPILLAR_POLL_TIMEOUT_MS
configSPEND_LIMIT_ENABLEDSet false to disable the wallet spending limit true
🔐 secretSPONSOR_API_KEY
configSPONSOR_FALLBACK_ENABLED
🔐 secretUNISAT_API_KEY
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

358/358 tools missing one or more hints — arxiv_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); arxiv_compile_digest (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); arxiv_list_digests (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +355 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Destructive tools are labelled

1 tool perform destructive updates without destructiveHint — pillar_disconnect deletes at line 48 (fs.unlink(SESSION_FILE))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Descriptions match behaviour

1 tool describes read intent but its handler mutates — arxiv_search (line 88: entryRegex.exec(xml))

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool inputs are validated

296/358 tool handlers declare input schemas (83%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

354/358 tool handlers wrap calls in try/catch (99%)

Wrap each tool handler body in try/catch and return a structured error response.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 9/358 tools referenced in tests (3%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

8 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Tool description accuracy

arxiv_search: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 10 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/aibtcdev/aibtc-mcp-server?variant=verified)](https://m8ven.ai/mcp/aibtcdev/aibtc-mcp-server)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: b2514b8ae99f04628e9b598e921cfde049511687
code hash: 42a16d095865673fce7e3ed4e2e81c1a1cd625ed35b6ca90a9e2c14d9dcda2d6
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client