Skip to content
Fedlex Connector logo

Fedlex Connector MCP server

Which MCP servers are Fedlex Connector's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-23

← Back to Fedlex Connector

Whose server it is
  • Registry namech.fedlex-connector/fedlex-connectorverified in the MCP registry

The registry name sits under fedlex-connector.ch. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-23
  • Stateanswerschecked 2026-10-23
  • Tools4
  • Server calls itselffedlex-connector
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-23 the server answered initialize and tools/list without a sign-in. First answer in 93 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: search Swiss federal acts by title; retrieve full text or single articles of federal acts.
  • Checked on 5 of the 7 days it takes to judge reliability.

Once connected

  • For "search Swiss federal acts by title", the likely first call is search_by_title.
  • For "retrieve full text or single articles of federal acts", the likely first call is get_law_text.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 5, the first on 2026-10-23
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
  • What an agent can do with it2 of 2 use cases
  • Use7 GitHub stars
  • Answeredmeasuring5 of the 7 daily checks it takes to print a share
  • Median first answer93 ms
  • Space in an agent's context≈ 717 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once
  • Not saying whether it only reads or can destroy: 4 of 4

What an agent can do with it

  • can do · search Swiss federal acts by title
  • can do · retrieve full text or single articles of federal acts
  • not sure · list amendments to a federal act over a period

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers4 tools · read 2026-10-23
  • search_by_title

    Search Swiss federal legislation titles in the Classified Compilation (RS/SR) on Fedlex. Use to find the RS number of a law when you know its name but not its number. Searches titles only, not article content. Returns only acts currently…

  • get_article

    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…

  • get_law_text

    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…

  • list_amendments

    List consolidation version dates for a Swiss federal act. Returns the dates each consolidated version took effect.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "fedlex-connector": {
      "type": "http",
      "url": "https://mcp.fedlex-connector.ch/"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http fedlex-connector https://mcp.fedlex-connector.ch/

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.fedlex-connector.ch/ as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.