Yultrace Bounty Feed
Search aggregated Web3 bounty listings from nine platforms so an agent can surface paid audit or dev work while you validate what to build next.
Overview
Yultrace Bounty Feed is an MCP server for the Idea phase that searches 386 bounty rows across nine sources for agent-assisted opportunity discovery.
What is this MCP server?
- 386 indexed bounty rows across nine named sources
- Sources include Bountycaster, Dework, Sherlock, Algora, GitHub, and Reddit
- Dedicated MCP remote (mcp2) for streamable HTTP agent access
- Search-oriented surface for agent-ranked opportunity pulls
- Version 0.1.1 public catalog entry
- 386 bounty rows indexed
- 9 bounty sources (Bountycaster, Dework, Sherlock, Algora, GitHub, Reddit, and related)
- Server version 0.1.1
What problem does it solve?
Builders waste hours jumping between bounty boards and social feeds because no agent hook aggregates listings in one searchable index.
Who is it for?
Indie Web3 or security freelancers using Claude Code or Cursor to scan bounties before picking a validate-or-build bet.
Skip if: Teams that need CRM-style deal tracking or non-bounty job boards without MCP integration.
What do I get? / Deliverables
Your agent can query a multi-source bounty index and return relevant paid work leads while you still scoping what to ship.
- Agent-queryable bounty search across nine sources
- Access to a 386-row indexed feed described in catalog metadata
Recommended MCP Servers
Journey fit
How it compares
Bounty discovery MCP feed, not an on-chain audit runner or generic job-site scraper skill.
Common Questions / FAQ
Who is Yultrace Bounty Feed for?
Solo builders and bounty hunters who want their coding agent to search consolidated Web3 bounty listings from multiple platforms.
When should I use Yultrace Bounty Feed?
Early in the journey when you are discovering paid audit, protocol, or dev opportunities before committing to a product scope.
How do I add Yultrace Bounty Feed to my agent?
Add the published streamable HTTP MCP remote URL (mcp2 endpoint) in your agent’s MCP server configuration.