# IndexMachine (npm · indexmachine-mcp)

Check your own sites' pages on Google and request indexing, plus IndexNow, from your AI assistant.

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.indexmachine.co`: 83/100, [markdown](https://verifymcp.io/servers/co-indexmachine-mcp/mcp.md), [page](https://verifymcp.io/servers/co-indexmachine-mcp/mcp)
- npm · `indexmachine-mcp`: 74/100 (this document), [markdown](https://verifymcp.io/servers/co-indexmachine-mcp/indexmachine-mcp.md), [page](https://verifymcp.io/servers/co-indexmachine-mcp/indexmachine-mcp)

## Channel facts

- Registry: `npm`
- Package: `indexmachine-mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 0 of 3 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1541 tokens (~154/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the IndexMachine MCP server?

IndexMachine runs locally as an npm package, launched with npx -y indexmachine-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add co-indexmachine-mcp -- npx -y indexmachine-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "co-indexmachine-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "indexmachine-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-indexmachine-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "indexmachine-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add co-indexmachine-mcp -- npx -y indexmachine-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-indexmachine-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "indexmachine-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-indexmachine-mcp --command npx --arg -y --arg indexmachine-mcp
```

### Hermes

```yaml
mcp_servers:
  co-indexmachine-mcp:
    command: "npx"
    args: ["-y", "indexmachine-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "co-indexmachine-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "indexmachine-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-indexmachine-mcp -t stdio -c npx -a -y indexmachine-mcp
```

### Other

```json
{
  "mcpServers": {
    "co-indexmachine-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "indexmachine-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-04 (score 73, +1)

- [functional improvement] Stability: unverified → 0.13

### 2026-11-01 (score 72, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 57)

First indexed and scored.

## MCP tools (10)

### `account_status` (~78 tokens)

Account and extension 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.

Input parameters:

- `tz` (string): IANA time zone for today's counts, such as Europe/Berlin; UTC by default

### `list_sites` (~61 tokens)

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.

### `site_summary` (~75 tokens)

Read one site

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.

Input parameters:

- `site` (string, required): The site: its id (a UUID) or its domain, such as example.com

### `list_pages` (~142 tokens)

List a site's 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.

Input parameters:

- `cursor` (string): next_cursor from the previous page
- `limit` (integer): Rows to return, 25 by default, 50 at most
- `q` (string): Part of the URL
- `site` (string, required): The site: its id (a UUID) or its domain, such as example.com
- `status` (string)

### `check_url` (~139 tokens)

Check a URL on Google

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.

Input parameters:

- `live` (boolean): Ask Google now; uses 1 of the site's 50 live checks a day
- `url` (string, required): A whole http or https URL of one of the user's sites

### `request_indexing` (~248 tokens)

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. Clients that can ask their user (MCP elicitation) get a question to confirm, and the answer does not pass through the model; with other clients the tool refuses first with a confirm token, and the call with that token stands for the user's yes.

Input parameters:

- `confirm` (string): The confirm token from this tool's refusal, once the user agreed
- `force` (boolean): Request a re-index of a page that is already indexed
- `url` (string, required): A whole http or https URL of one of the user's sites

### `get_indexing_request` (~73 tokens)

Read an 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.

Input parameters:

- `request_id` (string, required): The indexing request's id

### `list_indexing_requests` (~119 tokens)

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.

Input parameters:

- `cursor` (string): next_cursor from the previous page
- `limit` (integer): Rows to return, 25 by default, 50 at most
- `site` (string): The site: its id (a UUID) or its domain, such as example.com
- `status` (string)

### `cancel_indexing_request` (~54 tokens)

Cancel an 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.

Input parameters:

- `request_id` (string, required): The indexing request's id

### `submit_indexnow` (~201 tokens)

Submit URLs to 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. Clients that can ask their user (MCP elicitation) get a question to confirm, and the answer does not pass through the model; with other clients the tool refuses first with a confirm token, and the call with that token stands for the user's yes.

Input parameters:

- `confirm` (string): The confirm token from this tool's refusal, once the user agreed
- `site` (string, required): The site: its id (a UUID) or its domain, such as example.com
- `urls` (array, required): URLs of this site, 100 at most

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/co-indexmachine-mcp/indexmachine-mcp#diagnostics

## Score history

- 2026-11-05: 74
- 2026-11-04: 73
- 2026-11-03: 72
- 2026-11-02: 72
- 2026-11-01: 72
- 2026-10-31: 57

## Common questions

### What is the IndexMachine MCP server?

IndexMachine is an MCP server listed in the public MCP registry as co.indexmachine/mcp. Check your own sites' pages on Google and request indexing, plus IndexNow, from your AI assistant. This page covers its npm package (indexmachine-mcp).

### Is the IndexMachine MCP server safe to use?

IndexMachine scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the IndexMachine MCP server expose?

IndexMachine exposes 10 tools: account_status, list_sites, site_summary, list_pages, check_url, and 5 more. Their descriptions and schemas cost roughly 1,190 tokens of context every time the server is loaded.

### Is the IndexMachine MCP server still maintained?

IndexMachine is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the IndexMachine MCP server under?

IndexMachine declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/indexmachine-mcp
- Socket report: https://socket.dev/npm/package/indexmachine-mcp
- Repository: https://github.com/indexmachine/indexmachine-mcp
- Website: https://indexmachine.co/
- Changelog RSS feed: https://verifymcp.io/servers/co-indexmachine-mcp/indexmachine-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-indexmachine-mcp/indexmachine-mcp.json
- HTML version of this page: https://verifymcp.io/servers/co-indexmachine-mcp/indexmachine-mcp