MCP.Market

Hivelore MCP server

by Doucs91·io.github.Doucs91/hivelore·v0.53.1·3 stars

Deterministic gate: blocks any commit whose diff reintroduces a documented team mistake.

A92/100grade A
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

3 stars368 downloads/wk

Reviews

Write one

Nobody has reviewed Hivelore yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Hivelore tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan4 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 4 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Hivelore compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 95% of 48,255 servers
GitHub stars
3
more than 80% of 28,688 servers
Downloads a week
368
more than 84% of 12,191 servers with a package

Install Hivelore in Claude Code, Cursor or VS Code

Runs npx -y @hivelore/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add hivelore -- npx -y @hivelore/mcp
Add to Cursor

What the publisher says

From the Hivelore repository's README, as published. We do not edit it. Read it on GitHub

Hivelore

The deterministic policy gate for agent-written code — it refuses the commit that repeats a mistake your team already paid for. A repo-native context policy for coding-agent harnesses; the rules live as team memory. Formerly published as hAIve (@hiveai/*).

Hivelore is the enforcement layer inside an AI coding-agent harness. It briefs agents with the team's non-obvious knowledge before they act, then turns each hard-won lesson into a deterministic gate — in MCP, Git hooks, and CI — that blocks the change about to repeat it. Same diff, same verdict, on every machine. Memory is the substrate; the gate is the product.

A capable model already knows generic best practice. What it cannot guess is your team's arbitrary, repo-specific knowledge: that public ids are id + 100000 prefixed AC-, that the status field must be "OK"/"KO", that you never edit an applied migration. Left to itself, a confident agent invents a plausible answer - clean, tested, green, and wrong by policy. Hivelore carries that unguessable knowledge into the task and blocks the change that's about to violate it.

Hivelore's job is not to replace tests, linters, or observability. It makes the repo-specific knowledge those tools cannot infer available, auditable, and enforceable.

Capture a mistake → attach a validated guard → the commit that repeats it is refused. Same diff, same verdict, on every machine and in CI. Reproduce it in 60 seconds ↓

The problem

AI coding agents are powerful, but they often act with incomplete repo context. Compaction, parallel sessions, agent switches, and stale advisory docs all create the same failure mode: the agent changes code without carrying the team's current decisions into the work.

Most teams work around this with instructions and hope:

  • "Please read our architecture decisions first."
  • "Don't repeat the migration mistake from last sprint."
  • "Remember to capture what you learned."
  • "Don't merge code that invalidates a team decision."

Those rules are easy to skip. Hivelore turns them into repo-native context policy.

How it works

AI agent ──▶ Hivelore briefing ──▶ code change ──▶ Hivelore policy gate ──▶ merge
                  ▲                                       │
                  └── context breadcrumbs · decisions · gotchas · anchors

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Hivelore: common questions

Is Hivelore MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Hivelore safety report
How do I install Hivelore?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Hivelore need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Hivelore maintained?
The last commit was 44 days ago (2026-09-21). The latest release is v0.53.1.
How does Hivelore compare with other MCP servers?
safety score 92/100 (higher than 95% of 48,255 servers); github stars 3 (more than 80% of 28,688 servers); downloads a week 368 (more than 84% of 12,191 servers with a package). Full comparison.