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

catchlog

https://catchlog.rowb.app

Registry code: 61f545bff39f446b

api record

A fishing catch logbook: record catches with date, location, species and conditions via MCP.

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

endpoint
https://catchlog.rowb.app/mcp
door code
8ef7c6b68599880d
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 catchlog live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is catchlog 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 catchlog have?
3 tools: catch_summary, record_catch, list_entries.
Is catchlog 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
98.7%

90 days 98.8%· all time 98.5%

latency
639ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 911 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
lifestyle & home
used for
  • record a fishing catch
  • list logbook entries
  • summarize catches by species and place
takes → gives
text → data
tools
2 reads1 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 3 tools
1 auth-required 2 never probed 1 of 3 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_entries reads auth-required 19h ago

    List the entries stored in your own logbook, newest first. Entries belonging to other users are never returned.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "limit": {
      "type": "number",
      "description": "max entries (default 20, max 100)"
    }
  }
}
    arguments 10 lines
  • catch_summary reads unknown never probed

    Count what is in your logbook: totals, longest and heaviest, per species, per place and per month. Every number is counted from your entries; nothing is estimated.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • record_catch changes data unknown never probed

    Record one catch in your logbook: date, species, place, and optionally length, weight, method, weather and water temperature. Returns the stored entry, or the list of errors that prevented storing it.

    mcp-tool

    {
  "type": "object",
  "required": [
    "caught_on",
    "species",
    "place"
  ],
  "properties": {
    "notes": {
      "type": "string",
      "description": "free text (optional)"
    },
    "place": {
      "type": "string",
      "description": "where, e.g. \"north jetty\""
    },
    "method": {
      "type": "string",
      "description": "how it was caught (optional)"
    },
    "species": {
      "type": "string",
      "description": "what was caught, e.g. \"sea bass\""
    },
    "weather": {
      "type": "string",
      "description": "conditions (optional)"
    },
    "caught_on": {
      "type": "string",
      "description": "date of the catch, YYYY-MM-DD"
    },
    "length_cm": {
      "type": "number",
      "description": "length in cm (optional)"
    },
    "weight_kg": {
      "type": "number",
      "description": "weight in kg (optional)"
    },
    "water_temp_c": {
      "type": "number",
      "description": "water temperature in Celsius (optional)"
    }
  }
}
    arguments 46 lines
_ try it over mcp 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 61f545bff39f446b.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/61f545bff39f446b/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/61f545bff39f446b/badge.svg)](https://brick.blue/agent/61f545bff39f446b?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 knowoff the mcp door
card completeness
70%

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 rowb.app 19 entries

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.

11 more sit on this domain. All of them.