Skip to content
News

IndexCyborg is listed in the official MCP Registry

IndexCyborg's indexing server is published in the Model Context Protocol's official registry under the com.indexcyborg namespace, so MCP clients and directories can find it by name.

IndexCyborg's MCP server is listed in the official MCP Registry, the public catalogue of Model Context Protocol servers run by the MCP project at registry.modelcontextprotocol.io. The listing went live on November 9 under the name com.indexcyborg/indexcyborg.

MCP clients and other server directories read from the registry, so the listing makes the server discoverable wherever those catalogues are used, with its description, icons and connection address in one place.

A verified namespace

Names in the registry are tied to who can prove them. The com.indexcyborg namespace is verified against the indexcyborg.com domain with a signed proof served by the website itself, so only the operator of indexcyborg.com can publish under it.

What the listing points to

The entry describes a remote server: there is nothing to install. Clients connect over Streamable HTTP to https://indexcyborg.com/api/mcp, with OAuth for Claude and ChatGPT or an API key for coding agents such as Claude Code, Cursor and VS Code. The server gives AI assistants the same indexing tools as the IndexCyborg dashboard: Google index status and unindexed pages, IndexNow notifications, sitemap discovery, technical checks and website setup.

Setup instructions are on the MCP server page.

About IndexCyborg

IndexCyborg automates the work of getting a website indexed and keeping it indexed. It discovers pages from sitemaps, notifies IndexNow engines when pages change, monitors what Google reports for every page through the URL Inspection API, runs technical checks, and requests indexing from the site owner's own Search Console. It works from a dashboard, a REST API and an MCP server for AI assistants. indexcyborg.com

Media contact

hi@indexcyborg.com