Home / MCP registry index / io.github.gatoprd/bounty-engineer
Bounty Engineer Agent Commerce
io.github.gatoprd/bounty-engineer in the official MCP registry.
Endpoint https://bounty-engineer-x402-prod.onrender.com/mcp. Source: github.com/gatoprd/InstaVeil.
The registry describes it as: Remote MCP storefront for agent routing, verification, web extraction and x402-paid tools.
We read its 20 tools on 2026-10-21. 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
list_products get_commerce_radar_offer quote_batch_web_intelligence list_premium_agent_packs qualify_premium_buyer quote_premium_workload quote_premium_delivery recommend_paid_tool get_purchase_instructions quote_autonomous_purchase get_product_proof quote_instant_work paid_web_extract paid_funding_loop paid_funding_rates paid_json_contract_check paid_x402_payment_preflight paid_agent_purchase_firewall execute_paid_product get_workflow_recipe
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-gatoprd-bounty-engineer)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.