Home / MCP registry index / app.agentbit/mcp
AgentBIT
app.agentbit/mcp in the official MCP registry.
Endpoint https://agentbit.app/mcp. Source: github.com/socialbitro/agentbit-mcp.
The registry describes it as: x402 router-proxy + 79 keyless pay-per-call tools on Base. Pay once, we run the best tool.
We read its 100 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
agentbit_discover agentbit_route agentbit.address_eip55 agentbit.agent_counter agentbit.agent_list agentbit.agent_memory agentbit.ai_ask agentbit.ai_classify agentbit.ai_extract agentbit.ai_summarize agentbit.ai_translate agentbit.amazon_search agentbit.browser_render agentbit.business_identity agentbit.company_brief agentbit.company_enrich agentbit.company_research agentbit.content_moderate agentbit.contract_audit agentbit.convert_csv_json agentbit.convert_json_csv agentbit.convert_xml_json agentbit.counterparty_risk agentbit.counterparty_verify agentbit.crypto_trader_kit agentbit.decode_base58 agentbit.decode_base64 agentbit.decode_hex agentbit.decode_url agentbit.defi_yields agentbit.discover agentbit.dns_inspect agentbit.domain_dossier agentbit.domain_intel agentbit.email_deliverability agentbit.encode_base58 agentbit.encode_base64 agentbit.encode_hex agentbit.encode_url agentbit.endpoint_monitor agentbit.feed_read agentbit.financial_document agentbit.fx agentbit.hash_hmac agentbit.hash_keccak256 agentbit.hash_md5 agentbit.hash_sha1 agentbit.hash_sha256 agentbit.hash_sha512 agentbit.ip_intel agentbit.json_diff agentbit.json_validate agentbit.jwt_decode agentbit.maps_reviews agentbit.maps_search agentbit.market_sentiment agentbit.news_search agentbit.onchain_gas agentbit.onchain_read agentbit.paper_search and 40 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/app-agentbit-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.