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/turnale-app/turnaleWrote 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/turnale-app/turnale/turnale)<a href="https://agentmods.dev/mcp/turnale-app/turnale/turnale"><img src="https://agentmods.dev/badge/mcp/turnale-app/turnale/turnale/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/turnale-app/turnale/turnale"><img src="https://agentmods.dev/badge/mcp/turnale-app/turnale/turnale.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
turnale 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 1mo 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
{ "turnale": { "url": "https://mcp.turnale.app", "type": "streamable-http" } }
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.
- 1mo ago First seen · 6 lines scan A c72fbb4f15f4
turnale is an MCP server published in the GitHub repository turnale-app/turnale (0 stars, last pushed 2mo 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
connectwise-manage-mcp
MCP server "connectwise-manage-mcp" as configured in WYRE-AI/connectwise-manage-mcp. Runs in Docker (ghcr.io/wyre-ai/connectwise-manage-mcp:v1.9.0). Needs 8 environment variables to run.
connectmachine
Manage your ConnectMachine contacts, networks, events, and digital business cards. Remote server at mcp.connectmachine.ai.
microsoft-planner-mcp
MCP server "microsoft-planner-mcp", hosted remotely at localhost, as configured in aixolotl/microsoft-planner-mcp.
tokenrip
MCP server "tokenrip", hosted remotely at api.tokenrip.com, as configured in tokenrip/cli.
openproject-mcp-server
MCP server for OpenProject: 89 tools for work packages, attachments, git activity, time tracking, meetings and reporting over the API v3. Runs locally from the openproject-mcp-server Python package. Needs 7 environment variables to run.
alexandria-mcp
Search, read, and cite across 152 libraries: 11 tools, 3 prompts, and a full-text resource. Runs locally from the @the-40-thieves/alexandria-mcp npm package. Needs 11 environment variables to run.