NextCore Browser
org.homestaynextcorePublished by homestaynextcore.orgv0.3.187Updated Nov 6, 2026
Multi-profile browser: AI agents create, open and drive isolated signed-in profiles with own proxy
The publisher's own server: core.blue
Overview
A local, desktop-only MCP server that lets an AI agent create, open and drive multiple isolated, signed-in browser profiles, each with its own proxy.
- What you can do
- Create and manage multiple isolated browser profiles.
- Open profiles that are already signed in to sites.
- Drive browsing inside a chosen profile, keeping sessions separate.
- Route each profile through its own proxy.
- No individual tools are documented in the supplied listing, so exact operations are unclear.
- When to use it
- Useful when an assistant needs to work across several separate browser identities or accounts at once, keep sessions and cookies apart, or send different browsing traffic through different proxies. Best suited to desktop setups where a local browser process can run.
- Requirements
- Runs as a local process on the user's machine over stdio; desktop only, with no web-hosted option. No packages, environment variables, headers or authentication are declared, so the runtime and browser it depends on are not specified in the listing.
Installation
In SourceWeft
- Open NextCore Browser in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Tools
0Version history
12- v0.3.187LatestNov 6, 2026
- v0.3.186Nov 6, 2026
- v0.3.185Nov 4, 2026
- v0.3.184Nov 4, 2026
- v0.3.183Nov 4, 2026
- v0.3.182Nov 4, 2026
- v0.3.181Nov 3, 2026
- v0.3.179Nov 3, 2026
- v0.3.173Nov 1, 2026
- v0.3.172Nov 1, 2026
- v0.3.170Nov 1, 2026
- v0.3.165Oct 30, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.
Other Core integrations
core.blue
blue.coreOfficial publisher
Remote MCP endpoint for core.blue's private per-customer agent memory "houses": read its manual, try a sandbox, get pricing and recommendations, and request a…

Brevio Core
Published by GitHub account Brevio-Ventures
Local MCP server that lets a coding agent scan code for recurring agent-written mistakes, explain rules, list rules and turn a fix into a guard.

brain-core
Published by GitHub account xy-claude
Local MCP server giving a Claude Code agent persistent memory in a markdown vault plus SQLite and an optional self-hosted vector store.

Scovant Core
Published by GitHub account Scovant
Passive AI-agent readiness scan of a website: robots, llms.txt, JSON-LD, MCP discovery, security.

ProofCore
Published by GitHub account ProofCore-Protocol
Zero-Auth Cryptographic Notarization & Evidence Layer on TON Blockchain for AI Agents.