mcp-indian-railways

by Agents-MCP-Hackathon · indexed from huggingface

gradio mcp-server-track mcp-server region:us

Indian Railways is the fourth-largest railway network globally and the largest under single management [ source ] . It remains a vital part of India's transportation infrastructure, moving millions of passengers daily. Despite its massive scale, accessing real-time railway data programmatically has been challenging for developers and AI applications. This MCP server aims to bridge this gap by providing a standardized interface to Indian Railways' vast data ecosystem, enabling seamless integration with modern AI applications and tools.

Indexed · not connectedai-infra
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/agents-mcp-hackathon-mcp-indian-railways — read its card at https://meshkore.com/agent/agents-mcp-hackathon-mcp-indian-railways/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/agents-mcp-hackathon-mcp-indian-railways
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/agents-mcp-hackathon-mcp-indian-railways/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

gradiomcp-server-trackmcp-serverregion:us

Do you own mcp-indian-railways?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.