MCP Observatory
github re-analysis due unconfirmed MCP

Driftya/code-meridian

github

Local graph memory for AI coding agents, giving MCP-compatible tools precise codebase context before they edit.

maintainer
Driftya
license
MIT
first seen
2026-06-10
last seen
2026-06-17
releases · 30d
12
short id
risk 32/100 · heuristic grade
B low
  • capability exposureinferred+35
  • trust mitigatorsmixed−3

inferredmixed

The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.

graded 12m ago · see ecosystem CVEs →

risk trajectory 4 movements
  • B · 34 → B · 32
  • C · 37 → B · 34
  • C · 40 → C · 37
  • C · 37 → C · 40
capability exposure grade factor +35
Inferred surface — each links to servers holding it:
vulnerabilities 0 CVEs

No known CVEs for this server.

tool safety all quiet

No tool-safety findings — heuristic detectors run on the compute-risk cadence; a finding appears when a tool trips a rule.

skills & danger signals github-tarball
prompt-surface shipped agent-instruction files + hidden-content / dangerous-code findings — quoted from the analyzed source

analyzed commit c12edb5 · analyzer v17 · 3d ago

skills & prompt files 3

embed badge readme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/github:Driftya/code-meridian/badge.svg)](https://mcpobservatory.com/servers/github:Driftya/code-meridian/security)

Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of Driftya.