Skip to content
MCPSTAMP
MCP server report

Code civil (France) MCP server

io.arxo/code-civil

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 97 of 100 (grade A), higher than 84.8% of the 33,003 registry servers that responded over HTTPS that day. Ready for Claude, ChatGPT, Gemini and MCP Registry.

Measured facts

Score
97A
Sign-in
No sign-in
Tools listed
21
Protocol version
2025-11-25
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Ready No blocking check failed.
ChatGPT app directory Ready No blocking check failed.
Gemini Connected Apps Ready No blocking check failed.
Official MCP Registry Ready No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

One check to fix

  1. Warning

    Tool descriptions

    tool_descriptions

    Measured 2 over 2000 chars: law_packages, law_query

    Keep each tool description between 60 and 2000 characters: when to use it, what it returns, key limits.

16 checks passed, 10 did not run

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, JSON-RPC error for unknown method, GET answers SSE or 405, initialize latency, serverInfo name and version, Server instructions, tools capability declared, tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, readOnlyHint or destructiveHint on every tool, Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT), Human-readable title on every tool.

Not run. Sign-in method the store supports (OAuth or none), 401 carries WWW-Authenticate resource_metadata, Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields, issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), refresh_token grant advertised. The server asks for no sign-in, so the OAuth checks do not apply.

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for Code civil (France)

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fmcp.arxo.io%2Fmcp%2Fcode-civil)](https://www.mcpstamp.com/r/io-arxo-code-civil/)

HTML

<a href="https://www.mcpstamp.com/r/io-arxo-code-civil/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Fmcp.arxo.io%2Fmcp%2Fcode-civil" alt="McpStamp score" height="20"></a>
Registry entry

About this server

French Civil Code (LEGI) as executable rules: facts and a legal date in, answers with grounds out
Registry name
io.arxo/code-civil
Remote URL
https://mcp.arxo.io/mcp/code-civil
Version
0.1.10
Source
github.com/arxohq/arxo-code-civil
Website
code-civil.law.arxo.io/
Checked
2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade A servers

All grade A servers · All server reports · State of MCP readiness, November 2026