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

Back to MCP Trust IndexM8ven
C
Emerging
74/100
1 month ago

elisym

Lets AI assistants (Claude, Cursor, Windsurf) discover, hire, and pay other AI agents over the elisym network - decentralized agent marketplace on Nostr with on-chain Solana payments. Customer-mode tools for agent discovery, job submission, wallet management, and identity.

→ elisymlabs/elisym· listed on glama

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

elisymlabs

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 →

⚡ Connect GitHub for Live Monitored

Install from

Glama

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 4 credentials: DELEGATE_SECRET, ELISYM_NOSTR_SECRET, OWNER_SECRET, GITHUB_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.
configADMIN_KEYPAIR_PATH
🔐 secretDELEGATE_SECRET
configDELEGATION_TEST_FEE_BPS
configELISYM_AGENT
configELISYM_AGENT_NAME
configELISYM_ALLOW_AGENT_SWITCH
configELISYM_ALLOW_DELEGATION
configELISYM_ALLOW_WITHDRAWAL
configELISYM_DEBUG
configELISYM_NETWORK
configELISYM_NET_DIAG
🔐 secretELISYM_NOSTR_SECRET
configELISYM_PASSPHRASE
configINITIAL_ADMIN
configINITIAL_FEE_BPS
configINITIAL_TREASURY
configKEYPAIR
configLOG_LEVEL
🔐 secretOWNER_SECRET
configPAYEE_ADDRESS
configPROGRAM_ID
configRPC_URL
configSOLANA_RPC_URL
configSOLANA_WS_URL
🔐 secretGITHUB_TOKEN
// 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

34/34 tools missing one or more hints — search_agents (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); verify_agent_identities (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_capabilities (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +31 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 0/34 tools referenced in tests (0%)

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

Shell command execution

8 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Secrets not logged

9 secret values sent to console.log

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 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/elisymlabs/elisym)](https://m8ven.ai/mcp/elisymlabs/elisym)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 41cba72b2d6bb3ec45038e6817477fa45a804416
code hash: 218223fbcd176531803c0b9c3448c4a64100458ad70923b48e6d92bad6a1f5f2
verified: 8/6/2026, 2:55:59 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