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.

SpeedyIndex

NPM · SPEEDYINDEX-MCP · 2 COMPONENTS

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

+3 this week 81 Trust /100

Last scanned (13 hours ago)

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

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

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

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

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

  • 14 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.

  • 12 Nov 26 0
    • Package version: 0.1.0 → 0.1.2 functional
  • 11 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.

  • 10 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 9 Nov 26 76

    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 21 Nov 2026 · Analysed npm/speedyindex-mcp@0.1.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo uskotoivo81-netizen/speedyindex-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/uskotoivo81-netizen/speedyindex-mcp/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3825593384
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:10fc1b71a2cd889f2ca1904322648f40d813532308e9d559e43b50f0ee87b363bff42b527d7a63cdcb9ede89fdef6ca8e2d68717ab53ed39519a90fb4

Background: How many MCP packages publish verified provenance →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 14 exposed · ~800 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
check_backlinks ~61

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

NameTypeReqDescription
target_domainsarrayyes–
urlsarrayyesURLs, up to 10,000

No output schema declared.

No examples provided.

check_index ~77

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.

NameTypeReqDescription
enginestring–Search engine
titlestring––
urlsarrayyesURLs, up to 10,000

No output schema declared.

No examples provided.

get_backlink_report ~54

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

NameTypeReqDescription
limitinteger––
pageinteger––
task_idstringyes–

No output schema declared.

No examples provided.

get_balance ~22

SpeedyIndex balance: tokens, indexer credits and checker credits.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_report ~81

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

NameTypeReqDescription
enginestring–Search engine
fullboolean––
task_idstringyes–
task_typestring–checker = index check, indexer = indexing task

No output schema declared.

No examples provided.

list_tasks ~60

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

NameTypeReqDescription
enginestring–Search engine
pageinteger––
task_typestring–checker = index check, indexer = indexing task

No output schema declared.

No examples provided.

rank_check_status ~34

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

NameTypeReqDescription
check_idstringyes–

No output schema declared.

No examples provided.

rank_cost ~36

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

NameTypeReqDescription
project_idstringyes–

No output schema declared.

No examples provided.

rank_keyword_details ~61

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

NameTypeReqDescription
check_idstringyes–
keyword_idstringyes–
region_idstring––

No output schema declared.

No examples provided.

rank_locations ~46

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

NameTypeReqDescription
glstring––
qstringyes–

No output schema declared.

No examples provided.

rank_positions ~85

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.

NameTypeReqDescription
changed_onlyboolean––
check_idstring––
maxinteger––
project_idstringyes–
region_idstring––
tagstring––

No output schema declared.

No examples provided.

rank_projects ~36

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

NameTypeReqDescription
maxinteger––
searchstring––

No output schema declared.

No examples provided.

rank_run_check ~53

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

NameTypeReqDescription
project_idstringyes–
region_idstring––

No output schema declared.

No examples provided.

submit_for_indexing ~94

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.

NameTypeReqDescription
drip_feed_daysinteger––
enginestring––
titlestring––
urlsarrayyesURLs, up to 10,000

No output schema declared.

No examples provided.

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.

npm · speedyindex-mcp

# add to Claude Code
claude mcp add uskotoivo81-netizen-speedyindex -- npx -y speedyindex-mcp
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.