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.

io.speedvault/mcp

NPM · @SPEEDVAULT/MCP · SCANNED SEP 24

Run web performance audits, get code-level fixes, crawl for SEO, and read real-user Core Web Vitals.

Available components

0 this week 79 Trust /100
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 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability88
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1950 tokens (~97/item across 20 items; 18 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 20 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
Install

How do I install the io.speedvault/mcp server?

io.speedvault/mcp runs locally as an npm package, launched with npx -y @speedvault/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 · @speedvault/mcp

# add to Claude Code
claude mcp add io-speedvault-mcp -- npx -y @speedvault/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "io-speedvault-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@speedvault/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-speedvault-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@speedvault/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add io-speedvault-mcp -- npx -y @speedvault/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-speedvault-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@speedvault/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-speedvault-mcp --command npx --arg -y --arg @speedvault/mcp
# ~/.hermes/config.yaml
mcp_servers:
  io-speedvault-mcp:
    command: "npx"
    args: ["-y", "@speedvault/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-speedvault-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@speedvault/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add io-speedvault-mcp -t stdio -c npx -a -y @speedvault/mcp
// mcp.json
{
  "mcpServers": {
    "io-speedvault-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@speedvault/mcp"
      ]
    }
  }
}
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.

  • 24 Sept 26 +1

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

  • 23 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 22 Sept 26 0
    • Stability: 0.97 → pass security
  • 21 Sept 26 +1

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

  • 19 Sept 26 +1

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

  • 17 Sept 26 +1

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

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
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 24 Sept 2026 · Analysed npm/@speedvault/mcp@1.0.3

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 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 18 exposed · ~1,773 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 ~25

Show your plan, remaining API credits, rate limit, and per-product entitlements.

Input schema present but exposes no named parameters.

NameTypeReqDescription
apiCreditsRemainingnumber|null–Remaining API credits.
entitlementsobject–Per-product entitlements (Metrix, AI Fixes, Audit/Crawl, RUM, Monitor).
planstring–The account plan name.
rateLimitobject–Rate limit: requests per window.

No examples provided.

add_domain ~85

Register a new domain. Returns a verification token and instructions (meta tag or DNS TXT record). After adding, call verify_domain to prove ownership. A verified domain is required before you can crawl, monitor, or add RUM.

NameTypeReqDescription
domainstringyesThe domain to add, e.g. "example.com".
labelstring–An optional label for the domain.
NameTypeReqDescription
domainstring–The registered domain.
domainIdstring–The id of the registered domain; pass to verify_domain.
instructionsobject–Ownership-proof options: a meta tag and a DNS TXT record.
statusstring–Verification status (e.g. pending).

No examples provided.

compare_runs ~94

Return a structured diff of two completed audits: delta per metric (perf_score, LCP, FCP, TBT, CLS, SI, page_bytes, total_requests) with improved/regressed flags. Use this to see how a change affected performance before and after.

NameTypeReqDescription
auditId1stringyesThe first (before) audit id.
auditId2stringyesThe second (after) audit id.
NameTypeReqDescription
auditId1stringyesThe first (before) audit id.
auditId2stringyesThe second (after) audit id.
metricsobject–Per-metric diff (perf_score, lcp, fcp, tbt, cls, speed_index, page_bytes, total_requests, …).
urlAstring–URL of the first audit.
urlBstring–URL of the second audit.

No examples provided.

crawl_site ~159

Start a full-site crawl that aggregates SEO + structure issues across pages (grouped by category/template) and computes a site score. Costs 1 credit. Returns a crawlId; poll with get_crawl (wait=true) to get the grouped issues once it finishes. NOTE: the domain must be verified first — use list_domains / add_domain / verify_domain.

NameTypeReqDescription
maxPagesinteger–Cap pages crawled (clamped to your plan).
timeoutinteger–Max seconds to wait when wait=true (default 120).
urlstringyesThe site root or any page on the site to crawl from.
waitboolean–Wait for completion and return grouped issues (default false; crawls can be long).
NameTypeReqDescription
crawlIdstring–The crawl id; poll with get_crawl.
issuesobject–Issue counts by severity.
pagesCrawlednumber–Number of pages crawled.
scorenumber|null–Aggregate site score 0–100.
statusstring–Crawl status: crawling, done, or error.
templatesarray–Per-template issue breakdown (most-affected first).
urlstring–The site/page the crawl started from.

No examples provided.

create_monitor ~172

Add a URL to scheduled monitoring so SpeedVault re-audits it on a cadence and tracks regressions. Slot-limited by plan. NOTE: the domain must be verified first — use list_domains / add_domain / verify_domain.

NameTypeReqDescription
checkFrequencystring–How often to re-audit the URL (default daily).
devicestring–Emulated device for the scheduled audit (default desktop).
labelstring–An optional human-friendly label for this monitor (e.g. "Pricing page").
locationstring–Test region for the scheduled audit, e.g. "eu-west", "us-east", "ap-southeast".
urlstringyesThe absolute URL to monitor, e.g. https://example.com/pricing. Its domain must be verified first.
NameTypeReqDescription
checkFrequencystring–The cadence the monitor runs at.
monitorIdstring–The id of the newly created monitor.
urlstring–The URL now under monitoring.

No examples provided.

get_audit ~78

Fetch a previously-started audit by id. Set wait=true to block until it completes.

NameTypeReqDescription
auditIdstringyesThe audit id returned by run_audit.
timeoutinteger–Max seconds to wait when wait=true (default 120).
waitboolean–Block until the audit completes before returning (default false).
NameTypeReqDescription
auditIdstring–The audit id.
clsnumber|null–Cumulative Layout Shift (unitless).
fcpMsnumber|null–First Contentful Paint in milliseconds.
lcpMsnumber|null–Largest Contentful Paint in milliseconds.
pageBytesnumber|null–Total page weight in bytes.
performanceScorenumber|null–Lighthouse performance score 0–100.
requestsnumber|null–Total number of network requests.
speedIndexMsnumber|null–Speed Index in milliseconds.
statestring–Audit state: queued, running, complete, or error.
structureScorenumber|null–Structure (best-practices) score 0–100.
tbtMsnumber|null–Total Blocking Time in milliseconds.
topOpportunitiesarray–Top prioritized improvement opportunities.
urlstring–The URL that was audited.

No examples provided.

get_crawl ~82

Fetch a crawl by id with its score and grouped issues. wait=true blocks until done.

NameTypeReqDescription
crawlIdstringyesThe crawl id returned by crawl_site (or recheck_template).
timeoutinteger–Max seconds to wait when wait=true (default 120).
waitboolean–Block until the crawl completes before returning (default false).
NameTypeReqDescription
crawlIdstring–The crawl id; poll with get_crawl.
issuesobject–Issue counts by severity.
pagesCrawlednumber–Number of pages crawled.
scorenumber|null–Aggregate site score 0–100.
statusstring–Crawl status: crawling, done, or error.
templatesarray–Per-template issue breakdown (most-affected first).
urlstring–The site/page the crawl started from.

No examples provided.

get_fix_suggestions ~223

Return prioritized, ACTIONABLE fixes. Two modes: • Performance: pass auditId (a completed run_audit). Each fix has the issue, impact, how to fix it, a code snippet where useful, and estimated savings. • SEO/media: pass crawlId (a completed crawl_site), optionally narrowed with issue_type (e.g. "description-missing", "next-gen-images", "image-alt-missing"). Each fix reports how many pages are affected, example URLs, how to fix it, and a ready-to-apply snippet (e.g. <picture>/WebP, <meta name="description">, alt="", unique <title>). This is what you apply to improve scores. Cached perf fixes are free; a fresh AI generation may cost credits.

NameTypeReqDescription
auditIdstring–A completed audit id (performance fixes).
crawlIdstring–A completed crawl id (site-wide SEO + media fixes).
issue_typestring–With crawlId: target one issue group, e.g. "next-gen-images".
NameTypeReqDescription
auditIdstring–The audit id (performance mode).
countnumberyesNumber of fixes returned.
crawlIdstring–The crawl id (SEO/media mode).
fixesarrayyesThe actionable fixes to apply.
issueTypestring–The issue_type filter that was applied (SEO mode).
modestringyesWhich fix mode produced these results.
notestring–An optional note when no fixes are available.
sourcestring–Where the fixes came from (e.g. cache or ai).

No examples provided.

get_rum ~116

Return field (real-user) Core Web Vitals for a registered RUM site: p75 LCP/INP/CLS/FCP/TTFB with ratings, sample counts, and trends. Use list of sites from account first if you do not know the siteKey (call get_rum with no siteKey to list sites).

NameTypeReqDescription
daysinteger–Look-back window in days (default 7).
siteKeystring–The RUM site key. Omit to list your RUM sites instead.
NameTypeReqDescription
metricsobject–Field Core Web Vitals keyed by metric (lcp, inp, cls, fcp, ttfb) with p75 + sample count.
modestringyesWhether a site list or a single-site summary was returned.
siteKeystring–The RUM site key (summary mode).
sitesarray–Registered RUM sites (list mode).
totalSamplesnumber–Total real-user samples in the window.
windowDaysnumber–Look-back window in days (summary mode).

No examples provided.

get_rum_embed ~66

Return the <script> beacon snippet to install SpeedVault RUM on a site, so an agent building an app can wire up real-user Core Web Vitals collection. Paste it into the <head>.

NameTypeReqDescription
siteKeystringyesThe RUM site key to install.
NameTypeReqDescription
instructionsstring–Human-readable install instructions.
siteKeystringyesThe RUM site key the snippet is for.
snippetstring–The <script> beacon snippet to paste into <head>.

No examples provided.

get_seo_fixes ~97

Return actionable fix recipes for a completed site crawl. Each fix includes the issue, impact, how to fix it, a code snippet, and before/after showing the exact code change. Optionally narrow to one issue_type (e.g. "description-missing", "next-gen-images").

NameTypeReqDescription
crawlIdstringyesA completed crawl id from crawl_site.
issue_typestring–Narrow to one issue type.
NameTypeReqDescription
countnumberyesNumber of fixes returned.
crawlIdstringyesThe crawl id these fixes belong to.
fixesarrayyesThe SEO fix recipes (with before/after where available).
issueTypestring–The issue_type filter that was applied, if any.

No examples provided.

get_seo_issues ~93

Return the per-template issue breakdown from a completed site crawl. Shows each template (e.g. /products/:slug) with its page count and the SEO issues affecting it, including prevalence ("142 of 312 product pages have missing meta description") and priority scores. Use this after crawl_site to understand which templates need the most work.

NameTypeReqDescription
crawlIdstringyesA completed crawl id from crawl_site.
NameTypeReqDescription
countnumberyesNumber of templates returned.
crawlIdstringyesThe crawl id these templates belong to.
templatesarrayyesPer-template issue breakdown.

No examples provided.

list_audits ~38

List the most recent audits run via the API for this account.

NameTypeReqDescription
limitinteger–How many to return (default 25).
NameTypeReqDescription
auditsarrayyesRecent audits with id, URL, state, and performance score.
countnumberyesNumber of audits returned.

No examples provided.

list_domains ~46

List your domains with their verification status and linked product counts (RUM sites, monitors, analyses). Domains must be verified before you can crawl, monitor, or add RUM to them.

Input schema present but exposes no named parameters.

NameTypeReqDescription
countnumberyesNumber of domains returned.
domainsarrayyesDomains with verification status and linked product counts.

No examples provided.

list_monitors ~25

List the URLs under scheduled monitoring (SpeedVault Monitor) with their latest score.

Input schema present but exposes no named parameters.

NameTypeReqDescription
countnumberyesNumber of monitors returned.
monitorsarrayyesScheduled monitors with id, URL, cadence, and latest score.

No examples provided.

recheck_template ~102

Trigger a re-crawl of a site that was previously crawled. Use this after applying SEO fixes from get_seo_fixes to verify improvements. Returns a new crawlId. Costs 1 credit.

NameTypeReqDescription
crawlIdstringyesThe original crawl id to re-crawl.
timeoutinteger–Max seconds to wait when wait=true (default 120).
waitboolean–Wait for the re-crawl to complete (default false).
NameTypeReqDescription
crawlIdstring–The NEW crawl id created by the re-crawl.
pagesCrawlednumber–Number of pages crawled (once done).
scorenumber|null–Aggregate site score 0–100 (once done).
statusstring–Crawl status: crawling, done, or error.
templatesarray–Per-template issue breakdown (once done).
urlstring–The site/page being re-crawled.

No examples provided.

run_audit ~211

Run a single-page Lighthouse performance audit on a URL and (by default) wait for it to complete, returning scores (performance/structure), Core Web Vitals (LCP/FCP/TBT/CLS/SI), page weight, and the top prioritized opportunities. Use this on the page you just built or changed. Costs 1 credit. After this, call get_fix_suggestions with the returned auditId for concrete code fixes.

NameTypeReqDescription
connectionstring–Connection throttling preset. Omit to use the device default.
devicestring–Emulated device (default desktop).
locationstring–Test region: eu-west (Ireland, default), us-east (Virginia), ap-southeast (Singapore).
timeoutinteger–Max seconds to wait when wait=true (default 120).
urlstringyesThe absolute URL to audit, e.g. https://example.com/pricing
waitboolean–Block until the audit finishes (default true).
NameTypeReqDescription
auditIdstring–The audit id; pass to get_fix_suggestions / get_audit / compare_runs.
clsnumber|null–Cumulative Layout Shift (unitless).
fcpMsnumber|null–First Contentful Paint in milliseconds.
lcpMsnumber|null–Largest Contentful Paint in milliseconds.
pageBytesnumber|null–Total page weight in bytes.
performanceScorenumber|null–Lighthouse performance score 0–100.
requestsnumber|null–Total number of network requests.
speedIndexMsnumber|null–Speed Index in milliseconds.
statestring–Audit state: queued, running, complete, or error.
structureScorenumber|null–Structure (best-practices) score 0–100.
tbtMsnumber|null–Total Blocking Time in milliseconds.
timedOutboolean–True if the wait window elapsed before completion.
topOpportunitiesarray–Top prioritized improvement opportunities.
urlstring–The URL that was audited.

No examples provided.

verify_domain ~61

Verify ownership of a registered domain by checking for the meta tag or DNS TXT record. On success the domain becomes "active" and you can use it with all SpeedVault products.

NameTypeReqDescription
domainIdstringyesThe domain id from list_domains or add_domain.
NameTypeReqDescription
instructionsobject–Ownership-proof options to retry with if verification failed.
methodstring–The method that verified ownership (meta_tag or dns_txt).
statusstring–Resulting domain status (active when verified).
verifiedboolean–True if ownership was confirmed.

No examples provided.

Common questions

What is the io.speedvault/mcp server?

io.speedvault/mcp is listed in the public MCP registry as io.speedvault/mcp. Run web performance audits, get code-level fixes, crawl for SEO, and read real-user Core Web Vitals. This page covers its npm package (@speedvault/mcp).

Is the io.speedvault/mcp server safe to use?

io.speedvault/mcp scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 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 io.speedvault/mcp server expose?

io.speedvault/mcp exposes 18 tools: run_audit, get_audit, list_audits, get_fix_suggestions, crawl_site, and 13 more. Their descriptions and schemas cost roughly 1,773 tokens of context every time the server is loaded.

Is the io.speedvault/mcp server still maintained?

io.speedvault/mcp is still listed as active in the MCP registry. We last reached this channel on 24 September 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 io.speedvault/mcp server under?

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