Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

IndexMachine

NPM · INDEXMACHINE-MCP · 2 COMPONENTS

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

74 Trust /100

Last scanned (8 hours ago)

Scores higher than 48% of npm servers

Category Marketing and SEO

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 90% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +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.

  • 4 Nov 26 +1
    • Stability: unverified → 0.13 ▲ functional
  • 1 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 57

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/indexmachine-mcp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 3 packages
Packages resolved 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~1,190 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
account_status ~78

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.

NameTypeReqDescription
tzstring–IANA time zone for today's counts, such as Europe/Berlin; UTC by default

No output schema declared.

No examples provided.

cancel_indexing_request ~54

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.

NameTypeReqDescription
request_idstringyesThe indexing request's id

No output schema declared.

No examples provided.

check_url ~139

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.

NameTypeReqDescription
liveboolean–Ask Google now; uses 1 of the site's 50 live checks a day
urlstringyesA whole http or https URL of one of the user's sites

No output schema declared.

No examples provided.

get_indexing_request ~73

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.

NameTypeReqDescription
request_idstringyesThe indexing request's id

No output schema declared.

No examples provided.

list_indexing_requests ~119

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.

NameTypeReqDescription
cursorstring–next_cursor from the previous page
limitinteger–Rows to return, 25 by default, 50 at most
sitestring–The site: its id (a UUID) or its domain, such as example.com
statusstring––

No output schema declared.

No examples provided.

list_pages ~142

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.

NameTypeReqDescription
cursorstring–next_cursor from the previous page
limitinteger–Rows to return, 25 by default, 50 at most
qstring–Part of the URL
sitestringyesThe site: its id (a UUID) or its domain, such as example.com
statusstring––

No output schema declared.

No examples provided.

list_sites ~61

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

request_indexing ~248

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.

NameTypeReqDescription
confirmstring–The confirm token from this tool's refusal, once the user agreed
forceboolean–Request a re-index of a page that is already indexed
urlstringyesA whole http or https URL of one of the user's sites

No output schema declared.

No examples provided.

site_summary ~75

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.

NameTypeReqDescription
sitestringyesThe site: its id (a UUID) or its domain, such as example.com

No output schema declared.

No examples provided.

submit_indexnow ~201

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.

NameTypeReqDescription
confirmstring–The confirm token from this tool's refusal, once the user agreed
sitestringyesThe site: its id (a UUID) or its domain, such as example.com
urlsarrayyesURLs of this site, 100 at most

No output schema declared.

No examples provided.

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.

npm · indexmachine-mcp

# add to Claude Code
claude mcp add co-indexmachine-mcp -- npx -y indexmachine-mcp
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.