What transport data sources back this API?

It uses LokiJS for timetable data, GTFS SQLite for static schedules, and live GTFS-RT feeds for real-time updates.

How can I access the MCP endpoint?

The MCP endpoint is available at POST /mcp using JSON-RPC over Streamable HTTP.

Is there support for monitoring or error reporting?

Optional integrations with Sentry and New Relic APM are available via environment variables.

Which clients are compatible with this MCP server?

Clients like Claude, Cursor, and the MCP SDK can interact with this server.

Timetable API Node

public-transportgtfsrealtimemcpukraine

Express API serving real-time Lviv public transport data with read-only MCP endpoint, no API key required.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

We couldn’t automatically confirm this listing starts correctly

We ran the install command below but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @modelcontextprotocol/inspector

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "vbhjckfd-timetable-api-node": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/inspector"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Overview

This server provides real-time public transport information for Lviv, Ukraine, including stop arrivals, live vehicle positions, route geometry, and nearby stop discovery. It exposes both REST and a read-only MCP endpoint over Streamable HTTP, backed by LokiJS, GTFS SQLite, and live GTFS-RT feeds. Use it when you need up-to-date transit data for Lviv without authentication or API keys.

Use cases

Fetch real-time arrivals for a specific stop

Retrieve static route geometry and details

Discover nearby public transport stops

Track live vehicle positions on routes

Integrate Lviv transit data into chatbots or LLMs via MCP

Key features

Real-time stop arrival predictions

Live vehicle position tracking

Route geometry and static data from GTFS

Nearby stop discovery

Read-only MCP endpoint supporting JSON-RPC over Streamable HTTP

No API key or authentication required

Capabilities & Tool Schemas

Inspect callable tools, capabilities, and parameters exposed to AI agents by Timetable API Node.

Extracted Tool Capabilities

Real-time stop arrival predictions

Live vehicle position tracking

Route geometry and static data from GTFS

Nearby stop discovery

Read-only MCP endpoint supporting JSON-RPC over Streamable HTTP

No API key or authentication required

Documentation Overview

Timetable API Node

Express-based API for Lviv transport timetable data with a read-only MCP endpoint.

Requirements

Node.js 26 (see .nvmrc)

Run locally

bash

nvm use
make start

Test

bash

nvm use && make test

Monitoring

Two optional integrations, both off unless their environment variable is set:

Variable	Effect
`SENTRY_DSN`	Error reporting via `instrument.js`
`NEW_RELIC_LICENSE_KEY`	New Relic APM via `newrelic.cjs`

New Relic runs as a preloaded agent, so npm start carries the flags:

server.ts

node -r dotenv/config -r newrelic --import newrelic/esm-loader.mjs index.js

dotenv/config is preloaded first so .env is populated before the agent reads its configuration. The config file is newrelic.cjs (the agent is CommonJS and this project is ESM) and holds no secrets — the key comes from the environment. /health is excluded from transactions via rules.ignore.

The account is in the EU region; its license key starts with eu01xx and the agent picks the collector from that prefix. Use the 40-character ingest license key, not an NRAK-... user API key.

Cloud Run reads the key from Secret Manager:

bash

gcloud run services update timetable-api-node --region=us-central1 --project=timetable-252615 --set-secrets=NEW_RELIC_LICENSE_KEY=new-relic-license-key:latest

MCP Server

This service exposes a public read-only MCP endpoint over Streamable HTTP.

MCP endpoint: /mcp
Server card: /.well-known/mcp/server-card.json
Discovery hint: /robots.txt (non-standard comment hint)

Production deployment (see cloudbuild.yaml for Cloud Run) serves REST and MCP from api.lad.lviv.ua. The main site lad.lviv.ua is the public transport website (this repo still links there in HTML sitemap and tables for people, not for the API host). Use your own origin when running locally.

LLM and `/mcp` flow

An MCP client (Claude, Cursor, or the MCP SDK) talks JSON-RPC over Streamable HTTP to POST /mcp. Tool handlers reuse the same Express actions as the REST API, backed by LokiJS timetable data, GTFS SQLite (via gtfs), and live GTFS-RT feeds (for example track.ua-gis.com).

mermaid

graph LR;
  Client[LLM or MCP client] -->|JSON-RPC Streamable HTTP| Mcp["POST /mcp"];
  Mcp --> Tools[Tool handlers];
  Tools --> Actions[Express actions];
  Actions --> Loki[(LokiJS)];
  Actions --> Gtfs[(GTFS SQLite)];
  Actions --> Rt[GTFS-RT upstream];
  Loki --> Actions;
  Gtfs --> Actions;
  Rt --> Actions;
  Actions --> Tools;
  Tools --> Mcp;
  Mcp -->|MCP tool result| Client;

Try the live API

MCP Inspector (local): run npx @modelcontextprotocol/inspector, then open the UI with transport and server URL prefilled (from the inspector README):

http://localhost:6274/?transport=streamable-http&serverUrl=https%3A%2F%2Fapi.lad.lviv.ua%2Fmcp

Postman / curl: call a tool on production

POST https://api.lad.lviv.ua/mcp with Content-Type: application/json. The Streamable HTTP transport may require additional headers your MCP client sets automatically; for a quick manual test, follow the same sequence your MCP SDK uses (session initialize, then tools/call). Example tools/call body shape:

config.json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_stop_realtime",
    "arguments": { "stop_id": 101 }
  }
}

Successful tool responses return a natural-language text summary inside MCP content items (type: "text") — e.g. "Stop «Opera»: 3 arrivals. Next: T01 → «Rynok» in 2 min." The full structured payload is in the structuredContent field (for schema-aware clients). Each structuredContent payload follows a strict UI contract:

config.json

{
  "view": "transit_realtime",
  "data": { "...": "tool-specific source data" },
  "ui_blocks": [
    { "type": "map", "data": { "...": "map renderer input" } },
    { "type": "arrival_list", "data": { "...": "arrival list renderer input" } }
  ]
}

Consistency rule: each vehicle rendered on map must either have a matching ETA in list data or eta_status: "unassigned".

Exposed tools

get_stop_realtime
get_route_static
get_route_realtime
get_stop_geometry
get_stops_around_location
get_nearby_vehicles
get_vehicle_info

get_stop_realtime — input & example

Arguments (JSON):

Field	Type	Required
`stop_id`	positive integer or digits-only string	yes

Example result (shape only; values from upstream):

config.json

{
  "view": "transit_realtime",
  "data": {
    "stop": { "id": "707", "name": "Стадіон Сільмаш", "lat": 49.84, "lng": 24.03 },
    "arrivals": [
      {
        "route": "T30",
        "direction": "Рясівська",
        "vehicle_type": "tram",
        "arrival_minutes": 4,
        "vehicle_id": "tram_123",
        "lat": 49.83,
        "lng": 24.02,
        "bearing": 120
      }
    ],
    "updated_at": "2026-01-23T12:00:00Z"
  },
  "ui_blocks": [
    {
      "type": "map",
      "data": { "center": [49.84, 24.03], "vehicles": [] }
    },
    {
      "type": "arrival_list",
      "data": { "arrivals": [] }
    }
  ]
}

get_route_static — input & example

Arguments (JSON):

Field	Type	Required
`route_name`	route short name (e.g. `"T30"`, `"32A"`) or numeric external ID	yes

Example result (shape only; stops truncated for brevity):

config.json

{
  "view": "transit_realtime",
  "data": {
    "route": {
      "name": "T30",
      "long_name": "Рясне-2 — Сихів",
      "color": "#e81717",
      "type": "tram"
    },
    "stops": [
      [
        {
          "id": "101", "name": "Головний вокзал", "lat": 49.841, "lng": 24.003,
          "departures": ["05:30", "05:52"],
          "schedule": { "workday": ["05:30", "05:52", "06:10"], "weekend": ["07:00", "07:30"] }
        },
        { "id": "707", "name": "Стадіон Сільмаш", "lat": 49.838, "lng": 24.021, "departures": [], "schedule": { "workday": [], "weekend": [] } }
      ],
      [
        { "id": "707", "name": "Стадіон Сільмаш", "lat": 49.838, "lng": 24.021, "departures": [], "schedule": { "workday": [], "weekend": [] } },
        { "id": "101", "name": "Головний вокзал", "lat": 49.841, "lng": 24.003, "departures": [], "schedule": { "workday": [], "weekend": [] } }
      ]
    ],
    "shapes": [
      [[49.841, 24.003], [49.839, 24.012], [49.838, 24.021]],
      [[49.838, 24.021], [49.839, 24.012], [49.841, 24.003]]
    ],
    "updated_at": "2026-01-23T12:00:00Z"
  },
  "ui_blocks": [
    {
      "type": "map",
      "data": {
        "center": [49.841, 24.003],
        "zoom": 13,
        "polylines": [[[49.841, 24.003], [49.839, 24.012], [49.838, 24.021]]],
        "stops": [
          { "id": "101", "name": "Головний вокзал", "lat": 49.841, "lng": 24.003 },
          { "id": "707", "name": "Стадіон Сільмаш", "lat": 49.838, "lng": 24.021 }
        ],
        "vehicles": []
      }
    }
  ]
}

stops[0] is direction 0 (outbound), stops[1] is direction 1 (return). departures and schedule are populated only for the first stop of direction 0; all other stops have empty arrays. schedule.workday contains Monday–Friday departure times; schedule.weekend contains Saturday–Sunday departure times. departures keeps today's schedule for backward compatibility. shapes follows the same two-element order. The map block uses direction-0 polyline and all unique stops as markers.

get_route_realtime — input & example

Arguments (JSON):

Field	Type	Required
`route_name`	route short name (e.g. `"T30"`, `"32A"`) or numeric external ID	yes

Example result:

Read the full README →View source on GitHub →

Related MCP Servers

View all in Travel & Transportation View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars

Stargazers on the source repository.

npm downloads

1.1M

Package downloads in the last 30 days.

Last commit

3d ago

Most recent push to the default branch.

Install check

Inconclusive

Didn't respond in our test window — often a slow first install.

Directory activity

2 views

Config copies, upvotes, and views on AllMCPs.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Timetable API Node

No, the API is public and requires no API key or authentication.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Timetable API Node AllMCPs Directory Badge

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/vbhjckfd-timetable-api-node?style=directory)](https://allmcps.com/mcp/vbhjckfd-timetable-api-node)

HTML Embed

<a href="https://allmcps.com/mcp/vbhjckfd-timetable-api-node"><img src="https://allmcps.com/api/badge/vbhjckfd-timetable-api-node?style=directory" alt="Timetable API Node on AllMCPs" /></a>

Technical Specs & Signals

CategoryTravel & Transportation

PricingFree

10/11 checks healthy over the last 32d

51Quality signal: Good · 51/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership6/20

Documentation & tools23/30

Adoption & activity9/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

Supply-chain signal

2 high-severity advisories on record for this package. Most advisories affect transitive dependencies and may not be exploitable in this server's actual usage — this is a directional signal, not a security audit.

Critical 1High 1Medium 0Low 0

Scanned 22d ago via OSV.dev · @modelcontextprotocol/inspector (npm)

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 🚆 Travel & Transportation →Best MCP servers for Travel & Transportation →Alternatives to Timetable API Node →Install in Claude Desktop Install in Cursor Install in VS Code

Timetable API Node

public-transportgtfsrealtimemcpukraine

Express API serving real-time Lviv public transport data with read-only MCP endpoint, no API key required.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

We couldn’t automatically confirm this listing starts correctly

We ran the install command below but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @modelcontextprotocol/inspector

No response to initialize.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "vbhjckfd-timetable-api-node": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/inspector"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Overview

Use cases

Fetch real-time arrivals for a specific stop

Retrieve static route geometry and details

Discover nearby public transport stops

Track live vehicle positions on routes

Integrate Lviv transit data into chatbots or LLMs via MCP

Key features

Real-time stop arrival predictions

Live vehicle position tracking

Route geometry and static data from GTFS

Nearby stop discovery

Read-only MCP endpoint supporting JSON-RPC over Streamable HTTP

No API key or authentication required

Capabilities & Tool Schemas

Inspect callable tools, capabilities, and parameters exposed to AI agents by Timetable API Node.

Extracted Tool Capabilities

Real-time stop arrival predictions

Live vehicle position tracking

Route geometry and static data from GTFS

Nearby stop discovery

Read-only MCP endpoint supporting JSON-RPC over Streamable HTTP

No API key or authentication required

Documentation Overview

Timetable API Node

Express-based API for Lviv transport timetable data with a read-only MCP endpoint.

Requirements

Node.js 26 (see .nvmrc)

Run locally

bash

nvm use
make start

Test

bash

nvm use && make test

Monitoring

Two optional integrations, both off unless their environment variable is set:

Variable	Effect
`SENTRY_DSN`	Error reporting via `instrument.js`
`NEW_RELIC_LICENSE_KEY`	New Relic APM via `newrelic.cjs`

New Relic runs as a preloaded agent, so npm start carries the flags:

server.ts

node -r dotenv/config -r newrelic --import newrelic/esm-loader.mjs index.js

The account is in the EU region; its license key starts with eu01xx and the agent picks the collector from that prefix. Use the 40-character ingest license key, not an NRAK-... user API key.

Cloud Run reads the key from Secret Manager:

bash

gcloud run services update timetable-api-node --region=us-central1 --project=timetable-252615 --set-secrets=NEW_RELIC_LICENSE_KEY=new-relic-license-key:latest

MCP Server

This service exposes a public read-only MCP endpoint over Streamable HTTP.

MCP endpoint: /mcp
Server card: /.well-known/mcp/server-card.json
Discovery hint: /robots.txt (non-standard comment hint)

LLM and `/mcp` flow

mermaid

graph LR;
  Client[LLM or MCP client] -->|JSON-RPC Streamable HTTP| Mcp["POST /mcp"];
  Mcp --> Tools[Tool handlers];
  Tools --> Actions[Express actions];
  Actions --> Loki[(LokiJS)];
  Actions --> Gtfs[(GTFS SQLite)];
  Actions --> Rt[GTFS-RT upstream];
  Loki --> Actions;
  Gtfs --> Actions;
  Rt --> Actions;
  Actions --> Tools;
  Tools --> Mcp;
  Mcp -->|MCP tool result| Client;

Try the live API

MCP Inspector (local): run npx @modelcontextprotocol/inspector, then open the UI with transport and server URL prefilled (from the inspector README):

http://localhost:6274/?transport=streamable-http&serverUrl=https%3A%2F%2Fapi.lad.lviv.ua%2Fmcp

Postman / curl: call a tool on production

config.json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_stop_realtime",
    "arguments": { "stop_id": 101 }
  }
}

config.json

{
  "view": "transit_realtime",
  "data": { "...": "tool-specific source data" },
  "ui_blocks": [
    { "type": "map", "data": { "...": "map renderer input" } },
    { "type": "arrival_list", "data": { "...": "arrival list renderer input" } }
  ]
}

Consistency rule: each vehicle rendered on map must either have a matching ETA in list data or eta_status: "unassigned".

Exposed tools

get_stop_realtime
get_route_static
get_route_realtime
get_stop_geometry
get_stops_around_location
get_nearby_vehicles
get_vehicle_info

get_stop_realtime — input & example

Arguments (JSON):

Field	Type	Required
`stop_id`	positive integer or digits-only string	yes

Example result (shape only; values from upstream):

config.json

{
  "view": "transit_realtime",
  "data": {
    "stop": { "id": "707", "name": "Стадіон Сільмаш", "lat": 49.84, "lng": 24.03 },
    "arrivals": [
      {
        "route": "T30",
        "direction": "Рясівська",
        "vehicle_type": "tram",
        "arrival_minutes": 4,
        "vehicle_id": "tram_123",
        "lat": 49.83,
        "lng": 24.02,
        "bearing": 120
      }
    ],
    "updated_at": "2026-01-23T12:00:00Z"
  },
  "ui_blocks": [
    {
      "type": "map",
      "data": { "center": [49.84, 24.03], "vehicles": [] }
    },
    {
      "type": "arrival_list",
      "data": { "arrivals": [] }
    }
  ]
}

get_route_static — input & example

Arguments (JSON):

Field	Type	Required
`route_name`	route short name (e.g. `"T30"`, `"32A"`) or numeric external ID	yes

Example result (shape only; stops truncated for brevity):

config.json

{
  "view": "transit_realtime",
  "data": {
    "route": {
      "name": "T30",
      "long_name": "Рясне-2 — Сихів",
      "color": "#e81717",
      "type": "tram"
    },
    "stops": [
      [
        {
          "id": "101", "name": "Головний вокзал", "lat": 49.841, "lng": 24.003,
          "departures": ["05:30", "05:52"],
          "schedule": { "workday": ["05:30", "05:52", "06:10"], "weekend": ["07:00", "07:30"] }
        },
        { "id": "707", "name": "Стадіон Сільмаш", "lat": 49.838, "lng": 24.021, "departures": [], "schedule": { "workday": [], "weekend": [] } }
      ],
      [
        { "id": "707", "name": "Стадіон Сільмаш", "lat": 49.838, "lng": 24.021, "departures": [], "schedule": { "workday": [], "weekend": [] } },
        { "id": "101", "name": "Головний вокзал", "lat": 49.841, "lng": 24.003, "departures": [], "schedule": { "workday": [], "weekend": [] } }
      ]
    ],
    "shapes": [
      [[49.841, 24.003], [49.839, 24.012], [49.838, 24.021]],
      [[49.838, 24.021], [49.839, 24.012], [49.841, 24.003]]
    ],
    "updated_at": "2026-01-23T12:00:00Z"
  },
  "ui_blocks": [
    {
      "type": "map",
      "data": {
        "center": [49.841, 24.003],
        "zoom": 13,
        "polylines": [[[49.841, 24.003], [49.839, 24.012], [49.838, 24.021]]],
        "stops": [
          { "id": "101", "name": "Головний вокзал", "lat": 49.841, "lng": 24.003 },
          { "id": "707", "name": "Стадіон Сільмаш", "lat": 49.838, "lng": 24.021 }
        ],
        "vehicles": []
      }
    }
  ]
}

get_route_realtime — input & example

Arguments (JSON):

Field	Type	Required
`route_name`	route short name (e.g. `"T30"`, `"32A"`) or numeric external ID	yes

Example result:

Read the full README →View source on GitHub →

Related MCP Servers

View all in Travel & Transportation View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars

Stargazers on the source repository.

npm downloads

1.1M

Package downloads in the last 30 days.

Last commit

3d ago

Most recent push to the default branch.

Install check

Inconclusive

Didn't respond in our test window — often a slow first install.

Directory activity

2 views

Config copies, upvotes, and views on AllMCPs.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Timetable API Node

No, the API is public and requires no API key or authentication.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/vbhjckfd-timetable-api-node?style=directory)](https://allmcps.com/mcp/vbhjckfd-timetable-api-node)

HTML Embed

<a href="https://allmcps.com/mcp/vbhjckfd-timetable-api-node"><img src="https://allmcps.com/api/badge/vbhjckfd-timetable-api-node?style=directory" alt="Timetable API Node on AllMCPs" /></a>

Technical Specs & Signals

CategoryTravel & Transportation

PricingFree

10/11 checks healthy over the last 32d

51Quality signal: Good · 51/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership6/20

Documentation & tools23/30

Adoption & activity9/15

Community engagement0/10

Supply-chain signal

Critical 1High 1Medium 0Low 0

Scanned 22d ago via OSV.dev · @modelcontextprotocol/inspector (npm)

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 🚆 Travel & Transportation →Best MCP servers for Travel & Transportation →Alternatives to Timetable API Node →Install in Claude Desktop Install in Cursor Install in VS Code

Timetable API Node

Quick Install

Client Config & Setup

Overview

Use cases

Key features

Capabilities & Tool Schemas

Documentation Overview

Timetable API Node

Requirements

Run locally

Test

Monitoring

MCP Server

LLM and /mcp flow

Try the live API

Exposed tools

Related MCP Servers

Adoption & maintenance

Reviews

Frequently Asked Questions about Timetable API Node

AllMCPs Directory Badge

Technical Specs & Signals

Supply-chain signal

Feature Your MCP Server

Own this project?

Share & Embed

Explore more

Timetable API Node

Quick Install

Client Config & Setup

Overview

Use cases

Key features

Capabilities & Tool Schemas

Documentation Overview

Timetable API Node

Requirements

Run locally

Test

Monitoring

MCP Server

LLM and /mcp flow

Try the live API

Exposed tools

Related MCP Servers

Adoption & maintenance

Reviews

Frequently Asked Questions about Timetable API Node

AllMCPs Directory Badge

Technical Specs & Signals

Supply-chain signal

Feature Your MCP Server

Own this project?

Share & Embed

Explore more

LLM and `/mcp` flow

LLM and `/mcp` flow