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/xidik12/oculoWrote 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/xidik12/oculo/oculo)<a href="https://agentmods.dev/mcp/xidik12/oculo/oculo"><img src="https://agentmods.dev/badge/mcp/xidik12/oculo/oculo/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/xidik12/oculo/oculo"><img src="https://agentmods.dev/badge/mcp/xidik12/oculo/oculo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
oculo 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
{
"oculo": {
"command": "npx",
"args": [
"-y",
"oculo-mcp"
],
"env": {}
}
}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 · 10 lines scan A 598847e14832
oculo is an MCP server published in the GitHub repository xidik12/oculo (5 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
x-use
Browser-native AI agents for X (Twitter): multi-account, MCP-ready, no API keys required. Runs locally from the x-use-mcp Python package. Needs 2 environment variables to run.
chatcrystal
Local-first AI PKM memory for coding conversations. Runs locally from the chatcrystal npm package. Needs 2 environment variables to run.
uisight
Your AI sees the screen but can't measure it — measured web UI findings, shared live sessions. Runs locally from the uisight npm package. Needs 3 environment variables to run.
core
Agent-native MCP server for driving, inspecting, and asserting on real Electron desktop apps. Runs locally from the @electron-stagewright/core npm package.
ai-browser
MCP server "ai-browser" as configured in AI-XiaoDao/ai-browser-mcp. Runs CEFbro/AI-Fbowser-Mcp/mcp_bridge.js with node. Needs 3 environment variables to run.
chrome-mcp-server
MCP server "chrome-mcp-server", hosted remotely at 127.0.0.1, as configured in iloveitaly/llm-ide-rules.