# À proximité (remote · aproximite.ca)

A company that comes to your home in Vaudreuil-Soulanges. No company can pay for its place.

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `aproximite.ca`: 72/100 (this document), [markdown](https://verifymcp.io/servers/ca-aproximite-aproximite/aproximite.md), [page](https://verifymcp.io/servers/ca-aproximite-aproximite/aproximite)

## Channel facts

- Endpoint: `https://aproximite.ca/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http ca-aproximite-aproximite 'https://aproximite.ca/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ca-aproximite-aproximite": {
      "url": "https://aproximite.ca/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ca-aproximite-aproximite": {
      "type": "http",
      "url": "https://aproximite.ca/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ca-aproximite-aproximite]
url = "https://aproximite.ca/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ca-aproximite-aproximite": {
      "type": "remote",
      "url": "https://aproximite.ca/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ca-aproximite-aproximite --url 'https://aproximite.ca/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ca-aproximite-aproximite:
    url: "https://aproximite.ca/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ca-aproximite-aproximite": {
      "Transport": "http",
      "Url": "https://aproximite.ca/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ca-aproximite-aproximite -t streamable-http -u 'https://aproximite.ca/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ca-aproximite-aproximite": {
      "type": "http",
      "url": "https://aproximite.ca/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-19 (score 72, +1)

- [functional] Server version: 1.0.0 → 1.0.2
- [cosmetic] “prepare_referral_request” reworded the description of “urgency”

### 2026-11-18 (score 71, +2)

- [functional regression] Schema quality: 389 → 432
- [functional improvement] Tool coverage: 60% → 100%
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: good → excellent
- [cosmetic] “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”

### 2026-11-17 (score 69)

First indexed and scored.

## MCP tools (4)

### `get_referral_options` (~226 tokens)

À proximité: services and areas

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.

Input parameters:

- `locale` (string): The customer's language: fr for French, en for English. Use it for the review and the text messages they receive.

### `lookup_service_address` (~174 tokens)

Look up a service address

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.

Input parameters:

- `locale` (string, required): 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.

### `prepare_referral_request` (~951 tokens)

Prepare a request for review

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.

Input parameters:

- `addressLine1` (string, required): 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, required): 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, required): Customer-stated property location, required on every preparation. Ask the customer if unknown.
- `name` (string, required): The customer's name, as they gave it. The company uses it when calling back.
- `phone` (string, required): 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…

### `submit_referral_request` (~125 tokens)

Send the reviewed request

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.

Input parameters:

- `customerAuthorized` (boolean, required): true, only after the customer has seen the review and said yes to sending it.
- `privacyVersion` (string, required): The consent.privacyVersion from that same review, unchanged.
- `reviewToken` (string, required): The reviewToken from prepare_referral_request's ready review, unchanged.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ca-aproximite-aproximite/aproximite#diagnostics

## Score history

- 2026-11-21: 72
- 2026-11-20: 72
- 2026-11-19: 72
- 2026-11-18: 71
- 2026-11-17: 69

## Common questions

### 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.

## Links

- Remote endpoint: https://aproximite.ca/mcp
- Website: https://aproximite.ca/
- Changelog RSS feed: https://verifymcp.io/servers/ca-aproximite-aproximite/aproximite.xml
- Changelog JSON feed: https://verifymcp.io/servers/ca-aproximite-aproximite/aproximite/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ca-aproximite-aproximite/aproximite.json
- HTML version of this page: https://verifymcp.io/servers/ca-aproximite-aproximite/aproximite
