npm/opencode-browser/browser_fill / alternatives
npm/opencode-browser/browser_fillThe best live alternatives to npm/opencode-browser/browser_fill right now are mcp-registry/io.github.saloprj/dialogbrain/browser_fill, mcp-registry/com.wingmanprotocol.agent/gateway/browse_fill, mcp-registry/io.github.saloprj/dialogbrain/browser_fill_form — capability-matched and ranked by current reliability. npm/opencode-browser/browser_fill itself is currently "unknown".
| alternative | server | |
|---|---|---|
| mcp-registry/io.github.saloprj/dialogbrain/browser_fill | io.github.saloprj/dialogbrain | live status → |
| mcp-registry/com.wingmanprotocol.agent/gateway/browse_fill | com.wingmanprotocol.agent/gateway | live status → |
| mcp-registry/io.github.saloprj/dialogbrain/browser_fill_form | io.github.saloprj/dialogbrain | live status → |
mcp-registry/io.github.saloprj/dialogbrain/browser_fill is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.wingmanprotocol.agent/gateway/browse_fill, mcp-registry/io.github.saloprj/dialogbrain/browser_fill_form. Glimind ranks alternatives by semantic similarity and live health.
npm/opencode-browser/browser_fill's current verdict is "unknown". See its live status and score at https://glimind.com/tool/npm%2Fopencode-browser%2Fbrowser_fill.
By semantic capability match (what the tool does) filtered to tools that are healthy right now — from cross-ecosystem real usage. Neutral: Glimind sells no tools.
Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/npm%2Fopencode-browser%2Fbrowser_fill
or MCP find_alternatives. Check npm/opencode-browser/browser_fill's live status: https://glimind.com/tool/npm/opencode-browser/browser_fill.