Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/Bitget-AI/bitget-signalWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/bitget-ai/bitget-signal/bitget-signal)<a href="https://agentmods.dev/mcp/bitget-ai/bitget-signal/bitget-signal"><img src="https://agentmods.dev/badge/mcp/bitget-ai/bitget-signal/bitget-signal/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/bitget-ai/bitget-signal/bitget-signal"><img src="https://agentmods.dev/badge/mcp/bitget-ai/bitget-signal/bitget-signal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
bitget-signal scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "bitget-signal": { "command": "npx", "args": [ "-y", "@bitget-ai/bitget-signal" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 9 lines scan A c4ac8d20133d
bitget-signal is an MCP server published in the GitHub repository Bitget-AI/bitget-signal (2 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
bsv-wallet
MCP server "bsv-wallet" as configured in Calhooon/bsv-wallet-cli. Launched with cargo run --release --manifest-path mcp/Cargo.toml. Needs 1 environment variable to run.
bitcoin-mcp
MCP server for Bitcoin — 49 tools for AI agents to save money on fees. Zero config, works out of the box. Runs locally from the bitcoin-mcp Python package. Needs 5 environment variables to run.
saturnzap
CLI-first, non-custodial Lightning Network wallet for autonomous AI agents. Runs locally from the saturnzap Python package. Needs 2 environment variables to run.
agentic-aqua
Agentic AQUA — MCP server for Liquid Network and Bitcoin wallet operations. Runs locally from the agentic-aqua Python package.
crypto-swap
Native cross-chain swaps: Bitcoin, Ethereum, Solana, Polkadot, Tron, Arbitrum. Quote, swap, track. Remote server at chainflip-broker.io.
bitget-agent-mcp
Official Bitget MCP Server for the Unified Trading Account (UTA v3) API. Runs locally from the @bitget-ai/bitget-agent-mcp npm package. Needs 3 environment variables to run.