How do I use a custom MCP registry in VS Code?

Add "chat.mcp.gallery.serviceUrl": "https://neuronto.com" to your user settings.json, then type @mcp in the Extensions view: the MCP server gallery lists the registry's servers. An MCP registry policy set by your GitHub organization takes precedence over the setting.

How do I restrict GitHub Copilot to the MCP servers in a registry?

An organization or enterprise owner opens Settings, Copilot, Policies, keeps MCP servers in Copilot enabled, enters the registry URL in the MCP Registry URL field and saves. Choosing Registry only under the access restriction then lets developers start only the servers listed in that registry.

What is the difference between neuronto.com and neuronto.com/verified?

Both serve the same API. neuronto.com lists every server with connection details. neuronto.com/verified lists only server versions whose remote endpoint answered an MCP handshake, or asked for sign-in or payment in the protocol's own way, and was reachable at the last liveness check.

Can I publish a server to Neuronto's MCP registry?

No. This registry is read-only and answers 501 to every write, as the API specification documents for a read-only registry. Publish to the official MCP Registry, or serve a remote MCP endpoint and an ARD manifest on your own domain; both are picked up from the next snapshot.

MCP Registry v0.1 API

Use Neuronto as your MCP server gallery

Neuronto serves the MCP Registry v0.1 read API, the interface VS Code, Visual Studio, JetBrains IDEs, Eclipse, Xcode and the Copilot CLI read a server gallery from. Set the registry URL to https://neuronto.com to browse 55,696 MCP servers, or to https://neuronto.com/verified for only the 17,015 whose endpoint answered an MCP handshake and was reachable when last checked.

What the registry serves

Two sources, one API, nothing invented:

Source	What is listed
The official MCP Registry	Every server and every version, passed through as published, with its own status and publication dates. Records the registry's own schema rejects, and records with no package or remote a client could connect to, are left out.
Independently published remote servers	Remote MCP endpoints from Neuronto's index that are not in the official registry, listed only when the endpoint answered an MCP handshake and reported its version. The name is assigned in reverse DNS from the endpoint's host, and the record says so.

What Neuronto observed sits beside each record, never inside it, under _meta["com.neuronto/registry"]: the result and time of the last handshake, the number of tools the server listed, how many liveness probes it answered, a verified domain claim, and a link to the server's page here.

"_meta": {
  "com.neuronto/registry": {
    "source": "official-registry",
    "remoteCheck": {"url": "https://example.com/mcp", "result": "handshake-ok",
                    "checkedAt": "2026-11-03T05:12:40Z", "tools": 12},
    "liveness": {"reachable": true, "probes": 40, "succeeded": 40}
  }
}

VS Code

Add one line to your user settings.json:

"chat.mcp.gallery.serviceUrl": "https://neuronto.com"

Then type @mcp in the Extensions view. The gallery lists this registry's servers; installing one writes the server's own package or remote URL into your MCP configuration, so the server runs from where its publisher hosts it. Use https://neuronto.com/verified instead for only the servers that answered a handshake. A registry set by your organization's Copilot policy takes precedence.

GitHub Copilot for an organization or enterprise

Open the organization's or enterprise's Settings, then Copilot, then Policies.
Keep MCP servers in Copilot enabled.
In MCP Registry URL, enter https://neuronto.com/verified (or https://neuronto.com) and save.
To let developers start only listed servers, set the access restriction to Registry only.

The registry meets the requirements Copilot sets for a custom registry: the v0.1 endpoints, and Access-Control-Allow-Origin: *, Access-Control-Allow-Methods: GET, OPTIONS and Access-Control-Allow-Headers: Authorization, Content-Type on every /v0.1/servers path. The same applies to Visual Studio, JetBrains IDEs, Eclipse, Xcode and the Copilot CLI, which read the policy.

The API

Request	Answer
`GET /v0.1/servers`	One record per server version, ordered by name then version. Parameters: `limit` (up to 100), `cursor`, `search` (case-insensitive substring of the name), `version` (`latest` or an exact version), `updated_since` (RFC 3339), `include_deleted`.
`GET /v0.1/servers/{name}/versions`	Every version of one server; the name URL-encoded, as in `io.github.acme%2Fweather`.
`GET /v0.1/servers/{name}/versions/latest`	The latest version, or an exact one in place of `latest`.
`POST /v0.1/publish`, `PUT`, `DELETE`	501: the registry is read-only.

Every path also works under /verified. Deleted records are left out unless include_deleted=true, and are always included with updated_since, so a client keeping its own copy learns what was removed. A server Neuronto stops listing stays as a record marked deleted for 90 days.

curl -s 'https://neuronto.com/verified/v0.1/servers?search=weather&version=latest&limit=5'

Freshness

The registry is a snapshot, rebuilt each day after Neuronto's index has been refreshed, and replaced in one step, so a page of results never mixes two snapshots and a cursor stays valid across a rebuild. Every answer names its snapshot in an X-Registry-Snapshot header and in Last-Modified, and carries an ETag, so a client can ask with If-None-Match and get a 304 when nothing changed.

The snapshot of 3 November 2026 held 213,887 records: 55,696 servers with their latest versions, 17,015 of them verified.

Check your own domain. The console fetches what you publish and asks every public registry whether they return you.

Run a free audit