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

got-cosy-graph

https://gotcosy.com

Registry code: 96bfae9c9fc363cb

api record

6,300 independent hotels scored for cosiness from guest reviews, with verified booking links.

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

endpoint
https://gotcosy.com/api/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 got-cosy-graph live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is got-cosy-graph free to use?
Yes — the hub reached it with no key and no payment.
What tools does got-cosy-graph have?
2 tools: get_hotel_feeling, find_cosy_hotels.
Is got-cosy-graph 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 98.9%· all time 98.9%

latency
250ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 279 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
maps travel & places travel & transport
used for
  • find cosy hotels in a city
  • get a hotel's cosiness score
takes → gives
text → data
tools
2 reads
_ 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 2 tools
1 open 1 never probed 1 of 2 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.

  • find_cosy_hotels reads open 16h ago

    Find live, cosy-scored hotels from Got Cosy's cosiness index (gotcosy.com): hotels scored 0-10 for warmth, intimacy and character from photos and reviews. Only returns hotels that clear the public floor (score 5.0+). Optionally filter by city, country and a minimum cosy score.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "city": {
      "type": "string",
      "description": "City name, e.g. \"Paris\""
    },
    "limit": {
      "type": "number",
      "description": "Max results (default 20, max 100)"
    },
    "country": {
      "type": "string",
      "description": "Country name, e.g. \"France\""
    },
    "min_score": {
      "type": "number",
      "description": "Minimum cosy score 0-10 (the public floor is 5.0 regardless of this value)"
    }
  }
}
    arguments 21 lines
  • get_hotel_feeling reads unknown 16h ago

    Get one hotel's cosy score, evidence signals and description from Got Cosy, by its slug (as returned in find_cosy_hotels' results, or from a gotcosy.com/en/hotels/<slug> URL). Below-floor hotels return {below_bar:true} with no score exposed.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "The hotel's Got Cosy slug"
    }
  }
}
    arguments 12 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 96bfae9c9fc363cb.

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

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.