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/WWmcpWrote 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/wwmcp/elma365-elma365)<a href="https://agentmods.dev/mcp/theyahia/wwmcp/elma365-elma365"><img src="https://agentmods.dev/badge/mcp/theyahia/wwmcp/elma365-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/wwmcp/elma365-elma365"><img src="https://agentmods.dev/badge/mcp/theyahia/wwmcp/elma365-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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- elma365 — 100% identical, 0 lines differ
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.
- 12d ago First seen · 13 lines scan A b98171ea9cf7
elma365 is an MCP server published in the GitHub repository theYahia/WWmcp (29 stars, last pushed 4d 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-30.
Other mcp servers, from other repositories
prism-mcp
Persistent session memory for AI coding agents that never leaves your machine — including the on-device model that reasons over it. Restores your prior decisions, open TODOs, and changed files across sessions; adds associative recall of related past work. Runs locally from the prism-mcp-server npm package. Needs 1…
better-godot-mcp
MCP server for Godot Engine 4.x with 17 tools for scenes, scripts, and shaders. Runs locally from the @n24q02m/better-godot-mcp npm package. Needs 2 environment variables to run.
google-ai-search-mcp
Google AI search and documentation tools for MCP clients using Vertex AI or the Gemini API. Runs locally from the google-ai-search-mcp npm package. Needs 4 environment variables to run.
mcp-server
MCP server for Zooza — class scheduling, attendance, and booking for activity businesses. Remote server at mcp.zooza.app.
zooza
MCP server "zooza", hosted remotely at localhost, as configured in zooza-dev/zooza-mcp-server.
yandex-direct-mcp
MCP server for Yandex Direct — PPC campaigns, ads, keywords, statistics (Russia). Runs locally from the @theyahia/yandex-direct-mcp npm package.