Is axuse safe to install?

Security audit of ctoldigital/axuse · MCP Server by ctoldigital · ★ 774

✓ SAFE Basic audit · rule-based scan · 42 published rules

Yes — axuse passed AgentSkillsHub's rule-based security scan with no dangerous patterns detected. As with any third-party skill, confirm what credentials it requests before production use.

What it is: Accessibility-first browser & computer use for AI agents — one MCP server for every harness (Codex, Claude Code, OpenCode, Antigravity). Instruments the DOM/accessibility tree via CDP instead of screenshot loops: diffed snapshots, stable element refs, trusted input, typed errors. Zero dependencies

No dangerous patterns were detected: no credential exfiltration, no obfuscated downloads, no sandbox-escape attempts, no prompt-injection markers.

Audit summary

Security grade	✓ SAFE
Quality score	69/100
GitHub stars	774
Language	JavaScript
License	NOASSERTION
Last updated	2026-11-03

Check before you install

What credentials does it ask for, and where are they stored?
Is the maintainer identifiable and the repo actively maintained?
Read the install scripts and network calls before trusting it.

Run a live scan → Full details & install 5-dimension deep audit

Related MCP Server audits

Is rea safe? — SAFE · ★ 439.9k
Is ECC safe? — SAFE · ★ 298.5k
Is n8n safe? — SAFE · ★ 209.8k
Is dify safe? — SAFE · ★ 160.6k
Is open-webui safe? — SAFE · ★ 157.6k
Is cc-switch safe? — SAFE · ★ 152.6k

Browse all MCP Server skills →

This is AgentSkillsHub's free basic audit: an automated rule-based scan with 42 published rules built on SlowMist's agent-security taxonomy (credential theft, obfuscated payloads, privilege escalation, covert instructions to the agent, and more) across 186,000+ open-source AI agent skills and MCP servers, refreshed every 8 hours. A SAFE grade is a scan result, not a guarantee — deep 5-dimension audits (code · credentials · vendor · supply-chain · operational) are available for enterprise. Audited: 2026-11-04.