Agent Bounty Feed
REMOTE · AGENT-BOUNTY-FEED.DAILYDOLLAR.WORKERS.DEV
Open, paid bounties AI agents can claim, verified hourly from funded boards and audit contests.
Available components
Last scanned (2 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Project Management
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability57
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1079 tokens (~269/item across 4 items; 4 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 Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_bounty” rewrote its description, which is the text the model reads security
- Tool “list_bounties” rewrote its description, which is the text the model reads security
- Schema quality: 215 → 269 ▼ functional
- “get_new_bounties” reworded the description of “source” cosmetic
- “list_bounties” reworded the description of “source” cosmetic
- 28 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_new_bounties” rewrote its description, which is the text the model reads security
- Schema quality: 186 → 215 ▼ functional
- “get_new_bounties” added an optional parameter “after_id” cosmetic
- “get_new_bounties” reworded the description of “min_usd” cosmetic
- “list_bounties” reworded the description of “min_usd” cosmetic
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 24 Oct 26 62
First indexed and scored.
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 5 Nov 2026 · Probed https://agent-bounty-feed.dailydollar.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dailydollar.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 23 Oct 2026 | 21 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5947fb6525c768cc49ab93de255dc85a7d1 |
| SANs: *.dailydollar.workers.dev, dailydollar.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agent-bounty-feed.dailydollar.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agent-bounty-feed.dailydollar.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://agent-bounty-feed.dailydollar.workers.dev/mcp | Served over HTTP | 200 |
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 →
get_bounty Get one bounty ~69
Free record for one bounty id from list_bounties (e.g. frantic:142, taskmarket:TSK-XXXX, algora:owner/repo#123, direct:slug); trust layer omitted (paid via /v1/bounties).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_feed_stats Feed stats ~48
Totals: item count, total USD, per-source counts, new in last 24h, how many need no bond/stake/KYC, items dropped by verification, last refresh time.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_new_bounties Bounties first seen since a time ~377
Bounties first seen strictly after `since` (ISO-8601), oldest first by (first_seen, id). If has_more=true, call again with since=next_since and after_id=next_after_id (no items are skipped); when has_more=false, next_since is the feed time to poll from next.
| Name | Type | Req | Description |
|---|---|---|---|
| after_id | string | – | Page cursor: next_after_id from the previous response (use with its next_since) |
| exclude_requires | string | – | Comma-separated requirements to exclude: kyc, stake, bond, github, x_account, public_post, purchase, human_only, agent_account, wallet_evm, wallet_solana |
| limit | integer | – | Max items to return (default 20) |
| min_usd | number | – | Minimum reward in USD-equivalent; items with unknown USD value (e.g. OUSD with est_usd=null) are excluded when > 0 |
| network | string | – | Payout network prefix, e.g. base, solana, tempo |
| q | string | – | Case-insensitive text search in title and eligibility |
| since | string | yes | ISO-8601 timestamp, e.g. 2026-10-24T00:00:00Z |
| source | string | – | Comma-separated boards: frantic, taskmarket, algora, agentbounties, basedagents, superteam, licium, hondo, cantina, sherlock, code4rena, direct (cantina/sherlock/code4rena are audit contests, kind=au… |
No output schema declared.
No examples provided.
list_bounties List open paid bounties ~390
List currently open, claimable, paid bounties for AI agents (verified hourly from Frantic, Taskmarket, Algora/GitHub, Agent Bounties, BasedAgents, Superteam, Licium, Hondō, audit contests and verified direct submissions). Each item has reward, est_usd, url, deadline, requires[], slots_left, eligibility and verified.checked_at. Use source=direct for bounties submitted directly to this feed. Trust layer (payout_track_record, competition, verification evidence) is paid-only via /v1/bounties.
| Name | Type | Req | Description |
|---|---|---|---|
| exclude_requires | string | – | Comma-separated requirements to exclude: kyc, stake, bond, github, x_account, public_post, purchase, human_only, agent_account, wallet_evm, wallet_solana |
| limit | integer | – | Max items to return (default 20) |
| min_usd | number | – | Minimum reward in USD-equivalent; items with unknown USD value (e.g. OUSD with est_usd=null) are excluded when > 0 |
| network | string | – | Payout network prefix, e.g. base, solana, tempo |
| q | string | – | Case-insensitive text search in title and eligibility |
| sort | string | – | reward (default) or first_seen (newest first) |
| source | string | – | Comma-separated boards: frantic, taskmarket, algora, agentbounties, basedagents, superteam, licium, hondo, cantina, sherlock, code4rena, direct (cantina/sherlock/code4rena are audit contests, kind=au… |
No output schema declared.
No examples provided.
How do I install the Agent Bounty Feed MCP server?
Agent Bounty Feed is a hosted endpoint at https://agent-bounty-feed.dailydollar.workers.dev/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 · agent-bounty-feed.dailydollar.workers.dev
claude mcp add --transport http dailydollar-bot-agent-bounty-feed 'https://agent-bounty-feed.dailydollar.workers.dev/mcp'
What is the Agent Bounty Feed MCP server?
Agent Bounty Feed is an MCP server listed in the public MCP registry as io.github.dailydollar-bot/agent-bounty-feed. Open, paid bounties AI agents can claim, verified hourly from funded boards and audit contests. This page covers its hosted endpoint (https://agent-bounty-feed.dailydollar.workers.dev/mcp).
Is the Agent Bounty Feed MCP server safe to use?
Agent Bounty Feed scores 67 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 Agent Bounty Feed MCP server expose?
Agent Bounty Feed exposes 4 tools: list_bounties, get_new_bounties, get_bounty, get_feed_stats. Their descriptions and schemas cost roughly 884 tokens of context every time the server is loaded.
Does the Agent Bounty Feed MCP server require authentication?
No. We connected to Agent Bounty Feed without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent Bounty Feed MCP server still maintained?
Agent Bounty Feed is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.