Lombardia Trains
NUGET · LOMBARDIATRAINS.MCP · SCANNED SEP 20
Live Lombardy train boards, delays, platforms, and journey planning. No API key.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 13 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 799 tokens (~114/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Lombardia Trains MCP server?
Lombardia Trains runs locally as a NuGet package, launched with dnx LombardiaTrains.Mcp@0.1.1 --yes. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
nuget · LombardiaTrains.Mcp
claude mcp add denisraimondi-lombardia-trains -- dnx LombardiaTrains.Mcp@0.1.1 --yes
{
"mcpServers": {
"denisraimondi-lombardia-trains": {
"command": "dnx",
"args": [
"LombardiaTrains.Mcp@0.1.1",
"--yes"
]
}
}
} {
"servers": {
"denisraimondi-lombardia-trains": {
"command": "dnx",
"args": [
"LombardiaTrains.Mcp@0.1.1",
"--yes"
]
}
}
} codex mcp add denisraimondi-lombardia-trains -- dnx LombardiaTrains.Mcp@0.1.1 --yes
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"denisraimondi-lombardia-trains": {
"type": "local",
"command": [
"dnx",
"LombardiaTrains.Mcp@0.1.1",
"--yes"
],
"enabled": true
}
}
} mcp_servers:
denisraimondi-lombardia-trains:
command: "dnx"
args: ["LombardiaTrains.Mcp@0.1.1", "--yes"] {
"McpServers": {
"denisraimondi-lombardia-trains": {
"Transport": "stdio",
"Command": "dnx",
"Arguments": [
"LombardiaTrains.Mcp@0.1.1",
"--yes"
]
}
}
} {
"mcpServers": {
"denisraimondi-lombardia-trains": {
"command": "dnx",
"args": [
"LombardiaTrains.Mcp@0.1.1",
"--yes"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed nuget/LombardiaTrains.Mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | nuget |
| Reason | Signature present, unreadable |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_connection ~128
Direct trains between two stations, with departure, arrival, duration, delay and platform. Only direct services: this reads live boards rather than a timetable, so journeys needing a change are not found and the answer says so.
| Name | Type | Req | Description |
|---|---|---|---|
| at | string|null | – | When to leave, as 'HH:mm' for today or ISO '2026-08-29T09:00'. Defaults to now. |
| from | string | yes | Origin station code or name. |
| limit | integer | – | How many connections to return. Default 5. |
| to | string | yes | Destination station code or name. |
No output schema declared.
No examples provided.
find_journey ~208
Full journey between two places, changes included. Use this rather than find_connection whenever the two places are not obviously on the same line, or when a change may be needed. Plans from the Lombardy regional timetable, which reaches the Swiss stations on the cross-border lines, and falls back to Swiss open data for anywhere it does not cover. Returns timetabled times: pair it with get_departures or get_train for delays, platforms and cancellations.
| Name | Type | Req | Description |
|---|---|---|---|
| at | string|null | – | When to leave, as 'HH:mm' for today or ISO '2026-08-29T09:00'. Defaults to now. |
| from | string | yes | Origin, as a place or station name: 'Milano Centrale', 'Malpensa', 'Como'. |
| limit | integer | – | How many journeys to return. Default 3. |
| to | string | yes | Destination, as a place or station name. May be in Switzerland: 'Lugano', 'Chiasso'. |
No output schema declared.
No examples provided.
get_arrivals ~100
Arrival board for a station: time, train, origin, delay and platform.
| Name | Type | Req | Description |
|---|---|---|---|
| at | string|null | – | When, as 'HH:mm' for today or ISO '2026-08-29T09:00' for another day. |
| limit | integer | – | How many rows to return. Default 10. |
| station | string | yes | Station code such as 'S01136', or a name such as 'milano centrale'. |
No output schema declared.
No examples provided.
get_departures ~143
Departure board for a station: time, train, destination, delay in minutes (negative means early) and platform ('-' when not yet assigned). Works for future dates as well as today.
| Name | Type | Req | Description |
|---|---|---|---|
| at | string|null | – | When, as 'HH:mm' for today or ISO '2026-08-29T09:00' for another day. Defaults to now. Call the 'now' tool first if the user said something relative like 'Saturday'. |
| limit | integer | – | How many rows to return. Default 10. |
| station | string | yes | Station code such as 'S01136', or a name such as 'milano centrale'. |
No output schema declared.
No examples provided.
get_train ~75
Live status of a single train, stop by stop: delay, platforms, cancellations and crowding where published. Asks Trenord first and falls back to ViaggiaTreno, because neither source covers every line on its own.
| Name | Type | Req | Description |
|---|---|---|---|
| trainNumber | string | yes | Train number, for example '4307' or '11866'. |
No output schema declared.
No examples provided.
now ~57
Current date and time in Italy, with the day of the week. Call this before answering anything relative such as 'today', 'tonight', 'Saturday' or 'in an hour': the other tools need an explicit date and cannot guess one.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_station ~88
Find railway stations by name and return their codes. Names are frequently ambiguous — 'Milano' matches twenty-six stations, and many towns have both a national station and a separate Nord one served by different trains — so check here first when the user gave a name rather than a code.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Full or partial station name, for example 'milano centrale' or 'como'. |
No output schema declared.
No examples provided.
What is the Lombardia Trains MCP server?
Lombardia Trains is an MCP server listed in the public MCP registry as io.github.DenisRaimondi/lombardia-trains. Live Lombardy train boards, delays, platforms, and journey planning. No API key. This page covers its NuGet package (LombardiaTrains.Mcp).
Is the Lombardia Trains MCP server safe to use?
Lombardia Trains scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Lombardia Trains MCP server expose?
Lombardia Trains exposes 7 tools: get_departures, now, search_station, get_arrivals, get_train, and 2 more. Their descriptions and schemas cost roughly 799 tokens of context every time the server is loaded.
Is the Lombardia Trains MCP server still maintained?
Lombardia Trains is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Lombardia Trains MCP server under?
Lombardia Trains declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.