À proximité
REMOTE · APROXIMITE.CA
A company that comes to your home in Vaudreuil-Soulanges. No company can pay for its place.
Available components
Last scanned (17 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 21 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 Security80
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1729 tokens (~432/item across 4 items; 4 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 +1
- Server version: 1.0.0 → 1.0.2 functional
- “prepare_referral_request” reworded the description of “urgency” cosmetic
- 18 Nov 26 +2
- Schema quality: 389 → 432 ▼ functional
- Tool coverage: 60% → 100% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
- “lookup_service_address” reworded the description of “locale” cosmetic
- “lookup_service_address” reworded the description of “session” cosmetic
- “prepare_referral_request” reworded the description of “addressUnit” cosmetic
- “prepare_referral_request” reworded the description of “name” cosmetic
- “prepare_referral_request” reworded the description of “phone” cosmetic
- “prepare_referral_request” reworded the description of “postalCode” cosmetic
- “prepare_referral_request” reworded the description of “service” cosmetic
- “submit_referral_request” reworded the description of “customerAuthorized” cosmetic
- “submit_referral_request” reworded the description of “privacyVersion” cosmetic
- “submit_referral_request” reworded the description of “reviewToken” cosmetic
- 17 Nov 26 69
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 21 Nov 2026 · Probed https://aproximite.ca/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=aproximite.ca | CN=YR1,O=Let's Encrypt,C=US | 6 Oct 2026 | 4 Jan 2027 | RSA 2048 | SHA256-RSA | 5ff7e7d1bf220339e85359829886ba52027 |
| SANs: aproximite.ca | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 insecure
Validation of aproximite.ca. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ca. | DS published | 26384 | 13 | Verified |
| aproximite.ca. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://aproximite.ca/mcp | Verified | 200 | |
| http (plaintext) | http://aproximite.ca/mcp | HTTPS enforced | 308 | https://aproximite.ca/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 →
get_referral_options À proximité: services and areas ~226
Find out how to connect a homeowner with a local company chosen on merit for work in and around their home (an electrician, a plumber, a heating and cooling company, an exterminator, a cleaning company, a painter, a roofer, a moving company, a landscaper, a snow removal company, a window washer, a gutter company, a tree service, a general contractor, a handyman, a fence and deck builder, an appliance repair company, a window and door company, a pool company or a chimney sweep) through À proximité in Vaudreuil-Soulanges, Quebec. You can collect the job and contact details, prepare a request, show the customer a review and submit with their explicit permission. When a suitable professional accepts, they contact the customer directly. Read services, municipalities, availability and the workflow. No booking or callback-time guarantee. This tool only reads public information. Call this first.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | The customer's language: fr for French, en for English. Use it for the review and the text messages they receive. |
No output schema declared.
No examples provided.
lookup_service_address Look up a service address ~174
Return up to five labeled address suggestions or resolve one opaque selection. Read-only: this never changes a request or records consent. Query and selection are mutually exclusive. Suggestions are candidates only; never guess or auto-select. Manual entry is always available. If Google output is shown to the customer, include the exact attribution text Google Maps.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | yes | The customer's language: fr for French, en for English. Suggestions come back in it. |
| query | string | – | What the customer typed. Pass query or selection, not both. |
| selection | string | – | The suggestion the customer picked. Pass query or selection, not both. |
| session | string | – | The session returned by your previous lookup with a query, to keep the same search as the customer types more. Leave it out on the first query. |
No output schema declared.
No examples provided.
prepare_referral_request Prepare a request for review ~951
Validate the customer's details and return the exact request and consent notice to show them, with a review token. Nothing is sent. Work from two or more trades goes in services, one entry per trade with only that trade's part of the description, in this one call: never one description for several trades. Pass the situation, since and answers from the customer's words and get_referral_options' situations. Municipality must be the customer's stated job location; ask if unknown. Call again with corrected details if fieldsToCorrect is not empty. Photos are not supported here; the customer can add them on aproximite.ca.
| Name | Type | Req | Description |
|---|---|---|---|
| addressLine1 | string | yes | Customer-stated street address for this job. Required for a ready review. Manual entry is valid; never guess from a suggestion. |
| addressUnit | string | – | Apartment, unit or suite number, if the customer gave one. |
| answers | object | – | Answers to the situation's questions, question id to choice id, from what the customer said. Only that situation's questions and choices; leave out a question they can't answer. Later answers add to… |
| company | string | – | Only when the customer came from a company's page on this site (/fr/entreprises/{company} or /companies/{company}): that page's last path segment. The request goes to that company first when it can t… |
| description | string | – | The job as the customer would tell the company, in the first person and in their words, keeping every detail they gave about it (age, model, where, what happens). Only one trade's work: another trade… |
| locale | string | yes | The customer's language: fr for French, en for English. Use it for the review and the text messages they receive. |
| mode | string | – | one_company (default): one local company calls the customer. quotes: several local companies call about the same request so the customer can compare quotes and choose. Use quotes only when the custom… |
| municipality | string | yes | Customer-stated property location, required on every preparation. Ask the customer if unknown. |
| name | string | yes | The customer's name, as they gave it. The company uses it when calling back. |
| phone | string | yes | The customer's phone number, where the company calls back and where the confirmation text goes. A Canadian number, as they gave it. |
| postalCode | string | – | The job address's postal code, if the customer gave it. |
| sameCompanyAsLastTime | boolean | – | true only when the customer says they want the same company as for a previous job ("the same electrician as last time"). Never ask about it. |
| service | string | – | The trade for this job, from get_referral_options' services. When a situation is given, the service follows it. |
| services | array | – | ONLY when the customer describes work for two or more trades (for example after moving in: an electrical panel, painting and a cleaning): one entry per trade, never two for the same trade. Each entry… |
| since | string | – | Since when the problem has been going on: today, days (a few days), week_plus (more than a week) or unknown. Only for a problem situation, never for an installation. |
| situation | string | – | The situation from get_referral_options' situations that matches the job, confirmed with the customer. The service then follows the situation. An empty string removes it. |
| urgency | string | – | Urgent only when the customer says it is urgent or an emergency, as the website's Urgent choice. Everything else is flexible (default), including wanting it today, tomorrow, soon or fast. Never ask a… |
No output schema declared.
No examples provided.
submit_referral_request Send the reviewed request ~125
Send the request exactly as reviewed. CONSEQUENTIAL: call only after showing the customer the review from prepare_referral_request and getting their explicit permission. Pass that review token and privacy version with customerAuthorized:true. Repeating the same token never creates a second request.
| Name | Type | Req | Description |
|---|---|---|---|
| customerAuthorized | boolean | yes | true, only after the customer has seen the review and said yes to sending it. |
| privacyVersion | string | yes | The consent.privacyVersion from that same review, unchanged. |
| reviewToken | string | yes | The reviewToken from prepare_referral_request's ready review, unchanged. |
No output schema declared.
No examples provided.
How do I install the À proximité MCP server?
À proximité is a hosted endpoint at https://aproximite.ca/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 · aproximite.ca
claude mcp add --transport http ca-aproximite-aproximite 'https://aproximite.ca/mcp'
What is the À proximité MCP server?
À proximité is an MCP server listed in the public MCP registry as ca.aproximite/aproximite. A company that comes to your home in Vaudreuil-Soulanges. No company can pay for its place. This page covers its hosted endpoint (https://aproximite.ca/mcp).
Is the À proximité MCP server safe to use?
À proximité scores 72 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 À proximité MCP server expose?
À proximité exposes 4 tools: get_referral_options, lookup_service_address, prepare_referral_request, submit_referral_request. Their descriptions and schemas cost roughly 1,476 tokens of context every time the server is loaded.
Does the À proximité MCP server require authentication?
No. We connected to À proximité without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the À proximité MCP server still maintained?
À proximité is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the À proximité MCP server?
VerifyMCP ran 13 checks on À proximité, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.