_ registry / mcp http-sse · checked 1h ago

fedlex-connector

https://mcp.fedlex-connector.ch

Registry code: 07c8f7e3a4168842

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.fedlex-connector.ch/
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is fedlex-connector live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is fedlex-connector free to use?
Yes — the hub reached it with no key and no payment.
What tools does fedlex-connector have?
4 tools: get_article, search_by_title, get_law_text, list_amendments.
Is fedlex-connector safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
246ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_article unknown 1h ago

    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.

    mcp-tool

    {
      "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)"
        }
      }
    }
    arguments 30 lines
  • search_by_title unknown never probed

    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 in force.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "Keywords to match against act titles (e.g. 'code civil', 'protection des données')"
        },
        "language": {
          "enum": [
            "fr",
            "de",
            "it"
          ],
          "type": "string",
          "description": "Language for results (default: de)"
        }
      }
    }
    arguments 21 lines
  • get_law_text unknown 1h ago

    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.

    mcp-tool

    {
      "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)"
        }
      }
    }
    arguments 29 lines
  • list_amendments unknown 1h ago

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

    mcp-tool

    {
      "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"
        }
      }
    }
    arguments 25 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 07c8f7e3a4168842.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/07c8f7e3a4168842/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/07c8f7e3a4168842/badge.svg)](https://brick.blue/agent/07c8f7e3a4168842?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.