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/juergenkoller-software/inkra-mcpWrote 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/juergenkoller-software/inkra-mcp/inkra)<a href="https://agentmods.dev/mcp/juergenkoller-software/inkra-mcp/inkra"><img src="https://agentmods.dev/badge/mcp/juergenkoller-software/inkra-mcp/inkra/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/juergenkoller-software/inkra-mcp/inkra"><img src="https://agentmods.dev/badge/mcp/juergenkoller-software/inkra-mcp/inkra.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
inkra 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 9d 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
{
"inkra": {
"command": "/usr/local/bin/InkraMCP",
"env": {
"INKRA_PORT": "22300",
"INKRA_TOKEN": "<paste-from-inkra-settings-api-integrations>"
}
}
}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.
- 9d ago First seen · 9 lines scan A e967274f1a0e
inkra is an MCP server published in the GitHub repository juergenkoller-software/inkra-mcp (1 stars, last pushed 3mo 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
nemeton
MCP server "nemeton" as configured in juergenkoller-software/nemeton-mcp. Launched with /usr/local/bin/NemetonMCP. Needs 2 environment variables to run.
pdf-content-search
MCP server "pdf-content-search" as configured in juergenkoller-software/pdf-content-search-mcp. Launched with /usr/local/bin/pdf-content-search-mcp. Needs 2 environment variables to run.
mcpspend
Query your MCPSpend usage: cost today, top tools, recent sessions, budget projections. Runs locally from the @mcpspend/mcp-server npm package. Needs 2 environment variables to run.
fetch
Lets the agent fetch a URL and read its content as markdown. Runs locally from the mcp-server-fetch Python package.
nodejs-api-docs
An MCP Server for Node.js API documentation. Runs locally from the mcp-server-nodejs-api-docs npm package.
applemusic-mcp
MCP server for Apple Music — cross-platform library, playlists, and playback; no Apple Developer account required. Runs locally from the applemusic-mcp Python package.