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

studiofromthesea-mcp

https://studiofromthesea.fr

Registry code: 07c0b5add062f88e

api record

Serveur MCP de Studio From The Sea : offres et couverture pour artisans du batiment en Bretagne.

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

endpoint
https://studiofromthesea.fr/mcp
door code
f11758c4536e3a3b
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 studiofromthesea-mcp live?
Yes — it answered the hub's last check (checked 9h ago). It answered 94% of checks over the last 30 days.
Is studiofromthesea-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does studiofromthesea-mcp have?
3 tools: get_recent_pages, get_offers, list_coverage.
Is studiofromthesea-mcp 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
94.4%

90 days 98%· all time 98.4%

latency
106ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 405 checks · signed record
  • down → live
  • degraded → live
  • live → degraded· fetch failed
  • degraded → down· fetch failed
  • live → degraded· fetch failed
_ what it is for
topic
productivity & business marketing & seo
used for
  • list website offers for building tradespeople
  • list covered towns
  • get recently added local pages
takes → gives
text → data
tools
3 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 3 tools
3 open 3 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.

  • get_recent_pages reads open 22d ago

    Retourne les communes ajoutées le plus récemment à la couverture (nom du métier, date d'ajout, liste des communes réelles).

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_offers reads open 22d ago

    Retourne les 3 offres tarifaires fixes de Studio From The Sea (prix, ce qui est inclus, pour qui), sans abonnement obligatoire.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • list_coverage reads open 22d ago

    Retourne la zone géographique couverte et le nombre de communes avec une page dédiée par métier (électricien, plombier, couvreur, maçon, menuisier, peintre, plâtrier).

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 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 07c0b5add062f88e.

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