Lets an AI client check Google indexing status and request page indexing or IndexNow notifications for your websites.
Also known as indexmachine/indexmachine-mcp, indexmachine-mcp
- Stars
- 0
- Tools
- 10
- Downloads, 30 days
- 474
- Latest version
- 0.1.0
- Last commit
- Oct 31, 2026
- License
- MIT
What is IndexMachine MCP?
IndexMachine lets an AI client check Google indexing status and request page indexing or IndexNow notifications for your websites. It exposes 10 tools, such as account_status, list_sites, site_summary.
Summary generated from the project's README
About IndexMachine MCP server
IndexMachine allows developers to manage website indexing directly through AI assistants like Claude Desktop, Cursor, VS Code, and Claude Code. By connecting to your IndexMachine account via an API key, you can monitor which of your pages are currently indexed by Google and manage indexing requests. The server functions both locally using npx and as a remote server for web-based clients.
The toolset includes specific commands to list sites, check individual URL statuses, and queue indexing requests. It uses a Chrome extension to simulate manual clicks in Google Search Console, meaning requests are not instant but follow a queue. For alternative engines, the server can notify Bing and Yandex using IndexNow. Users can choose between full access keys or read-only keys to limit the assistant to monitoring tasks without the ability to queue requests or submit to IndexNow.
What you can do with it
- 1Verify Google indexing statusCheck if a specific URL is currently indexed by Google and see when it was last seen.
- 2Queue new indexing requestsRequest that Google index a new page or re-index an existing one.
- 3Notify alternative search enginesSend IndexNow notifications to Bing and Yandex for a list of URLs.
- 4Monitor site indexing healthGet a summary of a site including its daily request quota and median days to indexing.
Written from the project's README. Every use case is checked against a quote from it.
How to install IndexMachine MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall IndexMachine MCP in Claude Code
$ claude mcp add --env 'INDEXMACHINE_API_KEY=<YOUR_INDEXMACHINE_API_KEY>' indexmachine-mcp -- npx -y indexmachine-mcpInstall IndexMachine MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"indexmachine-mcp": {
"command": "npx",
"args": [
"-y",
"indexmachine-mcp"
],
"env": {
"INDEXMACHINE_API_KEY": "<YOUR_INDEXMACHINE_API_KEY>"
}
}
}
}Install IndexMachine MCP in VS Code
.vscode/mcp.json
{
"servers": {
"indexmachine-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"indexmachine-mcp"
],
"env": {
"INDEXMACHINE_API_KEY": "<YOUR_INDEXMACHINE_API_KEY>"
}
}
}
}Install IndexMachine MCP in VS Code CLI
$ code --add-mcp '{"name":"indexmachine-mcp","type":"stdio","command":"npx","args":["-y","indexmachine-mcp"],"env":{"INDEXMACHINE_API_KEY":"<YOUR_INDEXMACHINE_API_KEY>"}}'Install IndexMachine MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"indexmachine-mcp": {
"command": "npx",
"args": [
"-y",
"indexmachine-mcp"
],
"env": {
"INDEXMACHINE_API_KEY": "<YOUR_INDEXMACHINE_API_KEY>"
}
}
}
}Install IndexMachine MCP in Codex
$ codex mcp add indexmachine-mcp --env 'INDEXMACHINE_API_KEY=<YOUR_INDEXMACHINE_API_KEY>' -- npx -y indexmachine-mcpInstall IndexMachine MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.indexmachine-mcp] command = "npx" args = ["-y", "indexmachine-mcp"] [mcp_servers.indexmachine-mcp.env] INDEXMACHINE_API_KEY = "<YOUR_INDEXMACHINE_API_KEY>"
Install IndexMachine MCP in Gemini CLI
$ gemini mcp add -s user -e 'INDEXMACHINE_API_KEY=<YOUR_INDEXMACHINE_API_KEY>' indexmachine-mcp npx -- -y indexmachine-mcpInstall IndexMachine MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"indexmachine-mcp": {
"command": "npx",
"args": [
"-y",
"indexmachine-mcp"
],
"env": {
"INDEXMACHINE_API_KEY": "<YOUR_INDEXMACHINE_API_KEY>"
}
}
}
}Started by HostedMCP on 16 Nov 2026
We ran this command for indexmachine-mcp 0.1.0 in an isolated container with no network and no keys. It answered and listed 10 tools.
IndexMachine MCP tools 10
Read from the server with tools/listaccount_statusRead-onlyThe plan, the key's permissions and hourly request budget, whether the user's IndexMachine Chrome extension is online (it performs every Request indexing click), and today's requests per site against Google's daily quota of about 10 per site.
list_sitesRead-onlyEvery Search Console property connected to IndexMachine, with its page counts (indexed, awaiting, rejected, needs_fix, excluded), whether Google indexing is on, whether a paid plan covers it (billable, which Request indexing needs) and whether IndexNow is ready.
site_summaryRead-onlyOne site in full: page counts, today's Request indexing quota (about 10 a day, reset at midnight Pacific), the median days from a first request to indexing, and up to 30 days of counts.
list_pagesRead-onlyA site's pages by path, with their status, Google's coverage state and the last crawl and request. status not_indexed is every page that is neither indexed nor excluded; q matches part of the URL. A status comes from the last stored inspection; check_url has a single URL in full.
check_urlRead-onlyWhether a URL of one of the user's sites is indexed on Google, and as of when: the stored Search Console inspection, its open indexing request with the ETA, and with live: true a fresh URL Inspection from Google, which uses 1 of 50 live checks per site a day. indexed is null, not known, when the URL was never inspected. When Google refuses a live check, the stored state comes back with a warning.
request_indexingActionQueues a Request indexing click for a URL of one of the user's sites, also one that is not a page of the site yet. The user's IndexMachine Chrome extension performs it in their own Search Console when it next checks in, within about 10 requests per site per day; the answer has the queue position and the ETA in eta_text, which is for the click and not for indexing. It previews first, and queues nothing for a page that is already indexed unless force is true, a re-index. A re-index, a URL that is not in the sitemap, or the site's last request of the day waits for the user's yes. A client on MCP protocol 2026-07-28 that supports elicitation gets a question to confirm, and the answer does not pass through the model. This remote server keeps no session, so a client on an earlier protocol version is not asked: the tool refuses first with a confirm token, and the call with that token stands for the user's yes.
get_indexing_requestRead-onlyOne indexing request: its status, queue position and ETA in eta_text while open, and what Search Console answered once the extension performed it. A closed request with status requested means the click happened; whether Google indexed the page is check_url's answer.
list_indexing_requestsRead-onlyIndexing requests newest first, for one site or all of them: open ones (preparing, queued, served) with their position and ETA, or closed ones with their outcome. Closed requests are kept 90 days.
cancel_indexing_requestActionTakes an open indexing request out of the queue, so the extension never performs it. The page stays in IndexMachine. A closed request cannot be canceled.
submit_indexnowActionNotifies Bing, Yandex and the other IndexNow engines of up to 100 URLs of one site at once; it does not reach Google, and each engine decides when it crawls. It needs the site's IndexNow key file in place (indexnow_ready in list_sites) and takes 20 submissions per site a day. More than 10 URLs at once wait for the user's yes. A client on MCP protocol 2026-07-28 that supports elicitation gets a question to confirm, and the answer does not pass through the model. This remote server keeps no session, so a client on an earlier protocol version is not asked: the tool refuses first with a confirm token, and the call with that token stands for the user's yes.
| account_status | The plan, the key's permissions and hourly request budget, whether the user's IndexMachine Chrome extension is online (it performs every Request indexing click), and today's requests per site against Google's daily quota of about 10 per site. | Read-only |
| list_sites | Every Search Console property connected to IndexMachine, with its page counts (indexed, awaiting, rejected, needs_fix, excluded), whether Google indexing is on, whether a paid plan covers it (billable, which Request indexing needs) and whether IndexNow is ready. | Read-only |
| site_summary | One site in full: page counts, today's Request indexing quota (about 10 a day, reset at midnight Pacific), the median days from a first request to indexing, and up to 30 days of counts. | Read-only |
| list_pages | A site's pages by path, with their status, Google's coverage state and the last crawl and request. status not_indexed is every page that is neither indexed nor excluded; q matches part of the URL. A status comes from the last stored inspection; check_url has a single URL in full. | Read-only |
| check_url | Whether a URL of one of the user's sites is indexed on Google, and as of when: the stored Search Console inspection, its open indexing request with the ETA, and with live: true a fresh URL Inspection from Google, which uses 1 of 50 live checks per site a day. indexed is null, not known, when the URL was never inspected. When Google refuses a live check, the stored state comes back with a warning. | Read-only |
| request_indexing | Queues a Request indexing click for a URL of one of the user's sites, also one that is not a page of the site yet. The user's IndexMachine Chrome extension performs it in their own Search Console when it next checks in, within about 10 requests per site per day; the answer has the queue position and the ETA in eta_text, which is for the click and not for indexing. It previews first, and queues nothing for a page that is already indexed unless force is true, a re-index. A re-index, a URL that is not in the sitemap, or the site's last request of the day waits for the user's yes. A client on MCP protocol 2026-07-28 that supports elicitation gets a question to confirm, and the answer does not pass through the model. This remote server keeps no session, so a client on an earlier protocol version is not asked: the tool refuses first with a confirm token, and the call with that token stands for the user's yes. | Action |
| get_indexing_request | One indexing request: its status, queue position and ETA in eta_text while open, and what Search Console answered once the extension performed it. A closed request with status requested means the click happened; whether Google indexed the page is check_url's answer. | Read-only |
| list_indexing_requests | Indexing requests newest first, for one site or all of them: open ones (preparing, queued, served) with their position and ETA, or closed ones with their outcome. Closed requests are kept 90 days. | Read-only |
| cancel_indexing_request | Takes an open indexing request out of the queue, so the extension never performs it. The page stays in IndexMachine. A closed request cannot be canceled. | Action |
| submit_indexnow | Notifies Bing, Yandex and the other IndexNow engines of up to 100 URLs of one site at once; it does not reach Google, and each engine decides when it crawls. It needs the site's IndexNow key file in place (indexnow_ready in list_sites) and takes 20 submissions per site a day. More than 10 URLs at once wait for the user's yes. A client on MCP protocol 2026-07-28 that supports elicitation gets a question to confirm, and the answer does not pass through the model. This remote server keeps no session, so a client on an earlier protocol version is not asked: the tool refuses first with a confirm token, and the call with that token stands for the user's yes. | Action |
Configuration
INDEXMACHINE_API_KEYRequiredSecretAPI key from the Settings page of the IndexMachine dashboard (im_live_...)
| Name | Description | |
|---|---|---|
| INDEXMACHINE_API_KEY | API key from the Settings page of the IndexMachine dashboard (im_live_...) | RequiredSecret |
Automated checks
Ran Nov 16, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableindexmachine/indexmachine-mcp is public and reachablegithub.com/indexmachine/indexmachine-mcp ↗Pass
- Package names this repository as its sourceindexmachine-mcp names indexmachine/indexmachine-mcp as sourcenpmjs.com/package/indexmachine-mcp ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-31github.com/indexmachine/indexmachine-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from indexmachine-mcpPass
- No critical advisory in the package or its dependencies4 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model10 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-11-25 in 159 ms; tools/list returned 10 toolsPass
README
View on GitHubIndexMachine MCP server
Check your own sites' pages on Google and request indexing, plus IndexNow, from your AI assistant.
This MCP server lets Claude Code, Cursor, VS Code, Claude Desktop and claude.ai work with the sites you connected to IndexMachine: list your sites and pages, check whether a URL is on Google, queue a Request indexing click (also a re-index of a page that is already indexed) and notify Bing and the other IndexNow engines. It calls the IndexMachine API with your key and does nothing the API does not.
How a request really travels
IndexMachine uses Request indexing in your own Google Search Console and IndexNow, no link farms. So a request is not instant, and the server says so every time:
request_indexingqueues the click. It does not reach Google by itself.- The IndexMachine Chrome extension, in your Chrome and signed in to the Google account that owns the property, picks the request up when it next checks in: about every 5 minutes on extension 1.2.0 or newer, every 30 minutes on older versions. Chrome has to be running. When the extension has not checked in for 40 minutes there is no ETA, and the request waits in the queue.
- The extension clicks Request indexing in your Search Console, the same button you would press.
- Google takes about 10 of these requests per site per day, a day that resets at midnight Pacific. The number is observed; Google does not publish it. Requests you queue go ahead of the extension's daily work on your other pages and share the same 10. Once a site's day is used up, the ETA moves past midnight Pacific.
- Google then decides whether and when it indexes the page, often days later. The ETA is for the click,
never for indexing, and only
check_urlsays a page is indexed.
A re-index of a page that is already on Google (force: true) needs extension 1.2.0 or newer. IndexNow
tells Bing, Yandex and the other IndexNow engines directly; it needs the site's IndexNow key file in place,
takes 20 submissions per site a day and does not reach Google.
What you need
- An IndexMachine account with your sites connected: app.indexmachine.co. Signing up is free and shows which of your pages Google has not indexed. Requesting indexing needs a paid plan for the site (pricing).
- The IndexMachine Chrome extension, installed and signed in, for the Request indexing clicks.
- An API key (with claude.ai you can add it as a request header, see Remote server).
Create an API key
- Open the IndexMachine dashboard and choose Settings from your profile menu, or go straight to app.indexmachine.co/settings.
- Under API keys press Create key and give it a label, such as
Claude Code. - Pick Full (it also queues and cancels requests and submits to IndexNow) or Read only (sites, pages, checks and requests).
- Copy the key. It starts with
im_live_and is shown only once.
Roll or revoke a key on the same page at any time; an account holds up to 10 active keys.
Install
The package runs on your machine with npx (Node.js 20 or newer). Keep the key in your user-level
config, never in a file that lives in a repository.
Claude Code (user scope, so the key stays out of the project's .mcp.json)
claude mcp add --scope user indexmachine --env INDEXMACHINE_API_KEY=im_live_... -- npx -y indexmachine-mcp
Cursor (~/.cursor/mcp.json, the user-level file)
{
"mcpServers": {
"indexmachine": {
"command": "npx",
"args": ["-y", "indexmachine-mcp"],
"env": { "INDEXMACHINE_API_KEY": "im_live_..." }
}
}
}
VS Code (.vscode/mcp.json): VS Code asks for the key and keeps it out of the file.
{
"inputs": [
{ "type": "promptString", "id": "indexmachine-key", "description": "IndexMachine API key", "password": true }
],
"servers": {
"indexmachine": {
"type": "stdio",
"command": "npx",
"args": ["-y", "indexmachine-mcp"],
"env": { "INDEXMACHINE_API_KEY": "${input:indexmachine-key}" }
}
}
}
Claude Desktop (claude_desktop_config.json): the same block as Cursor, under mcpServers.
Other MCP clients: run npx -y indexmachine-mcp with INDEXMACHINE_API_KEY in its environment, or
use the remote server below.
Remote server
The remote server at https://mcp.indexmachine.co/mcp needs no install. Clients send the API key in a
header:
URL: https://mcp.indexmachine.co/mcp
Header: Authorization: Bearer <your key> (X-API-Key: <your key> works too)
Claude Code
claude mcp add --transport http indexmachine https://mcp.indexmachine.co/mcp \
--header "Authorization: Bearer $INDEXMACHINE_API_KEY"
Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"indexmachine": {
"url": "https://mcp.indexmachine.co/mcp",
"headers": { "Authorization": "Bearer im_live_..." }
}
}
}
VS Code (.vscode/mcp.json)
{
"inputs": [
{ "type": "promptString", "id": "indexmachine-key", "description": "IndexMachine API key", "password": true }
],
"servers": {
"indexmachine": {
"type": "http",
"url": "https://mcp.indexmachine.co/mcp",
"headers": { "Authorization": "Bearer ${input:indexmachine-key}" }
}
}
}
claude.ai: a custom connector
- In claude.ai, open Customize > Connectors, press + Add, then Add custom connector.
- Enter the name
IndexMachineand the URLhttps://mcp.indexmachine.co/mcp. - Under Request headers add
Authorizationwith the valueBearer im_live_..., then press Add. - In a chat, open +, then Connectors, and switch IndexMachine on.
IndexMachine and the Submitator connector can be on in the same chat: no tool name is shared.
Signing in with your IndexMachine account instead of a key (OAuth) is built into this server and stays off until IndexMachine's API issues sign-in tokens. Until then the server advertises no sign-in, and every client sends a key.
The remote server keeps nothing between requests: it passes the key on to the IndexMachine API and forgets it.
Tools
| Tool | What it does |
|---|---|
account_status |
Your plan, the key's permissions and hourly budget, whether the Chrome extension is online, and today's requests per site against Google's daily quota |
list_sites |
Your connected Search Console properties with page counts, whether Google indexing is on, whether a paid plan covers them and whether IndexNow is ready |
site_summary |
One site: today's Request indexing quota, the median days from a first request to indexing, and 30 days of counts |
list_pages |
A site's pages by status (indexed, not_indexed, awaiting, requested, rejected, needs_fix, excluded, not_found) or part of the URL, 50 at most per call |
check_url |
Whether a URL is indexed, and as of when, or that it is not known yet (never inspected); live: true asks Google now and uses 1 of 50 live checks per site a day |
request_indexing |
Queues a Request indexing click, also for a URL that is not a page of the site yet, and with force: true a re-index of an indexed page. Answers the queue position and an honest ETA |
get_indexing_request, list_indexing_requests |
Follow requests: open ones with their position and ETA, closed ones with what Search Console answered |
cancel_indexing_request |
Takes an open request out of the queue |
submit_indexnow |
Notifies Bing, Yandex and the other IndexNow engines of up to 100 URLs of one site |
Prompt: index_url checks a URL, queues a request when it is not indexed, and reports the ETA as it is.
Keys and safety
request_indexingpreviews before it queues. It asks you before a re-index of a page that is already on Google, a URL that is not in your sitemap, or your site's last request of the day; declining queues nothing. Clients that can ask their user (MCP elicitation) show the question themselves, and your answer never passes through the model; a question that gets no answer queues nothing either. Clients that cannot ask, and on the remote server clients on an MCP protocol before 2026-07-28, get a refusal first, with the reasons and aconfirmtoken: an HMAC under your API key that fits only that request, on that day, while your site's quota stays as it was. The model cannot make one up, so a call always takes the refusal first. Whether your assistant then shows you the reasons before it sends the token back is up to the assistant and to your client's approval of tool calls; the server cannot see it.submit_indexnowdoes the same above 10 URLs, with a token for those URLs on that Pacific day.cancel_indexing_requestis marked destructive (destructiveHint: true), and no other tool is: it undoes a request. The tools that only read are marked read-only, so clients can run them without asking.- The
npxpackage reads the key from its environment and sends it only tohttps://api.indexmachine.co.INDEXMACHINE_API_URLmay point it to a local development server, and nowhere else. - A read-only key fits an assistant that only checks: sites, pages, URL checks and requests.
- Every call carries a request id that starts with
mcp-. Revoke a key on the Settings page at any time. - Report a vulnerability by email to vlad@indexmachine.co, not in a public issue (SECURITY.md).
Development
npm install
npm test # unit, contract and protocol tests (it builds dist/ first)
npm run build
npm run sync:openapi # refresh openapi/v1.json and src/v1.d.ts from https://api.indexmachine.co/v1/openapi.json
npm run check:pack # pack, install in an empty folder, run the stdio handshake
npm run release:check # what a release needs, then the publishing commands
openapi/v1.json is the /v1 contract, and the API serves the same document at /v1/openapi.json. When
the API ships a new release, npm run sync:openapi and npm test show which new operations need a tool or
a line in EXCLUDED (src/tools/index.ts).
The remote server deploys to Vercel (vercel.json, api/) under the domain mcp.indexmachine.co.
OAuth turns on with MCP_OAUTH=1 and MCP_OAUTH_KEYS, the keys IndexMachine's API encrypts its access
tokens with.
License
MIT
IndexMachine MCP questions
How do I add IndexMachine MCP to Claude Code?
Run claude mcp add --env 'INDEXMACHINE_API_KEY=<YOUR_INDEXMACHINE_API_KEY>' indexmachine-mcp -- npx -y indexmachine-mcp in your terminal. Add --scope user to make it available in every project.
How do I add IndexMachine MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does IndexMachine MCP provide?
It exposes 10 tools, including account_status, list_sites, site_summary, list_pages, check_url.
How does the Google indexing request work?
The server queues a request that is picked up by the IndexMachine Chrome extension, which then clicks the 'Request indexing' button in your Google Search Console.
Is the indexing request instant?
No, the request is not instant and depends on when the Chrome extension checks in and Google's processing time.
Can I re-index a page that is already indexed?
Yes, you can perform a re-index of an already indexed page by using the force: true parameter, provided you have extension 1.2.0 or newer.