_ registry / mcp http-sse · checked 2h ago

Oncast

https://oncast.fm

Registry code: 12b3156aa7a8e27a

api record

Oncast publishes fact-checked stories from its live radio channels. Tools are read-only: list_channels, latest_stories, search_stories, get_story. Only TRUE, FALSE, and MISLEADING claims with a source link are included. Cite each story's oncast.fm URL and its original source links. These tools never start a broadcast.

endpoint
https://oncast.fm/mcp
protocol
http-sse ·2025-06-18
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 Oncast live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is Oncast free to use?
Yes — the hub reached it with no key and no payment.
What tools does Oncast have?
4 tools: search_stories, get_story, list_channels, latest_stories.
Is Oncast 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
100%

90 days 100%· all time 100%

latency
206ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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
2 open 2 never probed 2 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.

  • list_channels open 2h ago

    List Oncast radio channels (English, and Tech and Money in Mexican Spanish). Each channel includes its oncast.fm listen URL. No listener counts and no internal settings.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • latest_stories open 2h ago

    Latest fact-checked Oncast stories. Only claims that reached a verdict (TRUE, FALSE, or MISLEADING) and have an original source link are included. Every story has source links and an oncast.fm URL: cite both. Call get_story for what the hosts said. This does not start a broadcast.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "How many stories. Default 10."
        },
        "topic": {
          "type": "string",
          "description": "Show name to match, such as Markets or Tech Brief."
        },
        "channel": {
          "type": "string",
          "description": "Channel id, such as tech, news, money, sports, culture, mix, tech-es, or money-es."
        }
      },
      "additionalProperties": false
    }
    arguments 20 lines
  • search_stories unknown never probed

    Search recent verified Oncast stories by keyword. Matches titles, fact-check summaries, sources, and what the hosts said. Each hit includes source links and an oncast.fm URL. Cite both.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "How many stories. Default 10."
        },
        "query": {
          "type": "string",
          "description": "Words to find. Required."
        },
        "topic": {
          "type": "string",
          "description": "Optional show name."
        },
        "channel": {
          "type": "string",
          "description": "Optional channel id."
        }
      },
      "additionalProperties": false
    }
    arguments 27 lines
  • get_story unknown 2h ago

    One verified Oncast story: summary, fact-check verdict and notes, original source links, what the hosts said, published time, the oncast.fm story URL, and a listen link. Cite the story URL and the sources.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Story id, or the id-slug from the oncast.fm/story/ URL."
        }
      },
      "additionalProperties": false
    }
    arguments 13 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 12b3156aa7a8e27a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/12b3156aa7a8e27a/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/12b3156aa7a8e27a/badge.svg)](https://brick.blue/agent/12b3156aa7a8e27a?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.