npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@levnikolaevich/hex-research-mcp

v0.2.1

Published

Markdown-first research hypothesis graph MCP server for goals, hypotheses, run manifests, task links, sources, and coherent goal metrics.

Readme

hex-research-mcp

Markdown-first MCP server for indexing research hypotheses, goals, tasks, sources, and benchmark run manifests into a SQLite research graph.

npm downloads license node

Install

claude mcp add -s user hex-research -- npx -y @levnikolaevich/hex-research-mcp

Local Use

npm --prefix mcp install
npm --prefix mcp --workspace @levnikolaevich/hex-research-mcp run build
node mcp/hex-research-mcp/server.mjs

The server indexes a target project root with this layout:

docs/hypotheses/*.md
docs/goals/*.md
docs/sources/lib.yaml
benchmark/runs/*/manifest.yaml

The SQLite index is written to:

.hex-skills/researchgraph/index.db

Tools

  • index_hypotheses: rebuild the SQLite index.
  • verify_index: validate frontmatter and manifests without rebuilding.
  • find_hypotheses: search hypotheses by status, goal, task state, source, priority, or claim.
  • inspect_hypothesis: inspect one hypothesis and its linked graph data.
  • find_evidence: search evidence entries and cited sources.
  • find_runs: search targeted and explicit comprehensive benchmark runs.
  • trace_lineage: trace hypothesis lineage and dependency edges.
  • analyze_topology: summarize node/edge counts and hubs.
  • audit_orphans: report orphan, stale, evidence, source, task, and goal-run gaps.
  • inspect_goal: inspect one goal and linked hypotheses.
  • trace_goal_tree: trace goal decomposition.
  • audit_goal_alignment: audit hypothesis-goal coverage, explicit comprehensive-run metrics, and coverage candidates.
  • analyze_progress: inspect changed research files and field-level frontmatter deltas from git diff.
  • analyze_proposed: check readiness gaps for one hypothesis.
  • export_canvas: export a JSON Canvas graph.
  • export_research_map: generate docs/research-map.md from canonical split files.

Validation and Sources

Goal metrics_current is derived during indexing from explicit comprehensive run manifests. Do not write metrics_current, children, or achievement_status in goal frontmatter; verify_index reports those as source drift.

Projects may deduplicate citations in docs/sources/lib.yaml:

sources:
  carver-2015-systematic-trading:
    type: book
    title: Systematic Trading
    isbn: "9780857194459"
    year: 2015

Hypotheses and goals can then cite by id:

sources:
  - id: carver-2015-systematic-trading
    pages: "12-14"

Use the validator in Git hooks or CI:

npx -y --package @levnikolaevich/hex-research-mcp hex-research-validate --strict --path .

Example .pre-commit-config.yaml:

repos:
  - repo: local
    hooks:
      - id: hex-research-validate
        name: hex research graph validation
        entry: npx -y --package @levnikolaevich/hex-research-mcp hex-research-validate --strict --path .
        language: system
        pass_filenames: false

Fixture Example

npm --prefix mcp --workspace @levnikolaevich/hex-research-mcp test
npm --prefix mcp --workspace @levnikolaevich/hex-research-mcp run evals
npm --prefix mcp --workspace @levnikolaevich/hex-research-mcp run benchmark
npm --prefix mcp --workspace @levnikolaevich/hex-research-mcp run docs:quality:check

The test fixture covers live, pending implementation, valid refine, refine gap, status-verdict drift, comprehensive runs, targeted runs, cited sources, and opaque runner_environment manifest metadata.

Quality Snapshot

Release readiness: Server MVP verified on deterministic fixtures with npm packaging enabled. btc-trader migration, Phase 7 pull-up, and skill packaging remain out of scope for this snapshot.

| Metric | Value | |---|---:| | MCP tools covered | 16/16 | | Eval scenarios | 16 | | Benchmark workflows | 5 | | Avg estimated benchmark savings | 78.2% |

Methodology: evals call every registered tool against test/fixtures/project with deterministic assertions and structuredContent/text mirror checks. Benchmark token counts are rough ceil(chars / 4) estimates, not production tokenizer measurements.

| Tool | Risk | Eval | Test source | |---|---|---|---| | index_hypotheses | high | verified | test/indexing.mjs | | verify_index | medium | verified | test/schema-contract.mjs | | find_hypotheses | low | verified | test/tools.mjs | | inspect_hypothesis | low | verified | test/tools.mjs | | find_evidence | low | verified | test/tools.mjs | | find_runs | low | verified | test/tools.mjs | | trace_lineage | medium | verified | test/tools.mjs | | analyze_topology | low | verified | evals/index.mjs | | audit_orphans | medium | verified | test/audit.mjs | | analyze_progress | low | verified | evals/index.mjs | | analyze_proposed | medium | verified | evals/index.mjs | | inspect_goal | low | verified | test/tools.mjs | | trace_goal_tree | medium | verified | test/tools.mjs | | audit_goal_alignment | medium | verified | test/audit.mjs | | export_canvas | high | verified | test/export.mjs | | export_research_map | high | verified | test/export.mjs |

Goal-Directed Workflow

  1. Run verify_index before changing research files.
  2. Run index_hypotheses after edits.
  3. Use audit_goal_alignment to find active goals without live hypotheses or comprehensive metrics.
  4. Use find_hypotheses and inspect_hypothesis for scoped execution.
  5. Use analyze_progress for field-level frontmatter deltas in current git diff.
  6. Use export_canvas or export_research_map with dry_run: true before writing generated graph artifacts.