io.github.jxoesneon/ultranix-mcp

MCPcommunity
v1.4.0io.github.jxoesneonUnknownUpdated 18d agoGitHub

Secure Linux desktop automation - input, screen/OCR/vision, AT-SPI2 UI tree, window, clipboard

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
18d agoLast update
Reads these credentials
  • ULTRANIX_MCP_API_KEYAPI keyoptional

    API key(s) (uxcp_*) for HTTP transport auth - required for --transport http (fail-closed), unused on stdio

  • ULTRANIX_MCP_HISTORY_SECRETAPI keyoptional

    AES-256-GCM secret for encrypted action history (per-install generated if unset)

  • ULTRANIX_MCP_SENTRY_DSNAPI keyoptional

    Optional Sentry DSN for error reporting (unset = disabled)

  • ULTRANIX_MCP_AUDIT_SECRETAPI keyoptional

    Optional HMAC-SHA256 signing secret for audit.jsonl lines (tamper evidence for SIEM ingestion)

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.jxoesneon
LicenseUnknown
Version1.4.0
Sourcemcp-registry
GitHubjxoesneon/ultranix-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
F
10/100Untrusted
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
—Prompt-injection scan · not run+0/30
→ Not yet scanned — the repository archive is scanned on the next cron run
—Obfuscation / exfil scan · not run+0/20
→ Not yet scanned — the repository archive is scanned on the next cron run
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scanNot runHow well does this scan work?
EvalsNone
IndexedSep 17, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

Not scanned yet

Forge has no scan on record for this entry, so it holds no observation of its tool surface. That is an absence of evidence, not evidence that it exposes no tools.

About

Secure Linux desktop automation - input, screen/OCR/vision, AT-SPI2 UI tree, window, clipboard

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.