@hivelore/mcp

MCPcommunity
v0.53.1UnknownApache-2.0Updated 3mo agonpmGitHub

Hivelore MCP server - policy-aware briefing and memory tools for coding-agent harnesses

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
3kDownloads/wk
3mo agoLast update
Package
AuthorUnknown
LicenseApache-2.0
Version0.53.1
Sourcenpm+mcp-registry
npm@hivelore/mcp
GitHubDoucs91/hivelore
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface33 tools · 1 privileged
Security scan✓ Cleanv0.65.0 · todayHow well does this scan work?
EvalsNone
IndexedJul 9, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

33 tools · 1 privileged
Statically extracted from the published packagev0.65.0 · 7h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

mem_saveNo description published

This tool published no description. Forge does not invent one.

mem_suggest_topicNo description published

This tool published no description. Forge does not invent one.

mem_triedNo description published

This tool published no description. Forge does not invent one.

propose_sensorNo description published

This tool published no description. Forge does not invent one.

scaffold_testNo description published

This tool published no description. Forge does not invent one.

report_frictionNo description published

This tool published no description. Forge does not invent one.

ingest_findingsNo description published

This tool published no description. Forge does not invent one.

mem_session_endNo description published

This tool published no description. Forge does not invent one.

get_briefingNo description published

This tool published no description. Forge does not invent one.

mem_searchNo description published

This tool published no description. Forge does not invent one.

mem_timelineNo description published

This tool published no description. Forge does not invent one.

mem_for_filesNo description published

This tool published no description. Forge does not invent one.

mem_getNo description published

This tool published no description. Forge does not invent one.

mem_listNo description published

This tool published no description. Forge does not invent one.

get_project_contextNo description published

This tool published no description. Forge does not invent one.

bootstrap_project_saveNo description published

This tool published no description. Forge does not invent one.

code_mapNo description published

This tool published no description. Forge does not invent one.

mem_resolve_projectNo description published

This tool published no description. Forge does not invent one.

mem_updateNo description published

This tool published no description. Forge does not invent one.

mem_verifyNo description published

This tool published no description. Forge does not invent one.

mem_approveNo description published

This tool published no description. Forge does not invent one.

mem_rejectNo description published

This tool published no description. Forge does not invent one.

mem_feedbackNo description published

This tool published no description. Forge does not invent one.

mem_pendingNo description published

This tool published no description. Forge does not invent one.

mem_deleteprivilegedNo description published

This tool published no description. Forge does not invent one.

get_recapNo description published

This tool published no description. Forge does not invent one.

mem_relevant_toNo description published

This tool published no description. Forge does not invent one.

code_searchNo description published

This tool published no description. Forge does not invent one.

anti_patterns_checkNo description published

This tool published no description. Forge does not invent one.

mem_distillNo description published

This tool published no description. Forge does not invent one.

mem_conflict_candidatesNo description published

This tool published no description. Forge does not invent one.

pre_commit_checkNo description published

This tool published no description. Forge does not invent one.

mem_diffNo description published

This tool published no description. Forge does not invent one.

0 of 33 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Hivelore MCP server - policy-aware briefing and memory tools for coding-agent harnesses

Keywords
aienforcementpolicycontextbreadcrumbsmemorymcphaivemodel-context-protocolagentteamharnessharness-engineering
Alternatives
Comparing tool surfaces…

Tools exposed

33 tools · 1 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-12 — observed resolution, not a publisher declaration.

60 packages resolved · 3 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

67 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+55 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in memory & knowledge graphs