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

casa-rosanna

https://casarosannaottiolu.it

Registry code: fa0cb015d8903ab3

api record

Strumenti in sola lettura per Casa Rosanna, casa vacanze a Porto Ottiolu (Sardegna): disponibilità, prezzi indicativi, spiagge riparate oggi, dati della casa. Le prenotazioni si chiudono su WhatsApp con i proprietari: non esiste pagamento online.

endpoint
https://casarosannaottiolu.it/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 casa-rosanna live?
Yes — it answered the hub's last check (checked 24h ago). It answered 100% of checks over the last 30 days.
Is casa-rosanna free to use?
Yes — the hub reached it with no key and no payment.
What tools does casa-rosanna have?
4 tools: check_availability, house_info, beach_today, list_weeks.
Is casa-rosanna 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
300ms

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
1 open 3 never probed 1 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_weeks open 24h ago

    List upcoming Saturday-to-Saturday weeks at Casa Rosanna with availability and indicative direct price. / Elenco delle prossime settimane sabato-sabato con disponibilità e prezzo.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • check_availability unknown 24h ago

    Check if Casa Rosanna (holiday home in Porto Ottiolu, Sardinia, up to 5 guests) is free for the given dates and get the indicative direct-booking price. / Verifica disponibilità e prezzo indicativo di Casa Rosanna per le date indicate.

    mcp-tool

    {
  "type": "object",
  "required": [
    "checkin",
    "checkout"
  ],
  "properties": {
    "checkin": {
      "type": "string",
      "description": "Arrival date, YYYY-MM-DD"
    },
    "checkout": {
      "type": "string",
      "description": "Departure date, YYYY-MM-DD"
    }
  }
}
    arguments 17 lines
  • house_info unknown never probed

    Key facts about Casa Rosanna: location, rooms, amenities, check-in times, pets, contacts. / Dati principali della casa.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • beach_today unknown never probed

    Which beaches near Porto Ottiolu, Budoni and San Teodoro (north-east Sardinia) are most sheltered today and in the next two days, from the forecast wind. / Spiagge più riparate oggi e nei prossimi due giorni.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 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 fa0cb015d8903ab3.

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