# SpeedyIndex (npm · speedyindex-mcp)

Google, Bing and Yandex index checks, link indexing, backlink checks and Google Rank Tracker.

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.speedyindex.com`: 39/100, [markdown](https://verifymcp.io/servers/uskotoivo81-netizen-speedyindex/mcp.md), [page](https://verifymcp.io/servers/uskotoivo81-netizen-speedyindex/mcp)
- npm · `speedyindex-mcp`: 81/100 (this document), [markdown](https://verifymcp.io/servers/uskotoivo81-netizen-speedyindex/speedyindex-mcp.md), [page](https://verifymcp.io/servers/uskotoivo81-netizen-speedyindex/speedyindex-mcp)

## Channel facts

- Registry: `npm`
- Package: `speedyindex-mcp`
- Version: `0.1.2`
- 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-21.

- **Supply Chain Security**: 98/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.
  - 31 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to uskotoivo81-netizen/speedyindex-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 9 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 800 tokens (~57/item across 14 items; 14 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 74/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 22% 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

SpeedyIndex runs locally as an npm package, launched with npx -y speedyindex-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 uskotoivo81-netizen-speedyindex -- npx -y speedyindex-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "uskotoivo81-netizen-speedyindex": {
      "command": "npx",
      "args": [
        "-y",
        "speedyindex-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "uskotoivo81-netizen-speedyindex": {
      "command": "npx",
      "args": [
        "-y",
        "speedyindex-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add uskotoivo81-netizen-speedyindex -- npx -y speedyindex-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add uskotoivo81-netizen-speedyindex --command npx --arg -y --arg speedyindex-mcp
```

### Hermes

```yaml
mcp_servers:
  uskotoivo81-netizen-speedyindex:
    command: "npx"
    args: ["-y", "speedyindex-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "uskotoivo81-netizen-speedyindex": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "speedyindex-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add uskotoivo81-netizen-speedyindex -t stdio -c npx -a -y speedyindex-mcp
```

### Other

```json
{
  "mcpServers": {
    "uskotoivo81-netizen-speedyindex": {
      "command": "npx",
      "args": [
        "-y",
        "speedyindex-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-20 (score 81, +1)

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

### 2026-11-18 (score 80, +1)

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

### 2026-11-16 (score 79, +1)

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

### 2026-11-14 (score 78, +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-12 (score 77, 0)

- [functional] Package version: 0.1.0 → 0.1.2

### 2026-11-11 (score 77, +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.

### 2026-11-10 (score 76, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-09 (score 76)

First indexed and scored.

## MCP tools (14)

### `get_balance` (~22 tokens)

Account balance

SpeedyIndex balance: tokens, indexer credits and checker credits.

### `check_index` (~77 tokens)

Check if URLs are indexed

Create an index-check task in Google, Bing or Yandex for a list of URLs. Uses checker credits. Returns task_id; read the result with get_report once the task is processed.

Input parameters:

- `engine` (string): Search engine
- `title` (string)
- `urls` (array, required): URLs, up to 10,000

### `submit_for_indexing` (~94 tokens)

Submit URLs for indexing

Create an indexing task in Google or Yandex. Spends the user's balance (Google: pay-per-indexed mode). Ask the user before calling. drip_feed_days (2-30, Google only) spreads submissions over days.

Input parameters:

- `drip_feed_days` (integer)
- `engine` (string)
- `title` (string)
- `urls` (array, required): URLs, up to 10,000

### `list_tasks` (~60 tokens)

List tasks

Recent indexing or index-check tasks, newest first, with size, processed and indexed counts.

Input parameters:

- `engine` (string): Search engine
- `page` (integer)
- `task_type` (string): checker = index check, indexer = indexing task

### `get_report` (~81 tokens)

Task report

Indexed and unindexed URLs of a task. full=true adds SERP titles and error codes (-1 noindex, 0 none, else HTTP status).

Input parameters:

- `engine` (string): Search engine
- `full` (boolean)
- `task_id` (string, required)
- `task_type` (string): checker = index check, indexer = indexing task

### `check_backlinks` (~61 tokens)

Check backlinks on donor pages

Check donor pages for links to the given domains (anchors, rel, indexing). Spends tokens. Returns task_id for get_backlink_report.

Input parameters:

- `target_domains` (array, required)
- `urls` (array, required): URLs, up to 10,000

### `get_backlink_report` (~54 tokens)

Backlink check report

Per-donor results of a backlink check task: DA, spam score, indexing status and the links found.

Input parameters:

- `limit` (integer)
- `page` (integer)
- `task_id` (string, required)

### `rank_projects` (~36 tokens)

Rank Tracker projects

List Rank Tracker projects (domain, regions, schedule, last check).

Input parameters:

- `max` (integer)
- `search` (string)

### `rank_positions` (~85 tokens)

Keyword positions

Google positions of a project's keywords in a check (latest finished by default), with the change against the previous check. changed_only returns only keywords that moved.

Input parameters:

- `changed_only` (boolean)
- `check_id` (string)
- `max` (integer)
- `project_id` (string, required)
- `region_id` (string)
- `tag` (string)

### `rank_keyword_details` (~61 tokens)

Keyword in a check: top 10 and AI Overview

One keyword's result in a finished check: top-10 domains and the AI Overview (present, whether the site is cited, sources).

Input parameters:

- `check_id` (string, required)
- `keyword_id` (string, required)
- `region_id` (string)

### `rank_cost` (~36 tokens)

Cost of the next check

What the project's next position check can cost, in tokens (cost.max is held while it runs).

Input parameters:

- `project_id` (string, required)

### `rank_run_check` (~53 tokens)

Run a position check

Queue a Google position check for a project. Spends tokens: call rank_cost and ask the user first. Poll with rank_check_status.

Input parameters:

- `project_id` (string, required)
- `region_id` (string)

### `rank_check_status` (~34 tokens)

Check status

Status and progress of a Rank Tracker check (queued, running, done, failed).

Input parameters:

- `check_id` (string, required)

### `rank_locations` (~46 tokens)

Find a Google location

Find a city, region or country for a Rank Tracker region; use canonical_name as location and country_code as gl.

Input parameters:

- `gl` (string)
- `q` (string, required)

## Diagnostics

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

## Score history

- 2026-11-21: 81
- 2026-11-20: 81
- 2026-11-19: 80
- 2026-11-18: 80
- 2026-11-17: 79
- 2026-11-16: 79
- 2026-11-15: 78
- 2026-11-14: 78
- 2026-11-13: 77
- 2026-11-12: 77
- 2026-11-11: 77
- 2026-11-10: 76
- 2026-11-09: 76

## Common questions

### What is the SpeedyIndex MCP server?

SpeedyIndex is an MCP server listed in the public MCP registry as io.github.uskotoivo81-netizen/speedyindex. Google, Bing and Yandex index checks, link indexing, backlink checks and Google Rank Tracker. This page covers its npm package (speedyindex-mcp).

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

SpeedyIndex scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 SpeedyIndex MCP server expose?

SpeedyIndex exposes 14 tools: get_balance, check_index, submit_for_indexing, list_tasks, get_report, and 9 more. Their descriptions and schemas cost roughly 800 tokens of context every time the server is loaded.

### Is the SpeedyIndex MCP server still maintained?

SpeedyIndex is still listed as active in the MCP registry. We last reached this channel on 21 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 SpeedyIndex MCP server under?

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

### What did VerifyMCP test on the SpeedyIndex MCP server?

VerifyMCP ran 16 checks on SpeedyIndex, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/speedyindex-mcp
- Socket report: https://socket.dev/npm/package/speedyindex-mcp
- Repository: https://github.com/uskotoivo81-netizen/speedyindex-mcp
- Website: https://en.speedyindex.com/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/uskotoivo81-netizen-speedyindex/speedyindex-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/uskotoivo81-netizen-speedyindex/speedyindex-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/uskotoivo81-netizen-speedyindex/speedyindex-mcp.json
- HTML version of this page: https://verifymcp.io/servers/uskotoivo81-netizen-speedyindex/speedyindex-mcp
