fixou MCP server
fr.fixou/fixoufixou.frstreamable-httpv1.0.0Scanned
Create and track quote requests to local French tradespeople (80 trades) on fixou.fr.
3 tools: 1 change things and 2 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the fixou MCP server can do
The fixou MCP server is published by fixou.fr, a domain the MCP Registry verified. It has 3 tools. It can create or change data (1 tool: create_request), but cannot delete data. 2 tools only read.
1 tool reads private data (get_request); 1 tool brings in text other people can write (get_request); 1 tool can send data out of your system (create_request). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 15, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 1Claude Code: ask
create_requestCree une demande de devis Fixou au nom du client final.Can send data outNo findings
Why it is in this group
- The name "create_request" says "create": a word for a change.
What it can reach
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
Description, as the server wrote it 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.
Only reads 2Show 2 read-only tools
get_requestConsulte le statut d'une demande Fixou et les reponses des artisans (nom de l'entreprise, message, prix indicatif, delai, note moyenne).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_request" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "message": it reads messages.
- untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
Description, as the server wrote it 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.
list_categoriesListe tous les metiers proposes par Fixou, regroupes par famille, avec le questionnaire propre a chaque metier.No findings
Why it is in this group
- The name "list_categories" says "list": a word for reading.
Description, as the server wrote it 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).
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
1 path in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__fixou__create_request"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:54 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.fixou.fr/mcp: tools/list returned 3 tools to an anonymous client, including create_request (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:create_requestChanges thingsinputSchema
- Changed:get_requestOnly readsinputSchema
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http fixou https://mcp.fixou.fr/mcpclaude mcp add --transport http fixou https://mcp.fixou.fr/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__fixou__list_categories",
"mcp__fixou__get_request"
],
"ask": [
"mcp__fixou__create_request"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as fixou. Review it before you use it.
Capability tags behind 2 rules
- mcp__fixou__create_request outbound
- mcp__fixou__get_request private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/fr.fixou/fixou/verify?hash=8f5e037f70efd1c6cda9535419fa7382ccb3895c4b9eeb982fcd3700b9ded373" | jq -e '.changed == false'Pinned hash 8f5e037f70ef, from Nov 15, 2026, 09:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/fr.fixou/fixou/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/fr.fixou/fixou)Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.
fixou MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the fixou MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the fixou MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the fixou MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the fixou MCP server have?
- 3 tools: 1 write, 2 read. create_request, list_categories and get_request.
Does the fixou MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the fixou MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_request.
Has the fixou MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 2, 2026. Every change is on this page and in its Atom feed.