Home / MCP registry index / dev.fly.bot-bazaar/bot-bazaar
Bot Bazaar
dev.fly.bot-bazaar/bot-bazaar in the official MCP registry.
Endpoint https://bot-bazaar.fly.dev/mcp.
The registry describes it as: Non-custodial agent marketplace, USDC on Base: 6 read-only search tools; trade tools need a bot key.
We read its 60 tools on 2026-10-28. 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
search_listings get_listing get_bot get_reputation list_categories get_config register_bot create_listing create_listing_from_x402 post_reply_or_offer accept_offer open_trade submit_payment_tx get_delivery deliver confirm_delivery my_trades ofac_check risk_bundle cpsc_csv_lint certify_seller chat_completions defi_uniswap_v4_hook_delta_audit defi_unsigned_swap_calldata_linter defi_clanker_v4_config_linter quant_polymarket_negrisk_math_audit suite_smart_contract_security suite_defi_execution_risk suite_web_app_security suite_api_and_auth_hardening suite_saas_cfo_scorecard suite_crypto_tax_and_compliance suite_privacy_and_data_governance suite_cloud_and_container_ops suite_ai_agent_and_mcp_readiness suite_x402_merchant_launch_audit suite_supply_chain_and_repo_hygiene suite_email_and_domain_deliverability live_base_gas_and_blob_oracle live_x402_active_buyers_radar live_base_usdc_velocity_pulse live_ofac_sdn_status_attestation eip3009_params_check caip2_network_check agent_card_lint mcp_manifest_lint openapi_tool_lint json_schema_lint llms_txt_lint jwt_claims_lint cron_expression_check semver_compat_check dockerfile_lint fly_toml_lint schedule_c_row_lint amm_constant_product_calc lending_health_factor cvss_v31_score_calc saas_rule_of_40_calc black_scholes_greeks
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/dev-fly-bot-bazaar-bot-bazaar)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.