fr.fixou/fixou
REMOTE · MCP.FIXOU.FR
Create and track quote requests to local French tradespeople (80 trades) on fixou.fr.
Available components
Last scanned (16 hours ago)
Scores higher than 79% 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 627 tokens (~209/item across 3 items; 3 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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 (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
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.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://mcp.fixou.fr/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fixou.fr | CN=WE1,O=Google Trust Services,C=US | 12 Nov 2026 | 10 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 3a84ff55d808368613ca1e1ccb4381a0 |
| SANs: fixou.fr, *.fixou.fr | ||||||
| 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 mcp.fixou.fr. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| fr. | DS published | 65381 | 13 | Verified |
| fixou.fr. | 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=31536000 |
| content-security-policy | default-src 'self'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; object-src 'none'; script-src 'self' 'unsafe-inline' https://challenges.cloudflare.com https://static.cloudflareinsights.com https://www.googletagmanager.com; script-src-attr 'none'; style-src 'self' 'unsafe-inline'; font-src 'self' data:; img-src 'self' data: blob: https://*.google-analytics.com https://*.googletagmanager.com; media-src 'self' blob:; connect-src 'self' https://eu.i.posthog.com https://eu-assets.i.posthog.com https://*.sentry.io https://challenges.cloudflare.com https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com; frame-src https://challenges.cloudflare.com; worker-src 'self' blob:; manifest-src 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.fixou.fr/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.fixou.fr/mcp | HTTPS enforced | 301 | https://mcp.fixou.fr/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 →
create_request ~371
Cree une demande de devis Fixou au nom du client final. IMPORTANT : la demande n'est PAS publiee immediatement — elle attend une confirmation par email (double opt-in). L'email est celui du CLIENT FINAL (pas de l'agent) et est obligatoire : le client recevra un email « Confirmez votre demande » avec un lien valable 48 heures ; tant qu'il n'a pas clique, aucun artisan n'est contacte. Apres cet appel, invitez explicitement l'utilisateur a ouvrir sa boite mail et a cliquer sur ce lien de confirmation pour publier sa demande et suivre les reponses sur fixou.fr ; l'agent lui-meme n'a jamais acces a cet espace. La description doit faire au moins 20 caracteres. `answers` reprend les `id` de questions et les `value` d'options du metier (voir list_categories). Renvoie le `requestId` a utiliser avec get_request.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | yes | Reponses au questionnaire du metier, indexees par `id` de question. Valeur unique (question single) ou tableau de valeurs (question multi), choisies parmi les `value` des options. |
| categorySlug | string | yes | Slug du metier concerne, obtenu via list_categories. |
| description | string | yes | Description libre du besoin, en francais, de 20 a 5000 caracteres. |
| string | yes | Email du client final (obligatoire) ; il y recevra le lien de confirmation a cliquer pour publier sa demande, puis le suivi. | |
| phone | string | – | Telephone du client final (optionnel), transmis aux artisans qu'il choisira. |
| postalCode | string | yes | Code postal francais du lieu d'intervention (5 chiffres). |
No output schema declared.
No examples provided.
get_request ~112
Consulte le statut d'une demande Fixou et les reponses des artisans (nom de l'entreprise, message, prix indicatif, delai, note moyenne). Ne renvoie jamais de coordonnees : celles-ci ne sont communiquees qu'au client final, une fois qu'il a choisi un artisan sur fixou.fr. Une cle API ne peut consulter que les demandes qu'elle a elle-meme creees.
| Name | Type | Req | Description |
|---|---|---|---|
| requestId | string | yes | Identifiant de la demande, renvoye par create_request. |
No output schema declared.
No examples provided.
list_categories ~101
Liste tous les metiers proposes par Fixou, regroupes par famille, avec le questionnaire propre a chaque metier. A appeler avant create_request : le `slug` d'un metier devient le `categorySlug`, et le questionnaire indique les questions a couvrir. Dans create_request, l'objet `answers` doit utiliser les `id` de question comme cles et, comme valeurs, les `value` des options proposees (jamais les libelles).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the fr.fixou/fixou MCP server?
fr.fixou/fixou is a hosted endpoint at https://mcp.fixou.fr/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 · mcp.fixou.fr
claude mcp add --transport http fr-fixou-fixou 'https://mcp.fixou.fr/mcp'
What is the fr.fixou/fixou MCP server?
fr.fixou/fixou is an MCP server listed in the public MCP registry as fr.fixou/fixou. Create and track quote requests to local French tradespeople (80 trades) on fixou.fr. This page covers its hosted endpoint (https://mcp.fixou.fr/mcp).
Is the fr.fixou/fixou MCP server safe to use?
fr.fixou/fixou scores 81 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 fr.fixou/fixou MCP server expose?
fr.fixou/fixou exposes 3 tools: list_categories, create_request, get_request. Their descriptions and schemas cost roughly 584 tokens of context every time the server is loaded.
Does the fr.fixou/fixou MCP server require authentication?
No. We connected to fr.fixou/fixou without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the fr.fixou/fixou MCP server still maintained?
fr.fixou/fixou 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 fr.fixou/fixou MCP server?
VerifyMCP ran 12 checks on fr.fixou/fixou, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about fr.fixou/fixou: Authorization. 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.