Is the Amirdaraee Luxembourg MCP server down?

mcp-registry/io.github.amirdaraee/luxembourg-mcp

Also listed as awesome/amirdaraee/luxembourg-mcp, glama/amirdaraee/luxembourg-mcp

healthy
Last checked 2026-10-23 17:25 UTC · handshake 1.4s

As of 2026-10-23 17:25 UTC, the Amirdaraee Luxembourg MCP server is up with a Glimind reliability score of 77/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 17 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
99.7%
checks observed
4,430
outages (90d)
17
tools
44

Keyless MCP access to official Luxembourg public data: laws, statistics, mobility, and more.

Install Amirdaraee Luxembourg MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http amirdaraee-luxembourg-mcp-server https://mcp.luxembourg-mcp.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "amirdaraee-luxembourg-mcp-server": {
      "type": "http",
      "url": "https://mcp.luxembourg-mcp.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: D (68/100)

D (68/100): 0 error(s), 4 warning(s) across 44 tool(s); ~3,981 tokens of tool definitions.
Scores higher than 3% of 15,593 MCP servers Glimind has audited.
Its tool list costs an agent ~3,981 tokens per session — more than 55% of servers.
67 → 68 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions42
Safety hints30
Token cost75
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (5)

44 of 44 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: geocode_address, get_accessibility_audits, get_accessibility_figures, get_air_quality, get_bike_sharing and 39 more

44 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

49 parameter(s) across 30 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: geocode_address, get_accessibility_audits, get_bike_sharing, get_cfl_parking, get_city_mobility and 25 more

Handshake + tools/list takes ~3,387 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

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: 43 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 30 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.amirdaraee%2Fluxembourg-mcp/fixes

geocode_address 1 change
{
  "name": "geocode_address",
  "description": "Resolve a Luxembourg address to official Geoportail coordinates.",
  "inputSchema": {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "query": {
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
get_accessibility_audits 1 change
{
  "name": "get_accessibility_audits",
  "description": "Get the latest public-sector digital accessibility audits.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "limit": {
        "type": "integer",
        "default": 10,
        "maximum": 100,
        "minimum": 1
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_accessibility_figures 1 change
{
  "name": "get_accessibility_figures",
  "description": "Get national Digital Accessibility Observatory key figures.",
  "inputSchema": {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  },
  "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/io.github.amirdaraee/luxembourg-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.amirdaraee/luxembourg-mcp"}) 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%2Fio.github.amirdaraee%2Fluxembourg-mcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.amirdaraee%2Fluxembourg-mcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.amirdaraee%2Fluxembourg-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.amirdaraee%2Fluxembourg-mcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.amirdaraee%2Fluxembourg-mcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.amirdaraee%2Fluxembourg-mcp?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:6f056cc970be3aca…, first seen 2026-10-17, included at leaf 11874 of 53,332. Version history · verify what your client received.

Tools (44)

Compare: most reliable data servers · most reliable search servers · most reliable knowledge servers · most reliable web servers · most reliable retrieval 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 Amirdaraee Luxembourg MCP server down right now?

As of 2026-10-23 17:25 UTC, the Amirdaraee Luxembourg MCP server is up with a Glimind reliability score of 77/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 17 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Amirdaraee Luxembourg MCP server provide?

Amirdaraee Luxembourg MCP server advertises 44 tools, including geocode_address, get_accessibility_audits, get_accessibility_figures, get_air_quality, get_bike_sharing.

How do I install Amirdaraee Luxembourg MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.luxembourg-mcp.com/mcp

Is the Amirdaraee Luxembourg MCP server safe to connect to an AI agent?

Glimind scanned all 44 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 Amirdaraee Luxembourg 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