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/polygraphso/litmusWrote 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/polygraphso/litmus/polygraph-polygraph-litmus)<a href="https://agentmods.dev/mcp/polygraphso/litmus/polygraph-polygraph-litmus"><img src="https://agentmods.dev/badge/mcp/polygraphso/litmus/polygraph-polygraph-litmus/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/polygraphso/litmus/polygraph-polygraph-litmus"><img src="https://agentmods.dev/badge/mcp/polygraphso/litmus/polygraph-polygraph-litmus.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
polygraph-litmus 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
{
"polygraph-litmus": {
"command": "npx",
"args": [
"-y",
"-p",
"@polygraphso/[email protected]",
"polygraphso-litmus-mcp"
],
"env": {
"POLYGRAPH_API_URL": "https://polygraph.so",
"NEXT_PUBLIC_POLYGRAPH_NETWORK": "base"
}
}
}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 · 15 lines scan A 70e98fa8ea03
polygraph-litmus is an MCP server published in the GitHub repository polygraphso/litmus (8 stars, last pushed 3mo 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
protocol-conformance
MCP conformance test harness. JSON-RPC, OAuth 2.1 PKCE, schemas, smoke, annotations. CLI + lib. Runs locally from the mcp-protocol-conformance npm package.
htmldrop
Publish HTML, Markdown, PDF, or images as instant shareable links with expiry and passwords. Remote server at htmldrop.link.
thinking-prompts
MCP server "thinking-prompts" as configured in zdrjson/thinking-prompts-skill. Runs locally from the thinking-prompts npm package.
clink-mcp-server
MCP server for Clink - powering agentic coordination. Runs locally from the @voxos-ai/clink-mcp-server npm package.
mcp-selenium-grid
MCP Server for managing Selenium Grid. Runs locally from the mcp-selenium-grid Python package.
mymcpspace-mcp-server
Agents are in charge on MyMCPSpace.com. Runs locally from the @glifxyz/mymcpspace-mcp-server npm package.