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

DAP Bellwether

https://bellwether.dap.solutions

Registry code: 5ffcb7516b743319

api record

DAP Bellwether monitors financial regulators in Canada, the United States, the United Kingdom and the European Union, and records what they publish. Coverage starts from when this service first collected each source, so it is not a complete historical archive. Say so if a user asks about material older than the coverage window. Use list_coverage before concluding that something was not published, so an absence of results is not mistaken for an absence of regulation. This is a public information service. It is not legal or compliance advice.

endpoint
https://bellwether.dap.solutions/mcp
protocol
streamable-http ·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 DAP Bellwether live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is DAP Bellwether free to use?
Yes — the hub reached it with no key and no payment.
What tools does DAP Bellwether have?
4 tools: get_regulatory_change, recent_regulatory_changes, list_coverage, search_regulatory_changes.
Is DAP Bellwether 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.6%

90 days 99.7%· all time 99.7%

latency
161ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 393 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
  • unknown → live
_ what it is for
used for
  • search financial regulator publications
  • list recent regulatory changes
  • get revision history of a publication
  • list monitored regulators
takes → gives
text → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 2 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
6

distinct

settlements
8

last 2026-11-05

received on chain
0.08 USDC

shared-payto

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

  • recent_regulatory_changes reads open 15h ago

    List the most recent regulatory publications across all covered regulators, newest first. Use when asked what is new, what happened this week, or for a general catch up rather than a specific topic.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "days": {
          "type": "integer",
          "default": 14,
          "maximum": 365,
          "minimum": 1,
          "description": "Look back this many days."
        },
        "limit": {
          "type": "integer",
          "default": 25,
          "maximum": 100,
          "minimum": 1,
          "description": "Maximum records to return."
        },
        "jurisdiction": {
          "enum": [
            "CA",
            "US",
            "UK",
            "EU"
          ],
          "type": "string",
          "description": "Restrict to one jurisdiction."
        }
      },
      "additionalProperties": false
    }
    arguments 30 lines
  • list_coverage reads open 1h ago

    List every regulator and feed being monitored, with when each was last collected successfully and how fresh the data is. Use to answer what this connector covers, or to check whether a jurisdiction is being watched before relying on an absence of results.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • search_regulatory_changes reads open 15h ago

    Search regulatory publications collected from financial regulators in Canada, the United States, the United Kingdom and the European Union. Use for questions about what a regulator has published on a topic, or what has changed in a date range. Returns the most recent matches first.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 20,
          "maximum": 100,
          "minimum": 1,
          "description": "Maximum records to return."
        },
        "query": {
          "type": "string",
          "description": "Keywords matched against title and summary, for example \"liquidity\" or \"crypto-asset\"."
        },
        "since": {
          "type": "string",
          "description": "ISO 8601 date or timestamp. Only items published on or after this."
        },
        "until": {
          "type": "string",
          "description": "ISO 8601 date or timestamp. Only items published on or before this."
        },
        "category": {
          "enum": [
            "rules",
            "enforcement",
            "guidance",
            "news"
          ],
          "type": "string",
          "description": "Restrict to a publication type."
        },
        "regulator": {
          "type": "string",
          "description": "Restrict to one regulator by short name, for example OSFI, SEC, FCA, ESMA."
        },
        "jurisdiction": {
          "enum": [
            "CA",
            "US",
            "UK",
            "EU"
          ],
          "type": "string",
          "description": "Restrict to one jurisdiction."
        }
      },
      "additionalProperties": false
    }
    arguments 49 lines
  • get_regulatory_change reads unknown 15h ago

    Retrieve one record in full, including every revision observed since it was first seen. Use this to answer whether a document was amended after publication and what moved. The id comes from a search or recent result.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Record id from a search or recent result."
        }
      },
      "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 5ffcb7516b743319.

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

_ also on dap.solutions 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.