Other · Remote MCP server
Pegel
German and Swiss river gauges, groundwater and flood levels from ten official sources.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
de.fluvigil/pegel- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-10
- Updated
- 2026-09-10
- Publisher
- de.fluvigil
- Namespace
- Namespace verified by the MCP Registry via the domain fluvigil.de · how
- Website
- fluvigil.de/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://fluvigil.de/mcp | X-Api-Key (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- fluvigil 1.1.0 · protocol 2025-06-18
- Tools discovered
- 6:
search_stations,get_flood_situation,get_station,get_readings,get_weather,get_forecast - Checked on
- 2026-10-05
How to connect Pegel
Pegel is a remote MCP server: there is nothing to install. Its endpoint is https://fluvigil.de/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: X-Api-Key (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Peer CashMCP server for preparing and tracking Peer Cash Base USDC cash-outs. | Local · stdio |
| Peer CommonsAgent reliability experiments and persistent discussions, shared context and subscriptions. | Remote · HTTPLive check: sign-in required |
| Peering MCPWho peers with whom, where they meet, and who an address range belongs to. PeeringDB and RDAP. | Local · stdio |
| Peerkith MCPCheck an agent work row, post one, and preflight a no-spend cap before any spend/send. | Local · stdio |
| PendpostLocal-first social MCP: an agent drafts and schedules posts; you approve before anything publishes. | Local · stdio |
| PenholderPreventive human-approval write-gate for AI agents: writes commit only after a human approves. | Remote · HTTPLive check: sign-in required |
| PennyPilot MCPOpen-core, local, read-only MCP server for Pennylane Company API v2. Auditable READ_ONLY_GUARD. | Local · stdio |
| PennyRail Transaction RouterFind and quote agent capabilities, then pay only the selected x402 execution URL. | Remote · HTTPLive check: ✗ no handshake |