Graphiti MCP Server (gifflet/graphiti-mcp-server) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

C
Limited view
71/100
1 month ago

Graphiti MCP Server

A knowledge graph server for AI agents, built with Neo4j and integrated with Model Context Protocol, enabling dynamic graph management and semantic search.

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

gifflet

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

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// 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 3 credentials: OPENAI_API_KEY, AZURE_OPENAI_EMBEDDING_API_KEY, NEO4J_PASSWORD
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.
configSEMAPHORE_LIMIT❌ 10 Concurrent operation limit for LLM calls
configMODEL_NAMEgpt-4.1-mini
configSMALL_MODEL_NAME❌ gpt-4.1-nano Small LLM model for lighter tasks
configAZURE_OPENAI_ENDPOINT✅ - Azure OpenAI endpoint URL
configAZURE_OPENAI_API_VERSION✅ - Azure OpenAI API version
configAZURE_OPENAI_DEPLOYMENT_NAME✅ - Azure OpenAI deployment name
configAZURE_OPENAI_USE_MANAGED_IDENTITY❌ false Use Azure managed identity for auth
🔐 secretOPENAI_API_KEYyour_openai_api_key_here
configLLM_TEMPERATURE❌ 0.0 LLM temperature (0.0-2.0)
configEMBEDDER_MODEL_NAME❌ text-embedding-3-small Embedding model
configAZURE_OPENAI_EMBEDDING_ENDPOINT❌ - Separate endpoint for embeddings
configAZURE_OPENAI_EMBEDDING_API_VERSION❌ - API version for embeddings
🔐 secretAZURE_OPENAI_EMBEDDING_API_KEY❌ - Separate API key for embeddings
configNEO4J_URIbolt://neo4j:7687
configNEO4J_USER❌ neo4j Neo4j username
🔐 secretNEO4J_PASSWORD❌ demodemo Neo4j password
configMCP_SERVER_HOST❌ - MCP server host binding
// 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

8/8 tools missing one or more hints — add_memory (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_memory_nodes (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_memory_facts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +5 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 inputs are validated

7/8 tool handlers declare input schemas (88%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tests exist

No test files found

Add tests that exercise each declared tool.

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 4 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/gifflet-graphiti-mcp-server-2fo1d2)](https://m8ven.ai/mcp/gifflet-graphiti-mcp-server-2fo1d2)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 008db7cdf87f769d9b696386def340a048177551
code hash: a84e1c773b09c0f20d79d67d776a498ff4314c1f917a1a7c2fe824012f897f15
verified: 8/7/2026, 2:29:22 AM
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