IndexMachine
REMOTE · MCP.INDEXMACHINE.CO · 2 COMPONENTS
Check your own sites' pages on Google and request indexing, plus IndexNow, from your AI assistant.
Available components
Last scanned (3 hours ago)
Scores higher than 87% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 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 1581 tokens (~158/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
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.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 81
First indexed and scored.
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 · Probed https://mcp.indexmachine.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.indexmachine.co | CN=YR2,O=Let's Encrypt,C=US | 31 Oct 2026 | 29 Jan 2027 | RSA 2048 | SHA256-RSA | 5b7fb0907ccd2233fe0db3522ac5c50b643 |
| SANs: mcp.indexmachine.co | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.indexmachine.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| indexmachine.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.indexmachine.co/.well-known/oauth-protected-resource/mcp", scope="mcp"
Bearer resource_metadata="https://mcp.indexmachine.co/.well-known/oauth-protected-resource/mcp", scope="mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Protected resource metadata
| Document | https://mcp.indexmachine.co/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.indexmachine.co/mcp |
| Authorisation server | https://api.indexmachine.co |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.indexmachine.co/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.indexmachine.co/mcp | HTTPS enforced | 308 | https://mcp.indexmachine.co/mcp |
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 →
account_status Account and extension 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.
| Name | Type | Req | Description |
|---|---|---|---|
| tz | string | – | IANA time zone for today's counts, such as Europe/Berlin; UTC by default |
No output schema declared.
No examples provided.
cancel_indexing_request Cancel an 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.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | The indexing request's id |
No output schema declared.
No examples provided.
check_url Check a URL on Google ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| live | boolean | – | Ask Google now; uses 1 of the site's 50 live checks a day |
| url | string | yes | A whole http or https URL of one of the user's sites |
No output schema declared.
No examples provided.
get_indexing_request Read an 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.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | The indexing request's id |
No output schema declared.
No examples provided.
list_indexing_requests 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
list_pages List a site's 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The site: its id (a UUID) or its domain, such as example.com |
| status | string | – | – |
No output schema declared.
No examples provided.
list_sites 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 Request indexing ~268
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | A whole http or https URL of one of the user's sites |
No output schema declared.
No examples provided.
site_summary Read one site ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | The site: its id (a UUID) or its domain, such as example.com |
No output schema declared.
No examples provided.
submit_indexnow Submit URLs to IndexNow ~221
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | string | – | The confirm token from this tool's refusal, once the user agreed |
| site | string | yes | The site: its id (a UUID) or its domain, such as example.com |
| urls | array | yes | URLs of this site, 100 at most |
No output schema declared.
No examples provided.
How do I install the IndexMachine MCP server?
IndexMachine is a hosted endpoint at https://mcp.indexmachine.co/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.indexmachine.co
claude mcp add --transport http co-indexmachine-mcp 'https://mcp.indexmachine.co/mcp'
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 hosted endpoint (https://mcp.indexmachine.co/mcp).
Is the IndexMachine MCP server safe to use?
IndexMachine scores 83 out of 100 on VerifyMCP. 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,230 tokens of context every time the server is loaded.
Does the IndexMachine MCP server require authentication?
Yes. IndexMachine asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
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.