OpenDia connects web browsers such as Chrome, Arc, and Firefox to AI models. It is for people who want to use AI models through their browser, with automation and MCP support.
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/aeonfun/opendiaWrote 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/aeonfun/opendia/opendia-opendia)<a href="https://agentmods.dev/mcp/aeonfun/opendia/opendia-opendia"><img src="https://agentmods.dev/badge/mcp/aeonfun/opendia/opendia-opendia/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/aeonfun/opendia/opendia-opendia"><img src="https://agentmods.dev/badge/mcp/aeonfun/opendia/opendia-opendia.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
opendia 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
{
"opendia": {
"command": "npx",
"args": [
"-y",
"opendia"
]
}
}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 · 9 lines scan A 6d5acb9ccaff
opendia is an MCP server published in the GitHub repository aeonfun/opendia (1,932 stars, last pushed 8d 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-30.
Other mcp servers, from other repositories
huly-mcp
Huly MCP: feature-complete MCP server for Huly integration. Runs locally from the @firfi/huly-mcp npm package. Needs 9 environment variables to run.
real-browser
MCP server + Chrome extension for AI browser control with real sessions. Runs locally from the real-browser-mcp npm package.
browser-mcp
Browser MCP - the browser tool that can stop and ask you. A 2FA code, a CAPTCHA, a choice only you can make: it asks on your own screen, then carries on in the tab you were already signed into. 40 tools, any MCP client, MIT. Runs locally from the @agent360/browser-mcp npm package.
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
browser-controller
Control your browser. Runs locally from the browser-controller npm package.
chrome-bridge
Your real, logged-in Chrome as an MCP server: 60 token-efficient web-dev tools. ChromeOS included. Runs locally from the chrome-bridge-mcp npm package.