_ registry / mcp streamable-http · checked 1h ago

Base Daily Brief

https://basedailybrief.vercel.app

Registry code: e8910a9087a74588

api record

Paid daily news bulletin about the Base blockchain ecosystem, fetched by date or latest, with an optional 30-day subscription.

endpoint
https://basedailybrief.vercel.app/mcp
protocol
streamable-http ·2024-11-05
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Base Daily Brief live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is Base Daily Brief free to use?
Yes — the hub reached it with no key and no payment.
What tools does Base Daily Brief have?
4 tools: subscribe, get_latest_bulletin, list_bulletins, get_bulletin.
Is Base Daily Brief safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99%

90 days 98.9%· all time 98.9%

latency
1,120ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 366 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • get the latest daily bulletin
  • get a bulletin by date
  • list bulletins
  • subscribe for unlimited access
takes → gives
text → text
tools
3 reads1 moves money
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
3 open 1 never probed 3 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_latest_bulletin reads open 22h ago

    Get the latest Base Daily Brief bulletin. Costs $0.01 USDC via x402 on Base Mainnet. Use wrapFetchWithPayment or awal pay-for-service to pay and retrieve content.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "locale": {
          "enum": [
            "en",
            "tr"
          ],
          "type": "string",
          "default": "en",
          "description": "Language: en (English) or tr (Turkish)"
        }
      }
    }
    arguments 14 lines
  • list_bulletins reads open 22h ago

    List all available Base Daily Brief bulletins. Free — no payment required.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "locale": {
          "enum": [
            "en",
            "tr"
          ],
          "type": "string",
          "default": "en",
          "description": "Language: en (English) or tr (Turkish)"
        }
      }
    }
    arguments 14 lines
  • get_bulletin reads open 22h ago

    Get a specific Base Daily Brief bulletin by date. Costs $0.01 USDC via x402 on Base Mainnet. Use wrapFetchWithPayment or awal pay-for-service to pay and retrieve content.

    mcp-tool

    {
      "type": "object",
      "required": [
        "date"
      ],
      "properties": {
        "date": {
          "type": "string",
          "description": "Date in YYYY-MM-DD format, e.g. 2026-08-18"
        },
        "locale": {
          "enum": [
            "en",
            "tr"
          ],
          "type": "string",
          "default": "en",
          "description": "Language: en (English) or tr (Turkish)"
        }
      }
    }
    arguments 21 lines
  • subscribe moves money unknown never probed

    Subscribe for 30-day unlimited access. Costs $0.25 USDC via x402 on Base Mainnet. Returns an API key valid for 30 days — use X-API-Key header to bypass per-call payments.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "callbackUrl": {
          "type": "string",
          "description": "Optional HTTPS webhook URL to receive daily bulletins automatically."
        }
      }
    }
    arguments 9 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id e8910a9087a74588.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e8910a9087a74588/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/e8910a9087a74588/badge.svg)](https://brick.blue/agent/e8910a9087a74588?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.