Add Hronaut local browser MCP

[Hronom]

What

Refreshes the existing Hronaut listing with the current public release and verified icon URL.

Evidence

• Product/setup: https://hronaut.dev/setup
• Source: https://github.com/hronaut/hronaut
• Current release: https://github.com/hronaut/hronaut/releases/tag/v2.4.1
• Hronaut is a visible local Electron browser exposing durable workspaces through MCP.
• The entry uses verified: false; this is a vendor submission and maintainers should verify endpoints before changing that field.
• Current public terms are source-available under the Hronaut Subscription and Trial License: one 10-day trial, then $4/month or $24/year per named user.

Validation

• npx tsx scripts/validate-content.ts passed: 503 agents, 21 categories, 0 violations
• npm test -- --run passed: 21 tests
• No private data, secrets, unsupported benchmarks, hosted-browser claim or paid placement included.

[vercel]

@Hronom is attempting to deploy a commit to the assafbar-gmailcom's projects Team on Vercel.

A member of the Team first needs to authorize it.

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[assafbar2]

Merged via #103 — your Hronaut entry is live in the catalog. It conflicted with the 2026-09-13 weekly drop on content/changelog.json, so the commit was cherry-picked with your authorship preserved rather than asking you to rebase.

One note: verified was left as false, not as a judgment on the product. Your MCP endpoint is loopback-only (127.0.0.1:47812), so it cannot be confirmed from outside without installing the desktop app. The docs, cross-platform downloads, and skills.sh listing all check out. Happy to flip it once someone here runs it locally.

Also FYI: hronaut.json carries version and iconUrl, which are outside the documented schema. The validator accepts them, so they were left in place.