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/JOYLINK-LTD/lacuna-toolkitWrote 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/joylink-ltd/lacuna-toolkit/mcp-lacuna-mcp)<a href="https://agentmods.dev/mcp/joylink-ltd/lacuna-toolkit/mcp-lacuna-mcp"><img src="https://agentmods.dev/badge/mcp/joylink-ltd/lacuna-toolkit/mcp-lacuna-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/joylink-ltd/lacuna-toolkit/mcp-lacuna-mcp"><img src="https://agentmods.dev/badge/mcp/joylink-ltd/lacuna-toolkit/mcp-lacuna-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lacuna-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 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
{
"lacuna-mcp": {
"command": "npx",
"args": [
"-y",
"lacuna-mcp"
],
"env": {
"LACUNA_API_KEY": "",
"LACUNA_BASE_URL": ""
}
}
}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 · 13 lines scan A 536cf3a306e6
lacuna-mcp is an MCP server published in the GitHub repository JOYLINK-LTD/lacuna-toolkit (4 stars, last pushed 1mo 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
prompt-to-asset
Generate app icons, favicons, OG images, and logos by routing across 30+ image models. Runs locally from the prompt-to-asset npm package.
tiktok-agent-publisher
Local-first TikTok Content Posting API for AI agents: OAuth checks, dry-run and live uploads. Runs locally from the tiktok-agent-publisher npm package. Needs 3 environment variables to run.
photo-s
A locally run toolkit for processing batches of photos. It covers tasks such as compression, format conversion, color adjustment, metadata handling, RAW files, duplicate detection, and photo selection, through command-line, graphical, REST, and MCP interfaces.
ytdl-rmcp
yt-dlp search, download, metadata, delivery, and Plex workflows over MCP and CLI. Runs locally from the @dinglebear/rytdl npm package. Needs 28 environment variables to run.
cubelife
Give AI agents a persistent pixel-art character reflecting their state in real time. Runs locally from the cubelife npm package. Needs 2 environment variables to run.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.