org.homestaynextcore/nextcore-browser
NextCore Browser
Multi-profile browser: AI agents create, open and drive isolated signed-in profiles with own proxy
not probed in the official registry, not probed
- Endpoint
- (none)
- Host
- registry.modelcontextprotocol.io
- Website
- https://docs.homestaynextcore.org/en/use-cases/ai-agent-many-browser-profiles/
- Registry
- active, updated 2026-11-15 · registry entry
Compare this server with others.
More servers
Other registry entries on registry.modelcontextprotocol.io, the ones next to this name; all of them.
- Glint Render — web rendering for AI agents io.github.zzzjy765/ottersnap · not probed
- io.softspoken/softspoken · not probed
- SKETCHTALK – Draw to AI jp.twelvetone/sketchtalk · not probed
- arc moi.arc/arc · not probed
- org.p31ca/oasis-mcp · not probed
- XTester Studio pw.xtester/xtester · not probed
- Yandex Tools MCP ru.seyka/yandex-tools-mcp · not probed
- run.chromeflow/chromeflow · not probed
Servers that mention browser.
- ai.foura/mcp · alive
- ai.kaiv/can-i-use · alive
- NativePort ai.nativeport/mcp · needs auth
- ai.openhelm/openhelm · needs auth
- PlayDrop ai.playdrop/mcp · needs auth
- Qlane ai.qlane/qlane · needs auth
- Reduck ai.reduck/reduck · needs auth
- ai.smithery/ImRonAI-mcp-server-browserbase · not found
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The entry has no remote URL and no package: there is nothing to connect to. The entry is on the board so that the list holds the whole registry and says what it does not check.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.