palinode (phasespace-labs/palinode) is an MCP server listed on the M8ven Trust Index. It scores 71 out of 100, grade C. It declares 30 tools. No publisher has claimed this listing.

C
Limited view
71/100

palinode

The memory substrate for AI agents and developer tools. Git-versioned, file-native, MCP-first.

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

phasespace-labs

Source: Glama · also listed on github_repo_search

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 2 credentials: PALINODE_API_TOKEN, GEMINI_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.
configPALINODE_ALLOW_FRESH_DB
configPALINODE_DIRmemory_dir stays commented out in the copied config → it inherits below
configPALINODE_SOURCE
configPALINODE_RATE_LIMIT_SEARCH
configPALINODE_RATE_LIMIT_WRITE
configPALINODE_RATE_LIMIT_MAX_KEYS
configPALINODE_MAX_REQUEST_BYTESPOST /save Create a typed memory file. Schema: {content, type, slug?, entities?, title?}. Body cap 5 MB (override via ).
configPALINODE_API_HOST
configPALINODE_API_BIND_INTENT
configPALINODE_CONFIG
configEDITOR
configPALINODE_PROJECT
configMCP_CLIENT_NAME
configCLAUDE_CODE
🔐 secretPALINODE_API_TOKENWhen exposing the API beyond loopback, set — see [SECURITY.md](SECURITY.md#api-authentication) for the bearer-token auth model and the public-bind startup gate.
configPALINODE_API_TOKEN_FILE
configOLLAMA_URL
configEMBEDDING_MODEL
configPALINODE_API_PORT
configPALINODE_MCP_SURFACE
configPALINODE_ORG
configPALINODE_MEMBER
configPALINODE_HARNESS
configPALINODE_AGENT
configPALINODE_DESCRIBE_TIMEOUT_SECONDS
🔐 secretGEMINI_API_KEY
configPALINODE_INSTRUMENTATION_DISABLED
configSSH_CONNECTION
configPALINODE_MCP_BIND_INTENT
configPALINODE_MCP_HTTP_HOST
configPALINODE_MCP_SSE_HOST
configPALINODE_MCP_HTTP_PORT
configPALINODE_MCP_SSE_PORT
configPALINODE_MCP_LOG_LEVEL
configPALINODE_MEM0_COLLECTIONS
// quality suggestions

Tool annotations

26/30 tools have annotations

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

All four hints declared on every tool

4/30 tools missing one or more hints — palinode_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); palinode_save (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); palinode_trigger (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 test coverage

Only 2/30 tools referenced in tests (7%)

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

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 3 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/phasespace-labs/palinode)](https://m8ven.ai/mcp/phasespace-labs/palinode)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 2332f43f05c21657332ea09b3dd50348b615004e
code hash: cafd7c5bff680a3ad077b800de5b28195b815e8ad3e21e35ef2b64a1c3fdf0f5
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