cama (LoriensLibrary/cama) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 86 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

cama

Circular Associative Memory Architecture — an emotionally-indexed, three-layer memory system for human-AI interaction continuity

→ LoriensLibrary/cama· listed on github_repo_search

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

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

LoriensLibrary

Source: 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 →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

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
🚨
Secret credentials may flow to a network call
2 flows detected: EMBEDDING_API_KEY, AELEN_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 7 credentials: CAMA_HIVE_MCP_SECRET, EMBEDDING_API_KEY, CAMA_HTTP_SECRET, ANTHROPIC_API_KEY, CAMA_CONSENT_SECRET, CAMA_CONSENT_APPROVER_SECRET, AELEN_TOKEN
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.
configCAMA_HIVE_IDENTITY
🔐 secretCAMA_HIVE_MCP_SECRET
configCAMA_HIVE_MCP_PORT
configCAMA_HIVE_MCP_HOST
configCAMA_HIVE_MCP_TRANSPORT
configCAMA_LOG_LEVEL
configLOG_LEVEL
configCAMA_DB_PATH
configCAMA_RING_SIZE
🔐 secretEMBEDDING_API_KEY
configEMBEDDING_MODEL
configEMBEDDING_BASE_URL
configEMBEDDING_HEADERS_JSON
configEMBEDDING_PROVIDER
🔐 secretCAMA_HTTP_SECRET
configCAMA_HOST
configCAMA_TRANSPORT
configCAMA_PORT
configCAMA_BRIDGE_WRITE_ALLOWLIST
configCAMA_PERSONA_NAME
configCAMA_BOOT_SUMMARY
configCAMA_EXEC_MODE
configCAMA_REPO_ROOT
🔐 secretANTHROPIC_API_KEY
🔐 secretCAMA_CONSENT_SECRET
🔐 secretCAMA_CONSENT_APPROVER_SECRET
configCAMA_MODEL
configCAMA_EFFORT
configCAMA_PARTICIPANT_ID
configCAMA_EMBEDDING_CACHE
configCAMA_DASHBOARD_PORT
configCAMA_DASHBOARD_HOST
configCAMA_API_PORT
configCAMA_API_HOST
configCAMA_TOKEN_AELEN
configCAMA_TOKEN_LORIEN
configCAMA_TOKEN_EMBER
configCAMA_TOKEN_AETHON
configCAMA_HIVE_STRICT_AUTH
configCAMA_HIVE_CORS_ORIGINS
configCAMA_HIVE_K
configCAMA_THREAD_HOME
configCAMA_BRAIN_LOG
configCAMA_INSIGHT_LOG
configCAMA_SELF_LOG
configCAMA_HIVE_API_URL
🔐 secretAELEN_TOKEN
configCAMA_REPORT_DIR
configCAMA_SLEEP_LOG
configCAMA_EMBEDDING_PROVIDER
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

70/86 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

20/86 tools missing one or more hints — cama_isthisme_check (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); cama_isthisme_correct (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); cama_isthisme_stats (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +17 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

38/86 tools referenced in tests (44%)

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

Secrets stay with their owner

2 secrets sent to a request target we could not resolve (EMBEDDING_API_KEY → dynamic, AELEN_TOKEN → dynamic) — often a configured endpoint, not necessarily third-party

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Secrets not written to files

1 secret value written to files

Avoid persisting secrets to disk. Keep them in memory or your secret manager.

Secrets not logged

2 secret values sent to print

Redact or omit secret values from log output.

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 6 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/lorienslibrary/cama)](https://m8ven.ai/mcp/lorienslibrary/cama)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: eb3d6678c9c005d05bf793eed9c3ce51245f939b
code hash: c1c7317adb28cb723eeba898373c47b1bb071a4d674067f9793caf7e7479950e
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