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)<a href="https://agentmods.dev/mcp/theyahia/elma365-mcp/elma365"><img src="https://agentmods.dev/badge/mcp/theyahia/elma365-mcp/elma365/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"><img src="https://agentmods.dev/badge/mcp/theyahia/elma365-mcp/elma365.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
elma365 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 11d 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.
This is a copy
100% identical to elma365 — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"elma365": {
"command": "npx",
"args": [
"-y",
"@theyahia/elma365-mcp"
],
"env": {
"ELMA365_DOMAIN": "",
"ELMA365_TOKEN": ""
}
}
}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.
- 11d ago First seen · 13 lines scan A b98171ea9cf7
elma365 is an MCP server published in the GitHub repository theYahia/elma365-mcp (1 stars, last pushed 9d 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. It is 100% identical to elma365, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
tilda
MCP server for Tilda — website builder, page management (Russia). Runs locally from the @theyahia/tilda-mcp npm package. Needs 2 environment variables to run.
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.
moysklad
MCP server for MoySklad — warehouse, inventory, orders, reports (Russia). Runs locally from the @theyahia/moysklad-mcp npm package. Needs 1 environment variable to run.
yandex-direct
MCP server for Yandex Direct — 20 tools: PPC campaigns, ad groups, ads, keywords, bids, negative keywords, statistics, balance (Russia). Rubles I/O, sandbox support. Runs locally from the @theyahia/yandex-direct-mcp npm package. Needs 1 environment variable to run.
yandex-direct-mcp
MCP server for Yandex Direct — PPC campaigns, ads, keywords, statistics (Russia). Runs locally from the @theyahia/yandex-direct-mcp npm package.
planfix
MCP server for Planfix — tasks, contacts, project management (Russia). Runs locally from the @theyahia/planfix-mcp npm package. Needs 2 environment variables to run.