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

kestrel

https://kestrel.perch-app.workers.dev

Registry code: 672e00f878d2496d

api record

Watch any URL for changes: baseline, then check for a diff. Free, no signup/key.

from a public catalogue that lists it, not from the operator

endpoint
https://kestrel.perch-app.workers.dev/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 kestrel live?
Yes — it answered the hub's last check (checked 14h ago). It answered 100% of checks over the last 30 days.
Is kestrel free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does kestrel have?
4 tools: create_watch, delete_watch, check_watch, list_watches.
Is kestrel 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 99.8%· all time 99.8%

latency
893ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 415 checks · signed record
  • degraded → live
_ what it is for
topic
search & web scraping & fetch
used for
  • watch a web page for changes
  • check a watched page for diffs
  • list page watches
  • delete a page watch
takes → gives
text → data
tools
2 reads2 changes data
_ 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
4 auth-required 4 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.

  • create_watch changes data auth-required never probed

    Start monitoring a web page (or JSON/text URL) for changes. Captures a baseline snapshot now. Returns a watch_id and a token — save the token; it's how you check and manage your watches later. Pass an existing token to add more watches under the same account.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Absolute http(s) URL to monitor, e.g. https://example.com/pricing"
    },
    "label": {
      "type": "string",
      "description": "Optional human label for this watch."
    },
    "token": {
      "type": "string",
      "description": "Optional. Your existing Kestrel token to group this watch with others. Omit to get a new token."
    }
  }
}
    arguments 20 lines
  • delete_watch changes data auth-required never probed

    Stop monitoring a page and delete the watch.

    mcp-tool

    {
  "type": "object",
  "required": [
    "watch_id",
    "token"
  ],
  "properties": {
    "token": {
      "type": "string"
    },
    "watch_id": {
      "type": "string"
    }
  }
}
    arguments 15 lines
  • check_watch reads auth-required 19h ago

    Re-fetch a watched page and report whether it changed since the last check, with a short list of added/removed content lines. Updates the baseline to the new content. Call this every time you want the latest status (e.g. each run/heartbeat).

    mcp-tool

    {
  "type": "object",
  "required": [
    "watch_id",
    "token"
  ],
  "properties": {
    "token": {
      "type": "string",
      "description": "The token returned by create_watch."
    },
    "watch_id": {
      "type": "string"
    }
  }
}
    arguments 16 lines
  • list_watches reads auth-required 19h ago

    List all watches under your token, with per-watch check/change counts.

    mcp-tool

    {
  "type": "object",
  "required": [
    "token"
  ],
  "properties": {
    "token": {
      "type": "string"
    }
  }
}
    arguments 11 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 672e00f878d2496d.

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