HydraScope MCP

● Active

dev.krusch/hydrascope

Structural graph context, temporal SUPERSEDES lineage, and 4-axis ontology MCP on HydraDB.

Connect this server

One click to install, or copy the config below. Suits: Claude Desktop · Cursor.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "hydrascope": {
      "command": "npx",
      "args": [
        "-y",
        "hydrascope@0.1.1",
        "mcp"
      ]
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add hydrascope -- npx -y hydrascope@0.1.1 mcp
OpenAI Codex CLI
codex mcp add hydrascope -- npx -y hydrascope@0.1.1 mcp
VS Code
code --add-mcp '{"name":"hydrascope","type":"stdio","command":"npx","args":["-y","hydrascope@0.1.1","mcp"]}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Data & Analytics
Version
0.1.1
Registry
active
Published
11/19/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 21, 2026

Looks healthy: HydraScope MCP is maintained, open source.

Maintained
Active
Last commit 3 days ago (Nov 19, 2026), 0 open issues.
Official registry
Active
Published as dev.krusch/hydrascope in the official MCP registry, version 0.1.1.
Source
Open source, MIT
Public repository under the MIT licence, 0 stars, 0 forks.
Runs
On your machine
A local npm package started by your client; it can reach whatever your user account can.
Credentials
None declared
The registry entry declares no required environment variables.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself.

On GitHub

read Nov 19, 2026
Stars
0
Forks
0
Last push
Nov 19, 2026
License
MIT

JavaScriptai-agentscontext-engineeringgraph-raghydradbmcpopencypher

From the README

HydraScope Live Agent Context Layer (Skills, 64 MCP Tool Definitions, Resolved Entities, and Multi-Hop AST/ADR Lineage) Built on Self-Hosted HydraDB (v0.4.0) Launch Live Demo (https://hydrascope.krusch.dev) · Watch Loom Walkthrough (4m 45s) · Read Architecture Write-Up (krusch.dev) · Read Ontology Triad Paper (krusch.dev) Most agent stacks preload dozens of MCP tool schemas into every prompt window (12,000+ tokens before Turn 1) or bolt on a flat cosine vector store that retrieves deprecated v1 tools, misses mandatory post-check tools that share zero vocabulary with the user prompt, and repeats entity-lookup round-trips on every run. I built HydraScope on the open-source HydraDB (v0.4.0) graph engine (hydra-db/hydradb) as a live, self-sharpening context store for AI agents. HydraScope stores an agent's Skills, MCP Tool Definitions, Resolved Entities, and Code/ADR Lineage in HydraDB, traverses only the structural subgraph each task requires, and writes newly resolved entity aliases and co-executed tool paths back into HydraDB after every run. Architecture: How HydraDB Powers the Context Layer Why Plain Vector Stores and Tool Preloading Fail Here 1. Zero-Lexical-Overlap Tool & Code Dependencies: Refunding a disputed Stripe invoice (stripev2idempotentrefund) requires running double-entry cent conservation (ledgerverifycentconservation) and appending an HMAC receipt (auditappendsigned_receipt).…

Read the full README on GitHub →

The most-starred Data & Analytics servers in the index, with their live-check result.

ServerStarsLast pushLive check
PostHog41,013Nov 2026Needs sign-in
PostHog MCP Server40,870Nov 2026Needs sign-in
Agent-Native Analytics7,735Nov 2026Needs sign-in
TradingMCP5,320Nov 2026Needs sign-in
Jitsu5,138Nov 2026Needs sign-in

HydraScope MCP: questions people ask

Is HydraScope MCP a remote or a local MCP server?
According to its entry in the official MCP registry, HydraScope MCP ships as a local package (npm) that your client starts on your machine.
Is HydraScope MCP safe to use?
Looks healthy: HydraScope MCP is maintained, open source. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: On your machine; credentials: None declared. Serverdex check of Nov 21, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is HydraScope MCP still maintained?
Active: the repository's last commit 3 days ago. Last push Nov 19, 2026, 0 GitHub stars, MIT licence. Read from GitHub on Nov 19, 2026.
How do I add HydraScope MCP to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
  1. Krusch Context MCPPersistent working memory and SHA-256 span drift verification for AI coding agents in 5 MCP verbs.★ 83
  2. KruschStackLocal SQLite control plane for coding agents: persistent memory, Turn-0 grounding, and 2PC safety.★ 3
  3. G-Krusch Workspace MCPLocal-first Google Workspace MCP server with hybrid FTS5 Drive RAG, Docs, Calendar, and Gmail.
  4. Krusch Frontend MCPCanonical UI templates, WCAG color palettes, Tailwind CSS conversion, and responsive design MCP.
Browse all Data & Analytics →

Add the badge to your site

Show visitors that HydraScope MCP is listed here — it’s also the link we check for a free listing.

HydraScope MCP — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/dev-krusch-hydrascope?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="HydraScope MCP — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![HydraScope MCP — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/dev-krusch-hydrascope?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/dev-krusch-hydrascope) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/dev-krusch-hydrascope) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/dev-krusch-hydrascope)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/dev-krusch-hydrascope"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/dev-krusch-hydrascope"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/dev-krusch-hydrascope"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).