原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Italian Bus and Rail Search MCP Server

作者:Alexxanddr版本 0.3.0i★ 0i在你的电脑上运行代码仓库 ↗
注册名称io.github.Alexxanddr/italian-bus-search

安装方法

What it does

Read-only Italian bus searches and local NeTEx rail schedules.

  • Connects 在你的电脑上运行
  • Account or key No key needed
  • Category 搜索与 AI 记忆

可搭配使用

教 AI 做这类工作的 Skill,可与本项一起使用

timesfm

TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.

作者:google-research★ 35,6381 个 skill

Skill · 操作手册

Shadowbroker

Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…

作者:BigBodyCobain★ 11,6051 个 skill

Skill · 操作手册

google-maps-scraper

scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place

作者:gosom★ 8,2361 个 skill

Skill · 操作手册

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度0/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应0/8上次检查时云端端点有响应
使用分12/100

质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

通过 3/3 项检查 · 在你的电脑上运行

我们隐藏了部分命令

在本机运行:检查时在软件包仓库中找不到这个包

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器 · 作者的安装说明 · 同类的其他服务器

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

Claude 暂时无法连接 Italian Bus and Rail Search MCP Server

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

ChatGPT 暂时无法连接 Italian Bus and Rail Search MCP Server

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

你可以改用这些方式

B · 搜索与 AI 记忆 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

Claude Code 暂时无法连接 Italian Bus and Rail Search MCP Server

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

Cursor 暂时无法连接 Italian Bus and Rail Search MCP Server

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

VS Code 暂时无法连接 Italian Bus and Rail Search MCP Server

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

卡住了?问问正在用 Italian Bus and Rail Search MCP Server 的人💬 讨论 →

一览

每周下载量i
不在 npm/PyPI 上
连接方式
在你的电脑上运行
最新版本i
0.3.0
发布到注册中心i
2026年10月26日
代码最后更新i
2026年11月7日
作者
Alexxanddr
软件包
npm: italian-bus-search
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

在你的电脑上运行,适用于

GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

全部应用及其优缺点 →

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 Alexxanddr 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于12天前

  • ✓ 通过

    有许可证

    使用 MIT

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

已公开的漏洞(OSV.dev)

OSV.dev 中没有 italian-bus-search@0.3.0 的记录

只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/alexxanddr-italian-bus-search.svg)](https://mcp.popnx.com/en/servers/alexxanddr-italian-bus-search)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“搜索与 AI 记忆”中的其他服务器比较i

  • 星标数多于此分类中其他 6430 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 6430 个服务器的 61% 更新
  • 基础检查结果等于或优于此分类中其他 6430 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Italian Bus and Rail Search MCP Server 安全吗?

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于12天前,最新版本(0.3.0)于24天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它?

同一分类中有:OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

OpenSEO

Keyword research, site audits, rank tracking and AI visibility for your AI agent.

作者:every-app广泛使用★ 2.8万5天前更新

在云端运行✓ everyapp.com

Exa

Connect AI agents to Exa for web search, content fetching, and multi-step research.

作者:exa-labs广泛使用★ 52442个月前更新

在云端运行✓ 服务方 · exa.aiPopNx 团队已实际试用

Microsoft Learn MCP

Official Microsoft Learn MCP Server – real-time, trusted docs & code samples for AI and LLMs.

作者:MicrosoftDocs广泛使用★ 199712个月前更新

在云端运行✓ 服务方 · microsoft.comPopNx 团队已实际试用

Docs

Search and read Empryo's documentation. Read-only, no auth, no local access.

作者:proxysoul正在增长★ 16262个月前更新

在云端运行✓ empryo.com
与相似项目对比
本项
Italian Bus and Rail Search MCP Server
OpenSEOExaMicrosoft Learn MCPDocsCOTAL actions (cotal.ai)
运行位置需要安装在电脑上在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否否否否否否
可在 Claude 中按 + 添加否是是是否否
基础检查3/35/52/44/44/44/4
许可证MITMITMITCC-BY-4.0NOASSERTIONApache-2.0
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Italian Travel Search

An unofficial, read-only TypeScript service for live Italian coach and train searches through HTTP and Model Context Protocol interfaces.

The project hides provider-specific station catalogs, request formats, fare structures, and multi-leg responses behind one shared application core. Italo pricing initializes an anonymous technical session and temporary planning resource; customer login, fare selection, seat reservation, and payment are excluded.

[!IMPORTANT]

This project is not affiliated with or endorsed by Itabus, Autoservizi Salemi, Autolinee Federico, MarinoBus, or FlixBus. Provider names and trademarks belong to their owners. Before enabling a live adapter, confirm that your use complies with the provider's terms, applicable law, and any required authorization. This repository does not grant data-extraction or redistribution rights.

Features

  • One response model for locations and journeys across different booking platforms.
  • Live adapters for five bus operators and two train operators.
  • Partial results when one provider fails and another succeeds.
  • MCP over local stdio or stateless Streamable HTTP at /mcp, with backward-compatible bus tools and separate rail tools.
  • Trenitalia and Italo station and journey searches directly from their live booking APIs.
  • Official links for continuing a search manually on provider sites.
  • Searches respect the requested departure day; city searches preserve all Itabus stops, with physical-stop names/addresses where available.
  • Rail warnings identify urban transfers excluded from the quoted fare.
  • Structured, provider-scoped errors instead of leaked upstream responses.
  • Finite upstream request timeouts and bounded asynchronous quote polling.
  • One-hour location caches and 60-second journey caches.
  • Opt-in immutable journey pagination with five-minute in-memory snapshots, shared by HTTP and MCP.
  • Per-client in-memory rate limiting at 60 requests per minute.
  • Offline tests with synthetic fixtures; the test suite never contacts provider sites.
  • A small runtime dependency surface: the official MCP SDK and Zod.

Supported providers

Provider IDOperatorIntegrationLocationsJourneys
itabusItabusDemandware endpointsLiveLive
salemiAutoservizi SalemiAlbatross tenantLiveLive
federicoAutolinee FedericoAlbatross tenantLiveLive
marinobusMarinoBusAlbatross tenantLiveLive
flixbusFlixBusGlobal FlixBus search APILiveLive

Public provider behavior and limitations are documented in the bus and train API guides below.

Train stations, journeys, prices and availability come directly from Trenitalia and Italo booking APIs. No timetable download, dataset, storage volume or initialization command is required. If one operator fails, its error is reported alongside the other operator's results. ViaggiaTreno and Italo live boards/standalone status remain independent; Italo quote sessions are cleaned up best-effort.

Requirements

  • Node.js 22.18 or newer
  • npm

Quick start

git clone https://github.com/Alexxanddr/italian-travel-search.git

cd italian-travel-search npm install cp .env.example .env npm start

The server listens on http://127.0.0.1:3000 by default.

curl http://127.0.0.1:3000/health

curl http://127.0.0.1:3000/providers curl http://127.0.0.1:3000/train-providers curl 'http://127.0.0.1:3000/locations?query=Roma&provider=marinobus'

For journey searches, use today or a future date in Europe/Rome:

curl 'http://127.0.0.1:3000/journeys?origin=Roma&destination=Milano&date=YYYY-MM-DD&adults=1&children=0&provider=marinobus'

YYYY-MM-DD is a placeholder and must be replaced before running the command.

Web frontend

The dark, Italian-language Binario interface lives in frontend/ in this repository. It searches bus and train journeys through the HTTP API, with a single origin/destination/date form, progressive results, stable snapshot pagination and official booking links. It has no account, payment, AI model or direct provider/MCPHub access in the browser.

From the repository root:

npm ci

npm ci --prefix frontend npm start

In another terminal, from the same repository root:

npm run web:dev

Open http://127.0.0.1:5173

The local frontend proxy defaults to the API at http://127.0.0.1:3000. Optional local configuration belongs in ignored frontend/.env.local; copy frontend/.env.example if needed. Never use browser-exposed VITE_* variables for credentials.

npm run build:all

Install Chromium once before running browser tests:

cd frontend npx playwright install chromium cd .. npm run check:all

npm run build and npm run check retain their existing backend behavior. The frontend shares domain types and keeps its own build lockfile. The existing root Dockerfile builds both parts into one image: Node serves the UI at /, the browser API at /api/*, the existing HTTP endpoints and MCP at /mcp, all on port 3000. No NGINX or second container is needed. The npm package remains API/MCP-focused and excludes frontend assets/tooling. See the frontend guide, single-image Docker packaging, and publication review. Publishing source code does not require hosting a live website.

The published image is multiarch: linux/amd64 and linux/arm64 share the same tag, and Docker selects the matching architecture automatically.

One image, one process
docker build -t italian-travel-search:local .

docker run --rm -p 127.0.0.1:3000:3000 italian-travel-search:local

UI: http://127.0.0.1:3000/

API: http://127.0.0.1:3000/api/providers (also /providers)

MCP: http://127.0.0.1:3000/mcp

Without Docker, npm run build:all followed by node dist/index.js serves the same combined application. npm run web:dev remains the optional development server with live rebuilding.

HTTP interface

MethodPathPurpose
GET/healthProcess liveness
GET/providersAdapter status and operational reason
GET/train-providersTrain operators and configured schedule/price/live capabilities
GET/locationsProvider location search
GET/journeysNormalized one-way journey search
GET/train-locationsTrenitalia/Italo station search
GET/train-journeysLive rail journeys, availability and nullable prices
GET/train-statusStandalone live status where enabled
GET/station-boardLive arrivals/departures where enabled
POST/mcpStateless MCP Streamable HTTP endpoint

/locations and /journeys accept an optional provider parameter. Without it, all providers are queried independently and successful data is preserved alongside provider-scoped errors.

The complete contract is split into the Bus API and Train API, with shared behavior indexed in HTTP API.

MCP server

The simplest MCP configuration runs the published package directly with npx:

{

"mcpServers": { "italian-travel-search": { "command": "npx", "args": ["-y", "italian-travel-search@latest"] } } }

Alternatively, build and start the local stdio server:

npm run build

npm run mcp:built

The existing list_providers, search_locations, and search_journeys bus tools remain compatible. Location and journey searches accept optional offset/limit; increment offset by limit until truncated is false to retrieve every page. Rail adds list_train_providers, search_train_locations, search_train_journeys, get_train_status, and get_station_board. Trenitalia and Italo price and live adapters are enabled; Italo live tools retain date-unverified semantics.

For exhaustive journey searches, start with snapshot: true and continue with only the returned searchId, offset and limit. This keeps prices, errors, order and totals identical across pages. Expired IDs require a new search. The same opt-in flow exists over HTTP; see stable pagination.

{

"mcpServers": { "italian-travel-search": { "command": "node", "args": ["/absolute/path/to/italian-travel-search/dist/mcp/stdio.js"] } } }

For a container or remote MCPHub deployment, start the HTTP process and point the client to http://italian-travel-search:3000/mcp. The container image is ghcr.io/alexxanddr/italian-travel-search:latest. No dataset initialization or persistent volume is needed.

See MCP interface for the authoritative tool contract, limits, errors, and development command.

Architecture

The application has four layers:

  1. HTTP and MCP adapters validate their transport-specific requests;
  2. shared validation and SearchService orchestrate searches and partial results;
  3. each provider adapter translates a remote protocol into domain types;
  4. the domain module owns normalized data and error contracts.

Provider adapters implement one shared interface, so callers do not know whether a result came from Itabus Demandware or an Albatross tenant. See Architecture for modules, seams, data flow, caches, and test strategy.

Development

npm run dev

npm run mcp npm run check

npm run check runs the complete offline test suite, TypeScript type checking, and the configured lint check. To add an operator, follow Adding a provider; do not infer a new integration from HTML alone or copy credentials into fixtures.

Deployment

The default server deliberately binds to loopback and keeps rate-limit and cache state in process memory. Read Operations before placing it behind a reverse proxy or running multiple replicas.

Project documentation

  • HTTP API — shared behavior and error contract.
  • Bus API — bus providers, locations, journeys, and examples.
  • Train API — rail schedules, live prices/status, provenance, and examples.
  • MCP interface — authoritative tools, results, limits, and transport contract.
  • Architecture — modules, seams, flows, and design decisions.
  • Adding a provider — research, implementation, and verification checklist.
  • Operations — configuration, deployment constraints, and failure handling.
  • Glossary — stable project terminology.
  • Contributing — local workflow and pull-request expectations.
  • Security policy — private vulnerability reporting and supported versions.
  • Agent instructions — compact routing instructions for coding agents.

Scope and limitations

  • Searches are one-way only.
  • Availability is a provider-reported signal, not a seat or price guarantee.
  • Prices and schedules can change between search and purchase; rail results expose live observation and source metadata. The legacy field name timetableSource is retained for compatibility.
  • Caches and rate limits reset when the process restarts and are not shared across replicas.
  • Upstream interfaces are unofficial and can change without notice.
  • Both interfaces intentionally exclude accounts, bookings, payments, and CAPTCHA handling.

Always complete and confirm a purchase on the official provider site linked by bookingUrl.

Contributing and security

Contributions are welcome; start with CONTRIBUTING.md

只显示了开头部分;其余内容请在仓库中阅读