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/theYahia/elma365-mcpWrote 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/theyahia/elma365-mcp/elma365-mcp)<a href="https://agentmods.dev/mcp/theyahia/elma365-mcp/elma365-mcp"><img src="https://agentmods.dev/badge/mcp/theyahia/elma365-mcp/elma365-mcp/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/theyahia/elma365-mcp/elma365-mcp"><img src="https://agentmods.dev/badge/mcp/theyahia/elma365-mcp/elma365-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
elma365-mcp 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 12d 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
{ "elma365-mcp": { "command": "npx", "args": [ "-y", "@theyahia/elma365-mcp" ], "env": { "ELMA365_DOMAIN": "" } } }
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.
- 12d ago First seen · 12 lines scan A 5a5dcfb54cf0
elma365-mcp is an MCP server published in the GitHub repository theYahia/elma365-mcp (1 stars, last pushed 10d ago), 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-31.
Other mcp servers, from other repositories
tilda-mcp
MCP server for Tilda API — projects, pages. 3 tools. Runs locally from the @theyahia/tilda-mcp npm package. Needs 1 environment variable to run.
planfix-mcp
MCP server for Planfix API — tasks, contacts. 3 tools. Runs locally from the @theyahia/planfix-mcp npm package. Needs 1 environment variable to run.
yookassa-mcp
MCP server for YooKassa payment API — payments, refunds, receipts (54-FZ). 10 tools. First MCP for. Runs locally from the @theyahia/yookassa-mcp npm package. Needs 1 environment variable to run.
megaplan-mcp
MCP server for Megaplan — tasks, deals management via API v3. Runs locally from the @theyahia/megaplan-mcp npm package. Needs 1 environment variable to run.
kaiten-mcp
MCP server for Kaiten API — cards, boards. 3 tools. Runs locally from the @theyahia/kaiten-mcp npm package. Needs 1 environment variable to run.
salutespeech-mcp
MCP server for Sber SaluteSpeech API — speech recognition and synthesis. Runs locally from the @theyahia/salutespeech-mcp npm package. Needs 1 environment variable to run.