C
Emerging
74/100
2 days ago

orchestrator

LSC orchestrator: Crush+Ollama, MCP, OpenCode, deployment

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

AkashicRecords

Source: github_code

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.
🔐
You'll be asked for 5 credentials: MCP_API_KEY, ROCKET_API_KEY, ROCKET_PASSWORD, FALCON1_API_KEY, EVENT_BUS_AUTH_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.
configMCP_PORT
configMCP_HOST
🔐 secretMCP_API_KEY
configROCKET_URL
🔐 secretROCKET_API_KEY
configROCKET_USER
🔐 secretROCKET_PASSWORD
configFALCON1_HOST
configFALCON1_PORT
🔐 secretFALCON1_API_KEY
configWHISPER_URL
configTRANSLATION_URL
configTTS_URL
configJITSI_URL
configOBJECTBOX_PATH
configOBJECTBOX_PORT
configTAILSCALE_ENABLED
configTAILSCALE_HOSTNAME
configEVENT_BUS_ENABLED
configEVENT_BUS_HOST
configEVENT_BUS_PORT
configEVENT_BUS_NAMESPACE
🔐 secretEVENT_BUS_AUTH_TOKEN
configEVENT_BUS_SOURCE_NODE
configBRIDGE_ENABLED
configBRIDGE_TARGET_HOST
configBRIDGE_TARGET_PORT
configSYNC_INTERVAL_SECONDS
configSYNC_MAX_RETRIES
configSYNC_BATCH_SIZE
configOFFLINE_QUEUE_MAX_SIZE
configLOG_LEVEL
configLOG_FORMAT
configVOICE_LANG
configVOICE_CLONE
configLSC_CRUSH_MAX_PROFILES
// 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

19/19 tools missing one or more hints — send_message (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_messages (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_channel (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +16 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

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/akashicrecords-orchestrator-eaw8od)](https://m8ven.ai/mcp/akashicrecords-orchestrator-eaw8od)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: aad46aa6eaf01506bcde5bb27289c2a88b3a8d3f
code hash: acf5f4508bf873c92b5207399ab814f071a32ccb30b23deea060cca0656d64b4
verified: 8/19/2026, 1:24:23 PM
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