Is the Fedlex Connector MCP server down?

mcp-registry/ch.fedlex-connector/fedlex-connector · v1.0.0

Also listed as glama/jaytheskier/fedlex-connector

healthy
Last checked 2026-10-26 18:43 UTC · handshake 117ms

As of 2026-10-26 18:43 UTC, the Fedlex Connector MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 6 minutes.

uptime (30d checks)
100%
checks observed
4,938
outages (90d)
7
tools
4

Search Swiss federal legislation: laws, articles, amendments via the Fedlex SPARQL endpoint.

Point your MCP client at this streamable-http endpoint: https://mcp.fedlex-connector.ch/

Agent-readiness: B (85/100)

B (85/100): 0 error(s), 1 warning(s) across 4 tool(s); ~797 tokens of tool definitions.
Scores higher than 45% of 15,767 MCP servers Glimind has audited.
Its tool list costs an agent ~797 tokens per session — lighter than 80% of servers.
84 → 85 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (2)

4 of 4 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: get_article, get_law_text, list_amendments, search_by_title

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 4 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fch.fedlex-connector%2Ffedlex-connector/fixes

get_article 1 change
{
  "name": "get_article",
  "description": "Retrieve a single article when you already know the EXACT article number (e.g. from a cross-reference). Do NOT call this tool repeatedly to search for provisions — use get_law_text instead to fetch the full act or a section and locate relevant articles in the text.",
  "inputSchema": {
    "type": "object",
    "required": [
      "rs_number",
      "article"
    ],
    "properties": {
      "date": {
        "type": "string",
        "description": "Consolidation date in YYYY-MM-DD format. Defaults to the latest available version."
      },
      "article": {
        "type": "string",
        "description": "Article number (e.g. '3', '28a', '41')"
      },
      "language": {
        "enum": [
          "fr",
          "de",
          "it"
        ],
        "type": "string",
        "description": "Language (default: de)"
      },
      "rs_number": {
        "type": "string",
        "description": "RS/SR number (e.g. '210' for CC, '220' for CO, '311.0' for CP)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_law_text 1 change
{
  "name": "get_law_text",
  "description": "Retrieve the official consolidated text of a Swiss federal act (or a specific title/chapter) directly from Fedlex (fedlex.admin.ch). This is the PRIMARY tool for answering Swiss law questions — always start here. Fetch the full act or a specific section, then locate relevant provisions in the returned text. Prefer this over get_article unless you already know the exact article number.",
  "inputSchema": {
    "type": "object",
    "required": [
      "rs_number"
    ],
    "properties": {
      "page": {
        "type": "number",
        "description": "Page number for paginated results (default: 1). Large acts are split across multiple pages."
      },
      "section": {
        "type": "string",
        "description": "Limit to a specific title, chapter, or part (e.g. 'Titre huitième', 'Zweiter Teil'). If omitted, returns the full act."
      },
      "language": {
        "enum": [
          "fr",
          "de",
          "it"
        ],
        "type": "string",
        "description": "Language (default: de)"
      },
      "rs_number": {
        "type": "string",
        "description": "RS/SR number (e.g. '210' for CC, '220' for CO)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
list_amendments 1 change
{
  "name": "list_amendments",
  "description": "List consolidation version dates for a Swiss federal act. Returns the dates each consolidated version took effect.",
  "inputSchema": {
    "type": "object",
    "required": [
      "rs_number"
    ],
    "properties": {
      "since": {
        "type": "string",
        "description": "Start date in YYYY-MM-DD format (default: 1 year ago)"
      },
      "language": {
        "enum": [
          "fr",
          "de",
          "it"
        ],
        "type": "string",
        "description": "Language for amendment titles (default: de)"
      },
      "rs_number": {
        "type": "string",
        "description": "RS/SR number"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ch.fedlex-connector/fedlex-connector"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/ch.fedlex-connector/fedlex-connector"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fch.fedlex-connector%2Ffedlex-connector.svg)](https://glimind.com/server/mcp-registry%2Fch.fedlex-connector%2Ffedlex-connector?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fch.fedlex-connector%2Ffedlex-connector?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fch.fedlex-connector%2Ffedlex-connector.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fch.fedlex-connector%2Ffedlex-connector.svg
   :target: https://glimind.com/server/mcp-registry%2Fch.fedlex-connector%2Ffedlex-connector?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:5fd383c66c82def8…, first seen 2026-10-17, included at leaf 16286 of 74,820. Version history · verify what your client received.

Tools (4)

Compare: most reliable knowledge servers · most reliable retrieval servers · most reliable data servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Fedlex Connector MCP server down right now?

As of 2026-10-26 18:43 UTC, the Fedlex Connector MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 6 minutes.

How many tools does Fedlex Connector MCP server provide?

Fedlex Connector MCP server advertises 4 tools, including get_article, get_law_text, list_amendments, search_by_title.

How do I install Fedlex Connector MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.fedlex-connector.ch/

Is the Fedlex Connector MCP server safe to connect to an AI agent?

Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Fedlex Connector MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve