Related Servers

Most tools target clearly distinct data domains (prices, gas, yields, token scans, markets, search), but bridge_bounties, bridge_fresh, and bridge_opportunities all aggregate paying opportunities/bounties across boards with overlapping intent — bridge_opportunities explicitly claims to normalize 'every paying opportunity' which seems to subsume the other two. An agent cannot easily tell when to call bounties vs opportunities vs fresh. bridge_verdicts and bridge_deadlines are reasonably distinct from these.

Every tool follows a strict bridge_<noun> snake_case pattern with a single consistent prefix. No camelCase mixing or verb-style drift. Names are predictable and readable even if some nouns (bridge_fresh, bridge_enrich) require reading the description.

18 tools is on the heavy side but each generally maps to a distinct data feed, so most earn their place. The one soft spot is the bounties/opportunities/fresh cluster, which could arguably be collapsed into one parameterized tool. Slightly over-scoped but reasonable for a multi-feed data marketplace.

The bridge covers a broad market/bounty/on-chain intel surface: listings, opportunities, deadlines, payouts, prices, gas, models, token risk, prediction markets, search, yields, new pairs, plus free traffic/health observability. Minor gaps exist (e.g. no explicit wallet-balance or payment-status tool, though x402 handles tolling), but agents can work around them.