vakmanindebuurt
Registry code: 71acc1721a3af254
Zoek een vakman in België met search_service_or_craftsman en vraag daarna met submit_lead_quote een gratis offerte aan. Vraag de gebruiker altijd zelf om zijn gegevens en toestemming; verzin niets.
- endpoint
- https://vakmanindebuurt.be/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 vakmanindebuurt live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is vakmanindebuurt free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does vakmanindebuurt have?
- 2 tools: submit_lead_quote, search_service_or_craftsman.
- Is vakmanindebuurt 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 2 tools
- unknown → 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
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
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.
submit_lead_quote unknown never probed
Submit a free quote request for a job in Belgium. The request is sent to the chosen craftsman (craftsman_id from search_service_or_craftsman) or, without one, kept as a regional request. ONLY call this after the user has explicitly given every field below themselves and agreed that their contact details are passed to the craftsman; never invent, guess or reuse details from elsewhere. Set consent_contact and consent_text_shown to true only if that is the case. Validation errors are returned per field so you can ask the user again.
{ "type": "object", "required": [ "postcode", "job_description", "first_name", "last_name", "email", "phone", "desired_start", "consent_contact", "consent_text_shown" ], "properties": { "city": { "type": "string", "maxLength": 80, "description": "Optioneel: gemeente van de klus." }, "email": { "type": "string", "format": "email" }, "phone": { "type": "string", "description": "Belgisch gsm- of vast nummer, bv. 0475 12 34 56." }, "service": { "type": "string", "maxLength": 100, "description": "Alternatief voor expertise_id: de dienst als tekst." }, "postcode": { "type": "string", "pattern": "^[1-9][0-9]{3}$" }, "last_name": { "type": "string", "maxLength": 80, "minLength": 2 }, "first_name": { "type": "string", "maxLength": 60, "minLength": 2 }, "craftsman_id": { "type": "integer", "description": "Optioneel: de gekozen vakman uit de zoekresultaten." }, "expertise_id": { "type": "integer", "description": "Uit search_service_or_craftsman (matched_service.expertise_id)." }, "desired_start": { "enum": [ "asap", "within_2_weeks", "within_1_month", "within_3_months", "flexible" ], "type": "string" }, "street_address": { "type": "string", "maxLength": 120, "description": "Optioneel: straat en huisnummer." }, "consent_contact": { "type": "boolean", "description": "De gebruiker gaat ermee akkoord dat zijn gegevens aan de gekozen vakman worden doorgegeven. Moet true zijn." }, "job_description": { "type": "string", "maxLength": 1500, "minLength": 20, "description": "Wat moet er gebeuren? Zonder links of e-mailadressen." }, "client_reference": { "type": "string", "maxLength": 80, "description": "Optioneel: eigen referentie om dubbele indiening te voorkomen." }, "consent_text_shown": { "type": "boolean", "description": "De gebruiker heeft gezien dat zijn gegevens worden doorgegeven en de privacyverklaring is aangeboden. Moet true zijn." } } }arguments 90 linessearch_service_or_craftsman unknown 1h ago
Search for craftsmen (plumber, roofer, electrician, solar panels, ...) in Belgium by service and postcode on vakmanindebuurt.be. Returns the matched service, the municipality and up to 10 public craftsman profiles (no contact details). Use the returned expertise_id (and optionally a craftsman_id) in submit_lead_quote. Read-only.
{ "type": "object", "required": [ "service", "postcode" ], "properties": { "limit": { "type": "integer", "default": 5, "maximum": 10, "minimum": 1 }, "service": { "type": "string", "maxLength": 100, "minLength": 2, "description": "Wat de gebruiker zoekt, bv. \"loodgieter\", \"zonnepanelen\", \"dak herstellen\"." }, "postcode": { "type": "string", "pattern": "^[1-9][0-9]{3}$", "description": "Belgische postcode van 4 cijfers waar de klus is." } } }arguments 26 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 id71acc1721a3af254.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/71acc1721a3af254/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/71acc1721a3af254?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.