Other · Remote MCP server
Hydrant
Track issues, projects and dependencies with your agent in a workspace you control.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.hydrant/hydrant- Version
- 1.0.1
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-27
- Updated
- 2026-09-27
- Publisher
- dev.hydrant
- Namespace
- Namespace verified by the MCP Registry via the domain hydrant.dev · how
- Website
- hydrant.dev/help/agents/connect
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://hydrant.dev/api/mcp | None |
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 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Hydrant
Hydrant is a remote MCP server: there is nothing to install. Its endpoint is https://hydrant.dev/api/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.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
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 |
|---|---|
| Hvilkenai MCPDaily Scandinavian AI benchmark - Norwegian, Swedish, Danish. 12+ models tested. | Remote · HTTPLive check: ✓ handshake |
| HVTracker MCPPre-connect trust checks for AI agents and MCP servers using HVTracker's public trust registry. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| HybridS3Self-hosted S3-compatible object storage server with an MCP interface for AI agents. | Local · HTTP |
| Hyde MCPDiscover and trade tokenize-anything coins on hyde.trade (Robinhood Chain). Non-custodial. | Local · stdio |
| hypawave MCPAgent-to-agent Lightning commerce & messaging: buy, sell, discover, send encrypted files. | Local · stdio |
| HypelineGive an AI agent eyes on the web: turn any feed, page, or stream into deduplicated change events. | Remote · HTTPLive check: ✗ no handshake |
| Hyper MCPA fast, secure MCP server that extends its capabilities through WebAssembly plugins. | Local · stdio |
| Hyperiux VaultBrowse, inspect, and retrieve installable React and Next.js interaction effects from Hyperiux Vault. | Local · stdio |