Vakman in de Buurt
REMOTE · VAKMANINDEBUURT.BE
Zoek vakmannen in België en vraag gratis offertes aan via vakmanindebuurt.be.
Available components
Last scanned (18 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 4 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability57
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 554 tokens (~277/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.27 ▲ functional
- 2 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 27 Oct 26 67
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://vakmanindebuurt.be/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vakmanindebuurt.be | CN=YR2,O=Let's Encrypt,C=US | 30 Sept 2026 | 29 Dec 2026 | RSA 4096 | SHA256-RSA | 5f83a73346bd18d58b8f740a4511e3f88ac |
| SANs: vakmanindebuurt.be, vakmanindebuurtbe.webhosting.be, www.vakmanindebuurt.be | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of vakmanindebuurt.be. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| be. | present | 45588 | 13 | Verified |
| vakmanindebuurt.be. | present | 29436 | 13 | Verified |
| vakmanindebuurt.be. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vakmanindebuurt.be/mcp | Verified | 200 | |
| http (plaintext) | http://vakmanindebuurt.be/mcp | HTTPS enforced | 301 | https://vakmanindebuurt.be/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
search_service_or_craftsman Zoek vakman of dienst in België ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| postcode | string | yes | Belgische postcode van 4 cijfers waar de klus is. |
| service | string | yes | Wat de gebruiker zoekt, bv. "loodgieter", "zonnepanelen", "dak herstellen". |
No output schema declared.
No examples provided.
submit_lead_quote Vraag een offerte aan bij een vakman ~374
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Optioneel: gemeente van de klus. |
| client_reference | string | – | Optioneel: eigen referentie om dubbele indiening te voorkomen. |
| consent_contact | boolean | yes | De gebruiker gaat ermee akkoord dat zijn gegevens aan de gekozen vakman worden doorgegeven. Moet true zijn. |
| consent_text_shown | boolean | yes | De gebruiker heeft gezien dat zijn gegevens worden doorgegeven en de privacyverklaring is aangeboden. Moet true zijn. |
| craftsman_id | integer | – | Optioneel: de gekozen vakman uit de zoekresultaten. |
| desired_start | string | yes | – |
| string | yes | – | |
| expertise_id | integer | – | Uit search_service_or_craftsman (matched_service.expertise_id). |
| first_name | string | yes | – |
| job_description | string | yes | Wat moet er gebeuren? Zonder links of e-mailadressen. |
| last_name | string | yes | – |
| phone | string | yes | Belgisch gsm- of vast nummer, bv. 0475 12 34 56. |
| postcode | string | yes | – |
| service | string | – | Alternatief voor expertise_id: de dienst als tekst. |
| street_address | string | – | Optioneel: straat en huisnummer. |
No output schema declared.
No examples provided.
How do I install the Vakman in de Buurt MCP server?
Vakman in de Buurt is a hosted endpoint at https://vakmanindebuurt.be/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · vakmanindebuurt.be
claude mcp add --transport http be-vakmanindebuurt-leads 'https://vakmanindebuurt.be/mcp'
What is the Vakman in de Buurt MCP server?
Vakman in de Buurt is an MCP server listed in the public MCP registry as be.vakmanindebuurt/leads. Zoek vakmannen in België en vraag gratis offertes aan via vakmanindebuurt.be. This page covers its hosted endpoint (https://vakmanindebuurt.be/mcp).
Is the Vakman in de Buurt MCP server safe to use?
Vakman in de Buurt scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Vakman in de Buurt MCP server expose?
Vakman in de Buurt exposes 2 tools: search_service_or_craftsman, submit_lead_quote. Their descriptions and schemas cost roughly 510 tokens of context every time the server is loaded.
Does the Vakman in de Buurt MCP server require authentication?
No. We connected to Vakman in de Buurt without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Vakman in de Buurt MCP server still maintained?
Vakman in de Buurt is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.