Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Dispolà

REMOTE · DISPOLA.CA

Same-day appointment openings in Quebec: hair, nails, massage, physio. No account needed.

Available components

−1 this week 71 Trust /100

Last scanned (18 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Maps and Location

Recent critical change

Authorization (31 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability71
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3058 tokens (~382/item across 8 items; 7 tools + 1 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 Management33
  • Stability observed for 10 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
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
Changelog

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

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “chercher_places” rewrote its description, which is the text the model reads security
    • “chercher_places” added an optional parameter “clientele” cosmetic
    • “chercher_places” added an optional parameter “condition” cosmetic
  • 1 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • “chercher_places” reworded the description of “ville” cosmetic
  • 31 Oct 26 −6
    • Authorization: partial → fail ▼ critical
    • Tool “confirmer_code” rewrote its description, which is the text the model reads security
    • Tool “envoyer_code” rewrote its description, which is the text the model reads security
    • Tool “lien_alerte_texto” rewrote its description, which is the text the model reads security
    • Tool “preparer_demande” rewrote its description, which is the text the model reads security
    • Tool “proposer_limites” rewrote its description, which is the text the model reads security
    • Tool “confirmer_code” is now declared destructive security
    • Tool “envoyer_code” is now declared destructive security
    • Tool “proposer_limites” is now declared destructive security
    • “confirmer_code” reworded the description of “code” cosmetic
    • “proposer_limites” reworded the description of “accepter_seul” cosmetic
  • 30 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 301 → 341 ▼ functional
    • Server version: 1.1.0 → 1.2.0 functional
    • New tool “confirmer_code” functional
    • New tool “envoyer_code” functional
    • New tool “proposer_limites” functional
  • 29 Oct 26 +3
    • Schema quality: 365 → 301 ▲ functional
    • The server now declares the “resources” capability functional
    • First check of Capabilities: pass functional
    • First check of Schema quality: 100 functional
    • New resource “places” functional
    • Server version: 1.0.0 → 1.1.0 functional
  • 28 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 1019 → 1460 ▼ functional
    • New tool “preparer_demande” functional
  • 27 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.

Diagnostics

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://dispola.ca/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=dispola.ca CN=WE1,O=Google Trust Services,C=US 5 Oct 2026 3 Jan 2027 ECDSA 256 ECDSA-SHA256 89ac1045609984661376d709f9d51f00
SANs: dispola.ca, www.dispola.ca, *.www.dispola.ca
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of dispola.ca. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ca. present 26384 13 Verified
dispola.ca. absent 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=31536000; includeSubDomains
content-security-policy frame-ancestors 'none'; base-uri 'self'; object-src 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), payment=(), geolocation=(self), usb=(), serial=(), bluetooth=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://dispola.ca/mcp Verified 200
http (plaintext) http://dispola.ca/mcp HTTPS enforced 301 https://dispola.ca/mcp
MCP tools · 7 exposed · ~2,164 tokens

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 →

Tool Tokens
categories_et_villes ~60

Les villes, les catégories et leurs services, avec le nombre de places libres par ville et par catégorie d'ici 7 jours. / Cities, categories and services, with the number of open spots per city and category over the next 7 days.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

chercher_places ~551

Cherche les places libres d'une ville, par catégorie, jour, moment et quartier, et au besoin par condition de santé ou par clientèle (commerces Dispolà Pro qui l'ont cochée). Rend l'établissement, le quartier, le service, l'heure, la durée, le prix et le lien pour réserver. Avec une catégorie, rend aussi sur_demande : des commerces sans réservation en ligne, avec des moments estimés à confirmer. / Finds open appointment spots in a city, by category, day, time of day and neighbourhood, optionally by health condition or clientele, with the booking link. With a category, also returns sur_demande: businesses without online booking, with estimated times to be confirmed by phone.

NameTypeReqDescription
categoriestring–La catégorie (voir categories_et_villes). / The category.
clientelestring–Une clientèle (femmes_enceintes, enfants, aines, mobilite_reduite...) : seulement les commerces Dispolà Pro qui l'ont cochée. Sans sur_demande. / A clientele: only Dispolà Pro businesses that checked…
conditionstring–Une condition de santé (maux_de_dos, stress, commotion...) : seulement les commerces Dispolà Pro qui se disent à l'aise avec elle. Pas un diagnostic : ce que le ou la pro dit connaître. Sans sur_dema…
jourstring–aujourdhui, demain ou AAAA-MM-JJ (heure de Montréal). / today, tomorrow or YYYY-MM-DD.
latnumber–Latitude, avec lng : trie du plus proche au plus loin. / Latitude, with lng: sorts nearest first.
limiteinteger–Nombre de places, 10 par défaut. / Max spots, default 10.
lngnumber–Longitude, avec lat. / Longitude, with lat.
momentstring–am : avant midi ; pm : de midi à 17 h ; soir : après 17 h. / morning, afternoon, evening.
quartierstring–Un quartier, par exemple Plateau ou Limoilou : trie du plus proche au plus loin. / A neighbourhood: sorts nearest first.
villestringyesLa ville, ou ailleurs : ailleurs au Québec, hors des villes du site (Trois-Rivières, Granby, Saguenay...) ; donne alors la ville de la personne dans quartier, ou lat et lng. / The city, or ailleurs:…

No output schema declared.

No examples provided.

confirmer_code ~150

Vérifie le code à 6 chiffres que la personne a reçu par texto après envoyer_code ou proposer_limites. Avec le bon code, une demande part chez Dispolà, qui appelle le commerce, ou des limites deviennent actives et l'outil rend la clé mandat. Un mauvais code est refusé. / Checks the 6-digit code the person received by text. Sends the request, or activates their limits and returns the mandate key. A wrong code is rejected.

NameTypeReqDescription
codestringyesLes 6 chiffres reçus par la personne. / The 6 digits.
referencestringyesLa référence rendue par envoyer_code ou proposer_limites. / The reference returned earlier.

No output schema declared.

No examples provided.

envoyer_code ~359

Prépare la demande chez un commerce sur demande et texte à la personne un code à 6 chiffres, avec le texte exact de son accord. La personne lit ce code, et confirmer_code envoie la demande. Le prénom et le cellulaire sont ceux de la personne, pour elle-même. Avec mandat (la clé de confirmer_code après proposer_limites) et accepter_seul, une demande qui respecte toutes ses limites part sans code. / Prepares the request and texts the person a 6-digit code with the exact consent wording; confirmer_code sends it with that code. With a mandate key and auto-accept, a request within all their signed limits is sent without a code.

NameTypeReqDescription
cellulairestring–Son cellulaire, Canada ou États-Unis. / Their mobile number.
commercestringyesLe code du commerce (champ commerce de sur_demande). / Business code.
heuresstringyesAu moins 2 heures de moments, séparées par des virgules, qui vont toutes à la personne. / At least 2 times from moments, comma-separated.
languestring–Langue des textos. / Text language.
latnumber–Latitude, avec lng. / Latitude.
lieustring–Où est la personne : code postal ou quartier. / Postal code or neighbourhood.
lngnumber–Longitude, avec lat. / Longitude.
mandatstring–La clé mandat rendue par confirmer_code après proposer_limites. / Mandate key.
prenomstring–Le prénom de la personne. / Their first name.
servicestringyesLe service précis (champ services de sur_demande). / Precise service code.

No output schema declared.

No examples provided.

lien_alerte_texto ~221

Construit le lien du formulaire prérempli d'alerte texto quand aucune place ne convient. La personne l'ouvre, entre elle-même son cellulaire et consent aux textos ; l'outil ne soumet rien. / Builds a prefilled text alert form link; the person enters their own number and consents. The tool submits nothing.

NameTypeReqDescription
jourstring–aujourdhui, demain ou AAAA-MM-JJ (heure de Montréal). / today, tomorrow or YYYY-MM-DD.
languestring–Langue du formulaire. / Form language.
momentstring–am : avant midi ; pm : de midi à 17 h ; soir : après 17 h. / morning, afternoon, evening.
quartierstring–Le quartier de la personne. / Their neighbourhood.
servicestring–Le code du service, par exemple ongles.gel (voir categories_et_villes). / Service code.
villestringyesLa ville. / The city.

No output schema declared.

No examples provided.

preparer_demande ~378

Bâtit le lien de la demande chez un commerce sans réservation en ligne (sur_demande de chercher_places), avec les heures, le service et le lieu de la personne déjà choisis. La personne l'ouvre, vérifie, entre elle-même son prénom et son cellulaire et consent ; Dispolà appelle le commerce et lui texte l'heure confirmée. L'outil ne soumet rien. / Builds the prefilled request link for a business without online booking, with the person's times, service and location filled in. The person opens it, enters their own name and number and consents; Dispolà calls the business. The tool submits nothing.

NameTypeReqDescription
commercestringyesLe code du commerce (champ commerce de sur_demande). / Business code (commerce field of sur_demande).
heuresstring–Les heures qui vont à la personne, prises dans moments de sur_demande, séparées par des virgules : au moins 2, en cas que la première soit prise. Ex. 2026-10-29T14:00,2026-10-29T15:00. / Times from s…
languestring–Langue du formulaire. / Form language.
latnumber–Latitude de la personne, avec lng (arrondie à 100 m). / Latitude, with lng.
lieustring–Où est la personne : code postal ou quartier, pour un commerce de rechange proche d’elle. / Postal code or neighbourhood.
lngnumber–Longitude, avec lat. / Longitude, with lat.
servicestring–Le service précis (champ services de sur_demande, ex. coupe-courts). / Precise service code.

No output schema declared.

No examples provided.

proposer_limites ~445

Propose les limites dans lesquelles un agent peut demander pour la personne (le mandat ouvert d'AP2) : catégorie, services, jours (au plus 14), heures, lieu et rayon, prix max, et envoi sans code ou non. Dispolà les lui texte mot pour mot avec un code ; confirmer_code, avec ce code, rend la clé mandat. La personne peut tout annuler en textant STOP AGENT. / Proposes limits within which an agent may request on the person's behalf, texted to them word for word and signed with a text code.

NameTypeReqDescription
accepter_seulstring–oui : une demande qui respecte tout part sans code. non : un code à chaque demande. / Auto-accept.
apresstring–Pas avant cette heure, HH:MM. / Not before.
austring–Dernier jour, au plus 14 jours d'ici. Les limites expirent ce soir-là. / Last day; limits expire that night.
avantstring–Pas après cette heure, HH:MM. / Not after.
categoriestringyesLa catégorie. / The category.
cellulairestringyesSon cellulaire. / Their mobile number.
dustring–Premier jour, AAAA-MM-JJ. Demain par défaut. / First day.
languestring–Langue des textos. / Text language.
lieustring–Code postal ou quartier de la personne. / Postal code or neighbourhood.
prenomstringyesLe prénom de la personne. / Their first name.
prix_maxinteger–Prix max en dollars. Inconnu d’avance chez un commerce sur demande : Léon le vérifie au téléphone. / Max price.
rayon_kmnumber–Distance max du lieu, 3 km par défaut. / Max distance.
servicesstring–Les services permis (codes de services de sur_demande), séparés par des virgules. Sans : toute la catégorie. / Allowed service codes.
villestringyesLa ville. / The city.

No output schema declared.

No examples provided.

Install

How do I install the Dispolà MCP server?

Dispolà is a hosted endpoint at https://dispola.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 · dispola.ca

# add to Claude Code
claude mcp add --transport http ca-dispola-places 'https://dispola.ca/mcp'
Common questions

What is the Dispolà MCP server?

Dispolà is an MCP server listed in the public MCP registry as ca.dispola/places. Same-day appointment openings in Quebec: hair, nails, massage, physio. No account needed. This page covers its hosted endpoint (https://dispola.ca/mcp).

Is the Dispolà MCP server safe to use?

Dispolà scores 71 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 Dispolà MCP server expose?

Dispolà exposes 7 tools: chercher_places, categories_et_villes, lien_alerte_texto, preparer_demande, envoyer_code, and 2 more. Their descriptions and schemas cost roughly 2,164 tokens of context every time the server is loaded.

Does the Dispolà MCP server require authentication?

No. We connected to Dispolà without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Dispolà MCP server still maintained?

Dispolà 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.