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/ilinxa/ilinxa-captureWrote 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/ilinxa/ilinxa-capture/ilinxa-capture)<a href="https://agentmods.dev/mcp/ilinxa/ilinxa-capture/ilinxa-capture"><img src="https://agentmods.dev/badge/mcp/ilinxa/ilinxa-capture/ilinxa-capture/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/ilinxa/ilinxa-capture/ilinxa-capture"><img src="https://agentmods.dev/badge/mcp/ilinxa/ilinxa-capture/ilinxa-capture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
Grade A, and why
ilinxa-capture 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 yesterday.
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
{ "ilinxa-capture": { "command": "npx", "args": [ "-y", "ilinxa-capture" ] } }
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.
- yesterday First seen · 9 lines scan A 87635dd3878d
ilinxa-capture is an MCP server published in the GitHub repository ilinxa/ilinxa-capture (2 stars, last pushed 3d 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-11-03.
Other mcp servers, from other repositories
squish
Give AI random access to video: timestamped contact sheets + zoom into any start/end range. Runs locally from the @getsquish/squish npm package.
kinocut
Trusted, guardrailed video editing for AI agents. FFmpeg, Hyperframes, repurposing tools, Python client, CLI, and MCP server. Runs locally from the kinocut Python package.
kinocut
Trusted, guardrailed video editing for AI agents. FFmpeg, Hyperframes, repurposing tools, Python client, CLI, and MCP server. Runs locally from the kinocut Python package.
browser
MCP server "browser" as configured in felipebarcelospro/igniter-js. Launched with npx @playwright/mcp@latest.
clerk
MCP server "clerk", hosted remotely at mcp.clerk.com, as configured in FloB95/qrcodly.
bring-photo-mcp
Add products to Bring! from a photo — MCP for AI recognition, catalog matching, and verified writes. Runs locally from the bring-photo-mcp npm package. Needs 8 environment variables to run.