General Tools
imtakt.dev
Provides German public transport information including stop lookup, route planning, live departures, and train tracking.
ENDPOINT 1
https://api.imtakt.dev/mcp
MCP server metadata
- Name
- imtakt
- Version
- 0.5.0
ImTakt is a German public-transport harness. Tools are 1:1 with POST /v1/find, /plan, /show, /status, /follow. Required flow: 1. imtakt_find on each place name — copy best.stopId, never invent GTFS/EVA ids 2. imtakt_plan with fromId/toId, prefer view=board, arrive, fare=d-ticket when relevant 3. Choose using facts on each option (fareOk, slack, riskLevel, minTransferMinutes, cancelled, delayMinutes, historical). Do not emit bestOption. 4. imtakt_show that optionId 5. imtakt_follow a runId only when tracking a vehicle decisionBoundary is always agent. Hosted API: https://api.imtakt.dev (no login, no API key). Hosted MCP: https://api.imtakt.dev/mcp.
Known tools 5
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.imtakt]
url = "https://api.imtakt.dev/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"imtakt": {
"type": "http",
"url": "https://api.imtakt.dev/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: imtakt
Remote MCP URL: https://api.imtakt.dev/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"imtakt": {
"url": "https://api.imtakt.dev/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"imtakt": {
"type": "http",
"url": "https://api.imtakt.dev/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "imtakt",
"transport": "streamable-http",
"url": "https://api.imtakt.dev/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.