Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Bounty Engineer Agent Commerce

REMOTE · BOUNTY-ENGINEER-X402-PROD.ONRENDER.COM · SCANNED OCT 10

Remote MCP storefront for agent routing, verification, web extraction and x402-paid tools.

+6 this week 75 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2226 tokens (~111/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 73% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • Manipulation not yet verified: only 12 of 21 captured unit(s) of tool text has been judged so far, so we will not certify text no model has read as clean.Unverified
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Bounty Engineer Agent Commerce MCP server?

Bounty Engineer Agent Commerce is a hosted endpoint at https://bounty-engineer-x402-prod.onrender.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · bounty-engineer-x402-prod.onrender.com

# add to Claude Code
claude mcp add --transport http gatoprd-bounty-engineer 'https://bounty-engineer-x402-prod.onrender.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "gatoprd-bounty-engineer": {
      "url": "https://bounty-engineer-x402-prod.onrender.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "gatoprd-bounty-engineer": {
      "type": "http",
      "url": "https://bounty-engineer-x402-prod.onrender.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.gatoprd-bounty-engineer]
url = "https://bounty-engineer-x402-prod.onrender.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gatoprd-bounty-engineer": {
      "type": "remote",
      "url": "https://bounty-engineer-x402-prod.onrender.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add gatoprd-bounty-engineer --url 'https://bounty-engineer-x402-prod.onrender.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  gatoprd-bounty-engineer:
    url: "https://bounty-engineer-x402-prod.onrender.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "gatoprd-bounty-engineer": {
      "Transport": "http",
      "Url": "https://bounty-engineer-x402-prod.onrender.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add gatoprd-bounty-engineer -t streamable-http -u 'https://bounty-engineer-x402-prod.onrender.com/mcp'
// mcp.json
{
  "mcpServers": {
    "gatoprd-bounty-engineer": {
      "type": "http",
      "url": "https://bounty-engineer-x402-prod.onrender.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 10 Oct 26 −2
    • Judged manipulation: pass → unverified ▼ security
    • Tool coverage: 94% → 73% ▼ functional
    • Schema quality: pass → fail ▼ functional
  • 7 Oct 26 +7
    • HSTS header: fail → pass ▲ security
    • Schema quality: 77 → 98 ▼ functional
    • Tool coverage: 9% → 94% ▲ functional
  • 5 Oct 26 +1
    • Schema quality: 552 → 617 ▼ functional
    • New tool “quote_instant_work” functional
  • 3 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
  • 2 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “quote_autonomous_purchase” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 1.2.1 → 1.3.0 functional
  • 1 Oct 26 68

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 10 Oct 2026 · Probed https://bounty-engineer-x402-prod.onrender.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=onrender.com CN=WE1,O=Google Trust Services,C=US 21 Sept 2026 20 Dec 2026 ECDSA 256 ECDSA-SHA256 6eb1e3fe7d0631ea1337bfa4a321c137
SANs: onrender.com, *.onrender.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of bounty-engineer-x402-prod.onrender.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
onrender.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://bounty-engineer-x402-prod.onrender.com/mcp Verified 200
http (plaintext) http://bounty-engineer-x402-prod.onrender.com/mcp HTTPS enforced 301 https://bounty-engineer-x402-prod.onrender.com/mcp
MCP tools · 20 exposed · ~2,066 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
execute_paid_product ~172

Execute one selected paid API tool through native MCP x402 v2. For known product_id and bounded input, the first call only returns PaymentRequired; no paid output is released. With independently authorized budget and validated network, amount and payee, an x402 client retries with params._meta['x402/payment']; only verified paid success includes _meta['x402/payment-response']. Non-idempotent and payment-bearing; do not retry by signing a second transaction after uncertain settlement. Use a dedicated paid_* sibling when a narrower tool is available; use get_product_proof or quote_premium_delivery first if scope or input validity is uncertain.

NameTypeReqDescription
inputobject–Product-specific JSON input. Example for hash: {text:'hello'}
product_idstringyesPaid product id. Example: hash

No output schema declared.

No examples provided.

get_commerce_radar_offer ~82

Buyer-intent discovery for retailer competitor-price/stock and autonomous product-change feeds. Returns true $29.90 Starter and $99.90 Pro plans, free real-URL compatibility preflight, PayPal subscription and one-time 30-day Base USDC options. Does NOT create invoices, make transfers, contact third-party agents or claim buyers exist.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_product_proof ~50

Return one product's method, exact price, schema, sample input and autonomous purchase contract without spending funds. Example: {product_id:'web-extract'}.

NameTypeReqDescription
product_idstringyes–

No output schema declared.

No examples provided.

get_purchase_instructions ~68

Return the direct endpoint, price, payment network and purchase flow for one Bounty Engineer product. Does not spend funds. Example: {product_id:'x402-payment-preflight'}.

NameTypeReqDescription
product_idstringyesProduct id from list_products. Example: x402-payment-preflight

No output schema declared.

No examples provided.

get_workflow_recipe ~85

Get published sample input/output, exact credits for a batch, one-time pack options and prepaid HTTP integration. No payment or own-data execution occurs. Example: {tool:"funding-rates",calls:100}.

NameTypeReqDescription
callsinteger–Planned number of calls. Example: 100
toolstringyesWorkflow product id. Example: funding-rates

No output schema declared.

No examples provided.

list_premium_agent_packs ~145

Use this free catalog only when an authorized agent needs a high-volume one-time Base USDC credit pack ($99.90–$2,499.90) or high-ticket seller-payment and portfolio x402 analysis. Includes exact prices, proof links and safe per-pack checkout URLs. Before any spend use quote_premium_workload for planned credit usage or quote_premium_delivery for a real ledger/workspace input. For small workloads use list_products or per-call x402 instead. The catalog never signs, issues invoices, subscribes, or buys.

NameTypeReqDescription
max_spend_usdnumber–Buyer's maximum authorized total spend in USD; no purchase is made.

No output schema declared.

No examples provided.

list_products ~97

Read-only, free catalog of exact priced x402 tools: JSON/security, funding rates, extraction, seller-payment analysis and agent operations. Use list_products with {} to explore ordinary APIs; for $99.90–$2,499.90 one-time credit packs use list_premium_agent_packs, and for a known product use get_purchase_instructions. No purchase or wallet action occurs. Results are catalog entries, not proof of demand.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

paid_agent_purchase_firewall ~83

Evaluate a proposed agent purchase for hard-budget, duplicate-payment, seller/payTo drift and purchase-safety conditions before execution. Native MCP x402. Use get_product_proof for the current exact input schema.

NameTypeReqDescription
inputobject–Purchase-firewall request matching the published product schema. Call get_product_proof with product_id agent-purchase-firewall first.

No output schema declared.

No examples provided.

paid_funding_loop ~72

Screen fresh external funded tasks for payout rail, escrow, deadline and zero-deposit conditions. Native x402 payment, no API key. Example: {input:{limit:20,rail:'base'}}.

NameTypeReqDescription
inputobject–Funding-loop request. Example: {limit:20,rail:'base'}

No output schema declared.

No examples provided.

paid_funding_rates ~82

Fetch normalized live perpetual-futures funding rates with venue fallback and market context. Native x402 payment, no API key. Example: {input:{symbol:'BTCUSDT',providers:['binance','bybit']}}.

NameTypeReqDescription
inputobject–Funding-rate request. Example: {symbol:'BTCUSDT',providers:['binance','bybit']}

No output schema declared.

No examples provided.

paid_json_contract_check ~102

Validate structured JSON against the supported deterministic JSON Schema subset and return exact error pointers. Native x402 payment. Example: {input:{value:{price:25},schema:{type:'object',required:['price'],properties:{price:{type:'number'}}}}}.

NameTypeReqDescription
inputobject–JSON value/text plus schema. Example: {value:{price:25},schema:{type:'object',required:['price'],properties:{price:{type:'number'}}}}

No output schema declared.

No examples provided.

paid_web_extract ~74

Extract one public HTML page into clean Markdown, text, links, metadata and source hashes. Native x402 payment, no API key. Example: {input:{url:'https://example.com'}}.

NameTypeReqDescription
inputobject–Web extraction input. Required field: url. Example: {url:'https://example.com'}

No output schema declared.

No examples provided.

paid_x402_payment_preflight ~86

Preflight an x402 seller/payment contract before an autonomous buyer commits funds; checks payment-path risks without authorizing a purchase. Native MCP x402. Use get_product_proof for the current exact input schema.

NameTypeReqDescription
inputobject–x402 preflight request matching the published product schema. Call get_product_proof with product_id x402-payment-preflight first.

No output schema declared.

No examples provided.

qualify_premium_buyer ~213

Use when you have a real buyer-authorized budget and a concrete agent workflow. Matches one-workspace ledger reconciliation to the $149.90 Command Center, cross-workspace settlement controls to the $999.90 Tower ONLY with confirmed multiple workspaces, or high-volume prepaid credits ONLY with lower total declared cash cost. Always use the free input quote first. No contact to other buyers, signature, invoice, automatic purchase or payment. Example: {goal:'reconcile agent seller payment ledger receipts',max_spend_usd:250,workspaces:1}.

NameTypeReqDescription
callsinteger–For prepaid workloads, expected genuine tool call count
goalstringyesThe buyer's real operational goal, not marketing text
max_spend_usdnumberyesHard buyer-authorized USD ceiling; the agent must have buyer permission
toolstring–For prepaid workloads, a current supported tool id
workspacesinteger–Actual number of buyer-owned workspaces when relevant

No output schema declared.

No examples provided.

quote_autonomous_purchase ~145

Given an agent goal and hard USD budget, return a buyer-controlled value ladder: cheapest relevant proof, recommended value, optional higher-outcome upgrade, and executable purchase plan. This tool itself is free and never spends funds. Example: {goal:'extract a public webpage',max_price_usd:0.01,preferred_rail:'x402'}.

NameTypeReqDescription
goalstringyesPlain-language goal. Example: extract a public webpage
max_price_usdnumber–Hard total USD price ceiling; never exceeded. Example: 0.01
preferred_railstring–Preferred payment rail. Base USDC is the preferred direct wallet fallback.

No output schema declared.

No examples provided.

quote_batch_web_intelligence ~100

Quote the fixed cost and validate up to 10 public URLs without fetching them, spending USDC or creating an invoice. The paid batch returns provenance-linked snippets, content hashes, titles and optional client-supplied baseline comparisons. Use HTTP POST /v1/batch-web-intelligence after independently confirming the x402 payment challenge; the free quote is never a purchase.

NameTypeReqDescription
previous_hashesobject––
urlsarrayyes–

No output schema declared.

No examples provided.

quote_instant_work ~97

Zero-cost deterministic computation of the actual buyer-submitted reconciliation or quality task. Returns output SHA-256 and readiness; never returns the paid full result or spends USDC. Example: {input:{task:'quality',required:['id'],records:[{id:'A'}]}}.

NameTypeReqDescription
inputobjectyesInstant-work JSON input. Example: {task:'quality',required:['id'],records:[{id:'A'}]}

No output schema declared.

No examples provided.

quote_premium_delivery ~94

Validate actual caller-supplied Command Center or Control Tower input before authorizing an expensive analysis. Returns input hash, counts, deliverable list, posted price and a cheaper standalone alternative when one workspace suffices. Does not return the paid analysis, verify receipts on chain, sign or transfer funds.

NameTypeReqDescription
inputobjectyes–
max_spend_usdnumberyes–
toolstringyes–

No output schema declared.

No examples provided.

quote_premium_workload ~86

Free quote for up to 20 tool/call rows under a hard total budget. Compares one shared-key package against pay-per-call pricing and recommends a prepaid package only when it covers all tools and costs less. Includes smaller and funding-only alternatives; does not buy or create invoices.

NameTypeReqDescription
max_spend_usdnumberyes–
workloadarrayyes–

No output schema declared.

No examples provided.

recommend_paid_tool ~133

Free single-tool product recommendation by plain-language goal. Use for one specific agent task, not to assume budget approval or execute a payment. For multi-workspace settlement, reused receipts and shared agent budgets consider enterprise-commerce-control-tower; for one workspace seller ledger reconciliation consider agent-commerce-command-center. Before authorizing expensive analysis use quote_premium_delivery; for volume discounts use quote_premium_workload. A no-match result means DO_NOT_BUY. Example: {goal:'verify an x402 seller before paying'}.

NameTypeReqDescription
goalstringyesPlain-language buyer goal. Example: verify an x402 seller before paying

No output schema declared.

No examples provided.

Common questions

What is the Bounty Engineer Agent Commerce MCP server?

Bounty Engineer Agent Commerce is an MCP server listed in the public MCP registry as io.github.gatoprd/bounty-engineer. Remote MCP storefront for agent routing, verification, web extraction and x402-paid tools. This page covers its hosted endpoint (https://bounty-engineer-x402-prod.onrender.com/mcp).

Is the Bounty Engineer Agent Commerce MCP server safe to use?

Bounty Engineer Agent Commerce scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Bounty Engineer Agent Commerce MCP server expose?

Bounty Engineer Agent Commerce exposes 20 tools: list_products, get_commerce_radar_offer, quote_batch_web_intelligence, list_premium_agent_packs, qualify_premium_buyer, and 15 more. Their descriptions and schemas cost roughly 2,066 tokens of context every time the server is loaded.

Does the Bounty Engineer Agent Commerce MCP server require authentication?

No. We connected to Bounty Engineer Agent Commerce without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Bounty Engineer Agent Commerce MCP server still maintained?

Bounty Engineer Agent Commerce is still listed as active in the MCP registry. We last reached this channel on 10 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.