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/melaya-labs/melaya-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/melaya-labs/melaya-mcp/melaya)<a href="https://agentmods.dev/mcp/melaya-labs/melaya-mcp/melaya"><img src="https://agentmods.dev/badge/mcp/melaya-labs/melaya-mcp/melaya/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/melaya-labs/melaya-mcp/melaya"><img src="https://agentmods.dev/badge/mcp/melaya-labs/melaya-mcp/melaya.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
melaya 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
{
"melaya": {
"type": "http",
"url": "https://api.melaya.org/mcp"
}
}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 · 6 lines scan A b52ec4d402e3
melaya is an MCP server published in the GitHub repository melaya-labs/melaya-mcp (0 stars, last pushed 3d ago), licensed Apache-2.0. 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
helmdeck
Self-hosted MCP server: sandboxed browser, desktop, vision, code-edit packs for any agent. Runs locally from the @helmdeck/mcp-bridge npm package. Needs 2 environment variables to run.
ainative-browser-mcp
AI-powered browser automation MCP — 6 tools for web interaction, extraction, and validation. Runs locally from the @ainative/browser-mcp npm package.
devtools-lens-mcp
Give your AI agent Chrome DevTools: an MCP server for debugging Chromium applications. Runs locally from the devtools-lens-mcp npm package.
blop-mcp
MCP-native release confidence control plane for web apps. Runs locally from the blop-mcp Python package.
alethia
MIT-licensed MCP bridge to the Alethia runtime — the patent-pending zero-IPC E2E test runtime for AI agents. 2-5x faster than Playwright MCP. Signed evidence packs, EA1 fail-closed safety gate, WCAG + NIST 800-53 audits built in. Local-first, zero telemet. Runs locally from the @vitronai/alethia npm package.
camofox-browser-mcp
MCP server for driving a local camofox-browser instance. Runs locally from the camofox-browser-mcp npm package. Needs 6 environment variables to run.