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/dcode-co/logi-pluginsWrote 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/dcode-co/logi-plugins/logi-approval-logi-approval)<a href="https://agentmods.dev/mcp/dcode-co/logi-plugins/logi-approval-logi-approval"><img src="https://agentmods.dev/badge/mcp/dcode-co/logi-plugins/logi-approval-logi-approval/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/dcode-co/logi-plugins/logi-approval-logi-approval"><img src="https://agentmods.dev/badge/mcp/dcode-co/logi-plugins/logi-approval-logi-approval.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
logi-approval 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 2mo 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
{
"logi-approval": {
"command": "npx",
"args": [
"-y",
"@logi-auth/mcp-approval"
],
"env": {
"LOGI_AGENT_TOKEN": "${LOGI_AGENT_TOKEN}",
"LOGI_AGENT_PRIVATE_KEY": "${LOGI_AGENT_PRIVATE_KEY}",
"LOGI_AGENT_PUBLIC_ID": "${LOGI_AGENT_PUBLIC_ID}",
"LOGI_API_URL": "https://api.1pass.dev"
}
}
}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.
- 2mo ago First seen · 15 lines scan A a3318fdf3a67
logi-approval is an MCP server published in the GitHub repository dcode-co/logi-plugins (0 stars, last pushed 27d 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.
logi-approval compared with mcp servers from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| logi-approvaldcode-co/logi-plugins | MCP server | 0 | 27d ago | MIT | A | — | Claude Code |
| docs-langchainlangchain-ai/langchain | MCP server | 149k | today | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| component-explorermicrosoft/vscode | MCP server | 195k | today | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| codex_message_boardopenai/codex | MCP server | 134k | today | Apache-2.0 | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| reference-langchainlangchain-ai/langchain | MCP server | 149k | today | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| playwright-testmicrosoft/playwright | MCP server | 100k | yesterday | Apache-2.0 | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| reamorluto/rea | MCP server | 439k | yesterday | MIT | A | — | Claude Code |