Hydrant is the official remote MCP server from hydrant.dev. It answers at https://hydrant.dev/api/mcp over streamable HTTP and asks you to sign in with your hydrant.dev account before it lists its tools, so your client opens a login the first time it connects. Our probes reached it 4 of 4 times since 27 September 2026; the last check, on 12 November 2026, got the sign-in challenge, so it is up.
Track issues, projects and dependencies with your agent in a workspace you control.
Description as the publisher wrote it.
A sign-in. The server refused to list its tools to an anonymous client and answered with an authentication challenge, which is how an MCP server protected by OAuth behaves. Add it with one of the setups below; the first connection opens a login for your hydrant.dev account, and the tools appear once you have approved it.
Every block below points at https://hydrant.dev/api/mcp. Pick your client and copy.
claude mcp add --transport http hydrant https://hydrant.dev/api/mcp
{
"mcpServers": {
"hydrant": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://hydrant.dev/api/mcp"]
}
}
}{
"mcpServers": {
"hydrant": {
"url": "https://hydrant.dev/api/mcp"
}
}
}{
"servers": {
"hydrant": {
"type": "http",
"url": "https://hydrant.dev/api/mcp"
}
}
}{
"context_servers": {
"hydrant": {
"url": "https://hydrant.dev/api/mcp"
}
}
}{
"mcpServers": {
"hydrant": {
"serverUrl": "https://hydrant.dev/api/mcp"
}
}
}{
"mcpServers": {
"hydrant": {
"url": "https://hydrant.dev/api/mcp"
}
}
}name: Hydrant
version: 0.0.1
schema: v1
mcpServers:
- name: Hydrant
type: streamable-http
url: https://hydrant.dev/api/mcp{
"mcpServers": {
"hydrant": {
"httpUrl": "https://hydrant.dev/api/mcp"
}
}
}{
"mcpServers": {
"hydrant": {
"type": "http",
"url": "https://hydrant.dev/api/mcp"
}
}
}{
"mcpServers": {
"hydrant": {
"url": "https://hydrant.dev/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fhydrant.dev%2Fapi%2Fmcp&type=streamable_http&id=hydrant&name=Hydrant
It answered our last check on 12 November 2026 in 302 ms. Over 4 checks since 27 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by hydrant.dev and served from hydrant.dev, the vendor's own domain: https://hydrant.dev/api/mcp.
Add the server with a setup above. The first time your client connects it opens the sign-in page for hydrant.dev; approve it and the tools load.
It answered our last check on 12 November 2026 in 302 ms. Over 4 checks since 27 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://hydrant.dev/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It needs a sign-in rather than a key you paste: the server answered with an authentication challenge, so your client runs the login when it first connects.
Publisher: dev.hydrant. Endpoint host: hydrant.dev. ARD identifier: urn:air:dev.hydrant:mcp:hydrant.
First indexed 27 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.