{"id":"acuvity-mcp-server-bitcoin","name":"mcp-server-bitcoin","homepage":"https://hub.docker.com/r/acuvity/mcp-server-bitcoin","repo_url":"https://hub.docker.com/r/acuvity/mcp-server-bitcoin","category":"infrastructure","subcategories":[],"tags":["mcp","bitcoin","blockchain","tooling","agent-integration"],"what_it_does":"An MCP (Model Context Protocol) server intended to expose Bitcoin-related capabilities to AI agents via MCP tools (e.g., querying Bitcoin data).","use_cases":["Letting an AI agent fetch Bitcoin/chain-related information through MCP tools","Building agent workflows that require on-demand blockchain data access","Prototyping agent capabilities around addresses/transactions/block lookups"],"not_for":["Custodial wallet management or signing transactions","High-assurance financial operations without independent validation","Environments requiring strict compliance documentation for the upstream data source"],"best_when":null,"avoid_when":null,"alternatives":["Directly calling a Bitcoin/chain explorer REST API (where available) from the agent","Using a Bitcoin node/RPC and integrating it with a custom agent tool","Other MCP Bitcoin/chain-data servers (if you need the MCP abstraction)"],"af_score":34.2,"security_score":31.5,"reliability_score":23.8,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:35:13.085306+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":[],"oauth":false,"scopes":false,"notes":"No authentication details were provided in the supplied package information, so auth approach could not be confirmed."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Pricing not provided; MCP servers are often self-hosted and may rely on upstream API providers with their own costs."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":34.2,"security_score":31.5,"reliability_score":23.8,"mcp_server_quality":45.0,"documentation_accuracy":30.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":50.0,"rate_limit_clarity":20.0,"tls_enforcement":50.0,"auth_strength":30.0,"scope_granularity":0.0,"dependency_hygiene":40.0,"secret_handling":40.0,"security_notes":"No repo/manifest details were provided to verify TLS configuration, dependency CVEs, or secret handling practices. Treat upstream calls (e.g., to explorers/nodes) and any API keys as sensitive, and validate outputs for financial use.","uptime_documented":0.0,"version_stability":40.0,"breaking_changes_history":30.0,"error_recovery":25.0,"idempotency_support":"false","idempotency_notes":"Idempotency behavior is not described in the provided information.","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Upstream Bitcoin data sources may impose rate limits or inconsistent latency; agents should expect intermittent failures/timeouts.","If the MCP tools are thin wrappers, agents may need to handle partial data or unsupported parameters."]}}