npm/opencode-browser/browser_close / alternatives

Live alternatives to npm/opencode-browser/browser_close

The best live alternatives to npm/opencode-browser/browser_close right now are mcp-registry/io.github.saloprj/dialogbrain/browser_close, mcp-registry/com.wingmanprotocol.agent/gateway/browse_close — capability-matched and ranked by current reliability. npm/opencode-browser/browser_close itself is currently "unknown".

alternative	server
mcp-registry/io.github.saloprj/dialogbrain/browser_close	io.github.saloprj/dialogbrain	live status →
mcp-registry/com.wingmanprotocol.agent/gateway/browse_close	com.wingmanprotocol.agent/gateway	live status →

FAQ

What is the best alternative to npm/opencode-browser/browser_close?

mcp-registry/io.github.saloprj/dialogbrain/browser_close is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.wingmanprotocol.agent/gateway/browse_close. Glimind ranks alternatives by semantic similarity and live health.

Is npm/opencode-browser/browser_close down right now?

npm/opencode-browser/browser_close's current verdict is "unknown". See its live status and score at https://glimind.com/tool/npm%2Fopencode-browser%2Fbrowser_close.

How does Glimind pick alternatives?

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.

For agents

Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/npm%2Fopencode-browser%2Fbrowser_close or MCP find_alternatives. Check npm/opencode-browser/browser_close's live status: https://glimind.com/tool/npm/opencode-browser/browser_close.