Skip to content

IndexMachine MCP server

co.indexmachine/mcpindexmachine.costreamable-httpv0.1.0Scanned

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

10 tools: 1 can delete or cancel things, 1 do something that can't be undone, 3 change things and 5 only read.

Tools: 1 delete, 1 irreversible, 3 write, 5 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 3
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the IndexMachine MCP server can do

The IndexMachine MCP server is published by indexmachine.co, a domain the MCP Registry verified. It has 10 tools. It can delete or cancel things (1 tool: cancel_indexing_request), do things that cannot be undone, such as sending, paying or publishing (submit_indexnow) and create or change data (3 tools: site_summary, check_url and request_indexing). 5 tools only read.

4 tools bring in text other people can write (list_pages, check_url, request_indexing and 1 more); 3 tools can send data out of your system (check_url, request_indexing and submit_indexnow).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 13, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

10 tools

Deletes or cancels 1Claude Code: deny
  • cancel_indexing_requestTakes an open indexing request out of the queue, so the extension never performs it.No findings

    Why it is in this group

    • The name "cancel_indexing_request" says "cancel": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Cancel an indexing request
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Can't be undone 1Claude Code: ask
  • submit_indexnowNotifies 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.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "submit_indexnow" says "submit": a word for a change.
    • The description's first verb is "notify": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "crawl": it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.urls): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Submit URLs to IndexNow
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 3Claude Code: ask
  • check_urlWhether 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 f…Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check a URL on Google
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • request_indexingQueues 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.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "request_indexing" says "request": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Request indexing
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • site_summaryOne 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 co…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Read one site
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
Only reads 5Show 5 read-only tools
  • account_statusThe 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 reques…No findings

    Why it is in this group

    • The name "account_status" says "status": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Account and extension status
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_indexing_requestOne indexing request: its status, queue position and ETA in eta_text while open, and what Search Console answered once the extension performed it.No findings

    Why it is in this group

    • The name "get_indexing_request" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Read an indexing request
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_indexing_requestsIndexing 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.No findings

    Why it is in this group

    • The name "list_indexing_requests" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List indexing requests
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_pagesA site's pages by path, with their status, Google's coverage state and the last crawl and request.Reads text others writeNo findings

    Why it is in this group

    • The name "list_pages" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "crawl": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List a site's pages
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_sitesEvery 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…No findings

    Why it is in this group

    • The name "list_sites" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List sites
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:21 UTC, unchanged since Oct 31, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.indexmachine.co/.well-known/oauth-protected-resource/mcp
Authorization servers
https://api.indexmachine.co
Legacy HTTP+SSE transport
no
Dynamic client registration
no
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (1 destructive, 1 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.indexmachine.co/mcp: tools/list returned 10 tools to an anonymous client, including cancel_indexing_request (destructive), submit_indexnow (irreversible), site_summary (write), check_url (write), request_indexing (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http indexmachine https://mcp.indexmachine.co/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http indexmachine https://mcp.indexmachine.co/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__indexmachine__account_status",
      "mcp__indexmachine__list_sites",
      "mcp__indexmachine__list_pages",
      "mcp__indexmachine__get_indexing_request",
      "mcp__indexmachine__list_indexing_requests"
    ],
    "ask": [
      "mcp__indexmachine__site_summary",
      "mcp__indexmachine__check_url",
      "mcp__indexmachine__request_indexing",
      "mcp__indexmachine__submit_indexnow"
    ],
    "deny": [
      "mcp__indexmachine__cancel_indexing_request"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as indexmachine. Review it before you use it.

Capability tags behind 4 rules
  • mcp__indexmachine__list_pages untrusted-input
  • mcp__indexmachine__check_url untrusted-input, outbound
  • mcp__indexmachine__request_indexing untrusted-input, outbound
  • mcp__indexmachine__submit_indexnow untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/co.indexmachine/mcp/verify?hash=d1eaccbe280d5716aaeae8eac342b4466379afefc0a334fc49ad5ec2b9044366" | jq -e '.changed == false'

Pinned hash d1eaccbe280d, from Nov 13, 2026, 14:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/co.indexmachine/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for co.indexmachine/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/co.indexmachine/mcp.svg)](https://radar.anlyon.com/servers/co.indexmachine/mcp)

Source: MCP Registry · repository. Synced Oct 31, 2026, 18:17 UTC.

IndexMachine MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the IndexMachine MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the IndexMachine MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: cancel_indexing_request.

Can the IndexMachine MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: submit_indexnow.

What tools does the IndexMachine MCP server have?

10 tools: 1 destructive, 1 irreversible, 3 write, 5 read. cancel_indexing_request, submit_indexnow, site_summary, check_url, request_indexing, account_status, list_sites, list_pages and 2 more.

Does the IndexMachine MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the IndexMachine MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_url, request_indexing and submit_indexnow.

Has the IndexMachine MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.