GENOME MCP Server (NORTHTEKDevs/genome) is an MCP server listed on the M8ven Trust Index. It scores 67 out of 100, grade C. It declares 4 tools. No publisher has claimed this listing.

C
Limited view
67/100

GENOME MCP Server

A local, offline memory server for AI agents that stores and retrieves memories without LLM calls, enabling persistent cross-session memory with bi-temporal querying and auditable records.

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

NORTHTEKDevs

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 4 credentials: OPENAI_API_KEY, ANTHROPIC_API_KEY, OPENROUTER_API_KEY, GENOME_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretOPENAI_API_KEYdrop-in swap. To use OpenAI embeddings instead (set ):
🔐 secretANTHROPIC_API_KEY
configOR_RESP
configOR_JUDGE
🔐 secretOPENROUTER_API_KEY
configOPENAI_BASE_URL
configGENOME_MCP_DBenv var). Run standalone with genome-mcp or python -m genome.mcp.server.
configGENOME_HOST
configGENOME_PORT
configGENOME_STORAGE
🔐 secretGENOME_API_KEY
configGENOME_CACHE_SIZE
configGENOME_CORS_ORIGINS
configGENOME_MAX_REQUEST_BYTES
configGENOME_LAZY_INIT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

4/4 tools missing one or more hints — remember (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); recall (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); forget (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +1 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool handlers catch errors

Only 0/4 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

Only 0/4 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Domain consistency

npm scope @frostbyte doesn't match GitHub owner northtekdevs

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/northtekdevs/genome)](https://m8ven.ai/mcp/northtekdevs/genome)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: f1e5d43ee32d59307a0ee2d94fa7a2077dfdb99c
code hash: 711e7f9efb4f747030ddb90b7812adeecaf31cca9ed0273cb96fef818ee56afa
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client