# 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.

- Trust score: 67/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `agent-bounty-feed.dailydollar.workers.dev`: 67/100 (this document), [markdown](https://verifymcp.io/servers/dailydollar-bot-agent-bounty-feed/agent-bounty-feed.md), [page](https://verifymcp.io/servers/dailydollar-bot-agent-bounty-feed/agent-bounty-feed)

## Channel facts

- Endpoint: `https://agent-bounty-feed.dailydollar.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 94% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http dailydollar-bot-agent-bounty-feed 'https://agent-bounty-feed.dailydollar.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dailydollar-bot-agent-bounty-feed": {
      "url": "https://agent-bounty-feed.dailydollar.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dailydollar-bot-agent-bounty-feed": {
      "type": "http",
      "url": "https://agent-bounty-feed.dailydollar.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dailydollar-bot-agent-bounty-feed]
url = "https://agent-bounty-feed.dailydollar.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dailydollar-bot-agent-bounty-feed": {
      "type": "remote",
      "url": "https://agent-bounty-feed.dailydollar.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dailydollar-bot-agent-bounty-feed --url 'https://agent-bounty-feed.dailydollar.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dailydollar-bot-agent-bounty-feed:
    url: "https://agent-bounty-feed.dailydollar.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dailydollar-bot-agent-bounty-feed": {
      "Transport": "http",
      "Url": "https://agent-bounty-feed.dailydollar.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dailydollar-bot-agent-bounty-feed -t streamable-http -u 'https://agent-bounty-feed.dailydollar.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dailydollar-bot-agent-bounty-feed": {
      "type": "http",
      "url": "https://agent-bounty-feed.dailydollar.workers.dev/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 67, +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.

### 2026-11-02 (score 66, +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.

### 2026-10-30 (score 65, +1)

- [security] 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
- [functional regression] Schema quality: 215 → 269
- [cosmetic] “get_new_bounties” reworded the description of “source”
- [cosmetic] “list_bounties” reworded the description of “source”

### 2026-10-28 (score 64, 0)

- [security] 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
- [functional regression] Schema quality: 186 → 215
- [cosmetic] “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”

### 2026-10-27 (score 64, +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.

### 2026-10-25 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-24 (score 62)

First indexed and scored.

## MCP tools (4)

### `list_bounties` (~390 tokens)

List open paid bounties

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.

Input parameters:

- `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…

### `get_new_bounties` (~377 tokens)

Bounties first seen since a time

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.

Input parameters:

- `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, required): 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…

### `get_bounty` (~69 tokens)

Get one bounty

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).

Input parameters:

- `id` (string, required)

### `get_feed_stats` (~48 tokens)

Feed stats

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dailydollar-bot-agent-bounty-feed/agent-bounty-feed#diagnostics

## Score history

- 2026-11-05: 67
- 2026-11-04: 67
- 2026-11-03: 66
- 2026-11-02: 66
- 2026-11-01: 65
- 2026-10-31: 65
- 2026-10-30: 65
- 2026-10-29: 64
- 2026-10-28: 64
- 2026-10-27: 64
- 2026-10-26: 63
- 2026-10-25: 63
- 2026-10-24: 62

## Common questions

### 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.

## Links

- Remote endpoint: https://agent-bounty-feed.dailydollar.workers.dev/mcp
- Repository: https://github.com/dailydollar-bot/agent-bounty-feed
- Website: https://dailydollar-bot.github.io/agent-bounty-feed/
- Changelog RSS feed: https://verifymcp.io/servers/dailydollar-bot-agent-bounty-feed/agent-bounty-feed.xml
- Changelog JSON feed: https://verifymcp.io/servers/dailydollar-bot-agent-bounty-feed/agent-bounty-feed.json
- HTML version of this page: https://verifymcp.io/servers/dailydollar-bot-agent-bounty-feed/agent-bounty-feed