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/Bortor/turing-test-gameWrote 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/bortor/turing-test-game/turing-test-game)<a href="https://agentmods.dev/mcp/bortor/turing-test-game/turing-test-game"><img src="https://agentmods.dev/badge/mcp/bortor/turing-test-game/turing-test-game/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/bortor/turing-test-game/turing-test-game"><img src="https://agentmods.dev/badge/mcp/bortor/turing-test-game/turing-test-game.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
turing-test-game 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
{ "turing-test-game": { "command": "uvx", "args": [ "turing-test-game" ] } }
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 · 8 lines scan A 482c9db710c5
turing-test-game is an MCP server published in the GitHub repository Bortor/turing-test-game (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
loot-agent-mcp
MCP server "loot-agent-mcp" as configured in D-Kek/loot-agent-mcp. Runs locally from the loot-agent-mcp npm package. Needs 4 environment variables to run.
roblox-bridge-agent
MCP server "roblox-bridge-agent" as configured in evonar543/robloxbridgeagent. Runs locally from the roblox-bridge-agent npm package.
wwise-mcp
MCP server "wwise-mcp" as configured in linnn-nb/wwise-mcp. Runs locally from the wwise-mcp Python package.
raven-roblox-mcp
MCP server "raven-roblox-mcp" as configured in valrinx/raven-roblox-mcp. Runs locally from the raven-roblox-mcp npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.