toolzy
Registry code: 09c187b312403724
Recherche et location d'outils entre particuliers en France via Toolzy.
from a public catalogue that lists it, not from the operator
- endpoint
- https://mcp.toolzy.io/api/mcp
- protocol
- http-sse ·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 toolzy live?
- Yes — it answered the hub's last check (checked 28m ago). It answered 100% of checks over the last 30 days.
- Is toolzy free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does toolzy have?
- 3 tools: check_availability, get_tool_details, search_tools.
- Is toolzy 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.
90 days 100%· all time 100%
last good check
of 3 tools
- degraded → live
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.
through this hub
successful
what callers paid
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.
search_tools open 28m ago
Recherche d'outils et équipements disponibles à la location sur Toolzy. Utilisez ce tool quand l'utilisateur cherche un outil, veut louer du matériel, ou demande ce qui est disponible près de chez lui (ex: 'perceuse à Bordeaux', 'tondeuse à gazon', 'outils de bricolage'). La recherche couvre la commune demandée PUIS les communes voisines dans un rayon de 15 km : chaque résultat porte `is_local` et `distance_km`, et `search_area` donne la répartition. Indiquez toujours à l'utilisateur ce qui est dans sa ville et ce qui est à côté, avec la distance.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "city": { "type": "string", "description": "Ville de recherche. Les communes voisines sont incluses automatiquement." }, "limit": { "type": "integer", "maximum": 20, "minimum": 1, "description": "Nombre max de résultats (défaut: 10, max: 20)" }, "query": { "type": "string", "description": "Recherche textuelle (nom d'outil, marque, type)" }, "country": { "enum": [ "france", "belgique" ], "type": "string", "description": "Marché à interroger, pour lever une ambiguïté de commune homonyme (ex: Bruges)." }, "zipcode": { "type": "string", "description": "Code postal (filtre par préfixe)" }, "category": { "type": "string", "description": "Catégorie d'outils" }, "coaching": { "type": "boolean", "description": "Filtrer sur accompagnement disponible" }, "delivery": { "type": "boolean", "description": "Filtrer sur livraison disponible" }, "price_max": { "type": "number", "description": "Prix maximum par jour en euros" }, "radius_km": { "type": "number", "maximum": 100, "minimum": 1, "description": "Rayon autour de la ville en km (défaut: 15). N'élargissez que si l'utilisateur accepte de se déplacer plus loin." } }, "additionalProperties": false }arguments 55 linescheck_availability unknown 28m ago
Vérifie si un outil est disponible pour des dates données et calcule le prix total. Utilisez ce tool quand l'utilisateur demande la disponibilité, veut savoir le prix pour une période, ou demande 'est-ce disponible ce weekend ?'.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "tool_url", "start_date", "end_date" ], "properties": { "end_date": { "type": "string", "description": "Date de fin (YYYY-MM-DD)" }, "tool_url": { "type": "string", "description": "URL de l'annonce Toolzy (ex: https://www.toolzy.io/listings/perceuse-makita)" }, "start_date": { "type": "string", "description": "Date de début (YYYY-MM-DD)" } }, "additionalProperties": false }arguments 24 linesget_tool_details unknown 28m ago
Récupère les informations détaillées d'un outil sur Toolzy : prix, caractéristiques, photos. Utilisez ce tool quand l'utilisateur veut en savoir plus sur un outil spécifique après avoir vu les résultats de recherche. Renvoie aussi `similar_tools` : des alternatives de la même catégorie dans un rayon de 20 km avec leur distance — à proposer si l'outil est jugé trop cher ou trop loin.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "tool_url" ], "properties": { "tool_url": { "type": "string", "description": "URL de l'annonce Toolzy (ex: https://www.toolzy.io/listings/perceuse-makita)" } }, "additionalProperties": false }arguments 14 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id09c187b312403724.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/09c187b312403724/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/09c187b312403724?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.
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.