Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/elisymlabs/elisymWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/elisymlabs/elisym/mcp-elisym)<a href="https://agentmods.dev/mcp/elisymlabs/elisym/mcp-elisym"><img src="https://agentmods.dev/badge/mcp/elisymlabs/elisym/mcp-elisym/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/elisymlabs/elisym/mcp-elisym"><img src="https://agentmods.dev/badge/mcp/elisymlabs/elisym/mcp-elisym.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
elisym scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"elisym": {
"command": "npx",
"args": [
"-y",
"@elisym/mcp"
],
"env": {
"ELISYM_AGENT": "",
"ELISYM_NOSTR_SECRET": "",
"ELISYM_AGENT_NAME": "",
"ELISYM_NETWORK": "",
"ELISYM_PASSPHRASE": "",
"ELISYM_ALLOW_WITHDRAWAL": "",
"ELISYM_ALLOW_AGENT_SWITCH": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 18 lines scan A 57fe6694699d
elisym is an MCP server published in the GitHub repository elisymlabs/elisym (15 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
cinderwright-api
Cross-protocol agent payments hub. x402, MPP, L402/Lightning. 1551 services indexed. Runs locally from the cinderwright-mcp-server npm package.
solfleet
Agent-safe fleet management for independent Solana validators and RPC nodes. Runs locally from the solfleet Python package.
vtimestamp-write
MCP server for creating vtimestamp proofs on the Verus blockchain via a local or remote daemon. Runs locally from the vtimestamp-mcp-write npm package. Needs 4 environment variables to run.
vtimestamp
MCP server for verifying and querying vtimestamp proofs on the Verus blockchain. Runs locally from the vtimestamp-mcp npm package.
mint-mcp
Trust stack for AI agents: identity, attest, verify, rate, recommend, discover — on Solana. Remote server at mint-mcp-production.up.railway.app.
strategy-lab
Stress-test lowcap, perp and LP strategies. Returns the full distribution and a reproduction seed. Remote server at kellyruns.xyz.