# io.github.SeoScoreAPI/seoscoreapi-mcp (npm · seoscoreapi-mcp)

SEO audits, AI readability, accessibility, backlinks and score monitoring from SEO Score API.

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `seoscoreapi-mcp`: 76/100 (this document), [markdown](https://verifymcp.io/servers/seoscoreapi-seoscoreapi-mcp/seoscoreapi-mcp.md), [page](https://verifymcp.io/servers/seoscoreapi-seoscoreapi-mcp/seoscoreapi-mcp)

## Channel facts

- Registry: `npm`
- Package: `seoscoreapi-mcp`
- Version: `1.4.1`
- 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-05.

- **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.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 15 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 3660 tokens (~81/item across 45 items; 45 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 57% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_monitor" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 45 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 io.github.SeoScoreAPI/seoscoreapi-mcp server?

io.github.SeoScoreAPI/seoscoreapi-mcp runs locally as an npm package, launched with npx -y seoscoreapi-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 seoscoreapi-seoscoreapi-mcp -- npx -y seoscoreapi-mcp
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add seoscoreapi-seoscoreapi-mcp -- npx -y seoscoreapi-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add seoscoreapi-seoscoreapi-mcp --command npx --arg -y --arg seoscoreapi-mcp
```

### Hermes

```yaml
mcp_servers:
  seoscoreapi-seoscoreapi-mcp:
    command: "npx"
    args: ["-y", "seoscoreapi-mcp"]
```

### Netclaw

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

### Vellum

```bash
assistant mcp add seoscoreapi-seoscoreapi-mcp -t stdio -c npx -a -y seoscoreapi-mcp
```

### Other

```json
{
  "mcpServers": {
    "seoscoreapi-seoscoreapi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "seoscoreapi-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-05 (score 76, +1)

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

### 2026-11-03 (score 75, +1)

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

### 2026-11-01 (score 74, +1)

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

### 2026-10-29 (score 73, +1)

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

### 2026-10-27 (score 72, +1)

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

### 2026-10-25 (score 71, +1)

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

### 2026-10-23 (score 70, +1)

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

### 2026-10-22 (score 69, +3)

- [functional improvement] Stability: unverified → 0.23

## MCP tools (45)

### `audit` (~205 tokens)

Run a full SEO audit on a URL. Returns score (0-100), letter grade, category breakdowns (meta, technical, social, performance, accessibility), AI readability score, SXO/AEO/AIO scores (paid plans), and a prioritized list of fixes. Usually returns in seconds. Free tier: 2 audits a day. Core Web Vitals (LCP, INP, CLS) are not measured unless include_core_web_vitals is true.

Input parameters:

- `include_core_web_vitals` (boolean): Also measure Core Web Vitals (LCP, INP, CLS, FCP, TTFB) with Google PageSpeed Insights and return them under core_web_vitals. Adds about 10 seconds the first time a URL is measured (cached 24 hours).…
- `url` (string, required): The URL to audit. Must include the protocol (https://...).

### `batch_audit` (~78 tokens)

Audit multiple URLs in one call. Requires Starter plan ($5/mo) or higher. Returns one audit object per URL.

Input parameters:

- `include_core_web_vitals` (boolean): Also measure Core Web Vitals for every URL. Slower: the batch can take a few minutes.
- `urls` (array, required): URLs to audit (1–10).

### `usage` (~25 tokens)

Get the current plan, monthly usage, and remaining quota for the API key in use.

### `report_url` (~60 tokens)

Return a public, shareable HTML report URL for a domain. Useful for sending audit results to clients without exposing API keys. Format: https://seoscoreapi.com/report/{domain}

Input parameters:

- `domain` (string, required): Domain (e.g. example.com).

### `add_monitor` (~44 tokens)

Add a URL to score monitoring. Re-audits on schedule and alerts via email when the score drops.

Input parameters:

- `frequency` (string)
- `url` (string, required)

### `list_monitors` (~22 tokens)

List all URLs currently under score monitoring for the active API key.

### `history` (~53 tokens)

Fetch the audit-score history for a URL. Returns a time-series of past scores so you can see trends. Requires Starter plan ($5/mo) or higher.

Input parameters:

- `limit` (integer)
- `url` (string, required)

### `history_domains` (~29 tokens)

List every domain audited by this API key with the latest score and 30-day trend. Starter+.

### `backlinks` (~109 tokens)

Look up observed backlinks for a domain. SEO Score API maintains an audit-fed backlink graph: every audit contributes the external links found on the audited page. The dataset is a sample (NOT a comprehensive backlink index like Ahrefs) and the response always includes a data_caveat. Coverage grows over time. Requires Basic plan ($15/mo) or higher.

Input parameters:

- `domain` (string, required): Target domain (e.g. example.com)
- `limit` (integer): Max sample rows to return (1-500)

### `deep_audit` (~205 tokens)

Run a Deep Audit — a thorough, AI-assisted SEO audit that scores a URL across 9 dimensions (technical, crawlability, content/entity, Core Web Vitals, technical SEO, structured data, security, media, off-site): thousands of catalog checks plus up to 150 AI checks. Runs asynchronously server-side; this tool waits for the result (about 90 seconds once it starts, longer if queued). Included on Pro ($39/mo, 20/month) and Ultra ($99/mo, 100/month); other keys spend a purchased Deep Audit credit. For long waits use start_deep_audit + get_deep_audit instead.

Input parameters:

- `business_type` (string): Optional: saas | local_service | ecommerce | storefront | blog | publisher — tunes which checks apply.
- `timeout_seconds` (integer): How long to wait before giving up (job keeps running).
- `url` (string, required): URL to audit. Must include the protocol (https://...).

### `start_deep_audit` (~99 tokens)

Queue a Deep Audit and return immediately with a job_id. Poll it with get_deep_audit. Same plans as deep_audit.

Input parameters:

- `business_type` (string): Optional: saas | local_service | ecommerce | storefront | blog | publisher.
- `url` (string, required): URL to audit. Must include the protocol (https://...).
- `webhook_url` (string): Optional public URL POSTed once when the job completes.

### `get_deep_audit` (~71 tokens)

Get a Deep Audit job's status: queued (queue_position, eta_seconds), running (progress 0-100, stage), completed (result) or failed (error). Poll every 5-10 seconds.

Input parameters:

- `job_id` (string, required): The job_id from start_deep_audit.

### `deep_audit_usage` (~26 tokens)

Deep Audits used and remaining this calendar month for the API key in use.

### `remove_monitor` (~22 tokens)

Remove a URL from score monitoring.

Input parameters:

- `url` (string, required)

### `compare` (~67 tokens)

Compare 2-5 URLs side by side with a structured diff: each URL's score and category breakdown plus who is ahead and by how much, per category and per URL pair. Requires Basic plan ($15/mo) or higher.

Input parameters:

- `urls` (array, required): 2 to 5 URLs.

### `competitive_audit` (~75 tokens)

Head-to-head SEO comparison of your page against a competitor's page with keyword-relevance scoring. Requires Pro plan ($39/mo) or higher.

Input parameters:

- `competitor_url` (string, required): The competitor's page URL.
- `keyword` (string, required): Target keyword (max 200 characters).
- `url` (string, required): Your page URL.

### `accessibility_audit` (~169 tokens)

Run an ADA / WCAG 2.1 AA accessibility audit (axe-core). Paid plans only. Returns the compliance score and grade, lawsuit risk (high/medium/low/minimal), category breakdowns, violations (WCAG 2.1 AA failures with affected elements and a plain-English fix), best_practices (not WCAG requirements; they never lower the score), needs_review and priorities. ADA audits have their own monthly allowance, separate from the audit quota (the usage tool reports ada_remaining). Each key may run 2 at a time; a 429 is not counted.

Input parameters:

- `include_trackers` (boolean): Also add the tracker and pixel inventory to the report.
- `url` (string, required): The URL to audit. Must include the protocol (https://...).

### `ai_readability` (~36 tokens)

Score how well a page can be consumed by AI/LLM systems. Counts as one audit.

Input parameters:

- `url` (string, required)

### `trackers` (~95 tokens)

List the third-party trackers and pixels a page loads (analytics, advertising, session replay, chat, marketing automation, A/B testing, monitoring), including pixels a tag manager injects. Loads the page in a real browser with no interaction; it does not determine whether a tracker waited for consent, and it is not legal advice. Counts as one audit; a page that can't be loaded is not counted.

Input parameters:

- `url` (string, required)

### `conversion` (~100 tokens)

Score how well a page turns a visitor into a lead or a sale: headline, call to action, trust, forms and objections, each 0-100, with a prioritized fix list. It does not measure the actual conversion rate. Counts as one audit. Free keys get the scores and the first two priorities; paid plans get the full list.

Input parameters:

- `page_type` (string): Detected from the page when omitted.
- `url` (string, required)

### `quick_wins` (~209 tokens)

Find the page-2 quick wins in the user's own Google Search Console data: queries ranking 11-20 worth working on first, each with an opportunity score and an estimate of the extra clicks from moving onto page 1. The API does not connect to Search Console: pass the exported rows or the CSV export text. Nothing is stored. The click numbers are estimates. Works on every plan; counts as one audit. Up to 1 MB per request.

Input parameters:

- `csv` (string): The Performance export as text, with a header row. Use instead of rows.
- `exclude_terms` (array): Words to leave out, such as the brand name.
- `limit` (integer): Default 25, max 200.
- `min_impressions` (integer): Default 50.
- `rows` (array): Rows like {query, page, clicks, impressions, position}. `page` is optional.
- `target_position` (integer): 1-10, default 5.

### `llms_txt` (~75 tokens)

Generate an llms.txt file for a domain and return its text, ready to save at /llms.txt. Basic plan ($15/mo) and higher get the curated version with per-page descriptions; other keys (or no key) get the basic version.

Input parameters:

- `domain` (string, required): Domain (e.g. example.com).

### `geo_audit` (~59 tokens)

Run a GEO (Generative Engine Optimization) audit: 26 checks measuring how visible a page is to LLMs. Requires Basic plan ($15/mo) or higher; uses the plan's monthly GEO allowance.

Input parameters:

- `url` (string, required)

### `geo_brand_probe` (~124 tokens)

Probe LLMs to measure how often a brand is mentioned in AI responses. Requires Basic plan ($15/mo) or higher; uses the plan's monthly GEO allowance. Can take a while.

Input parameters:

- `brand` (string, required)
- `domain` (string, required): The brand's domain (e.g. mybrand.com).
- `models` (array): Optional, e.g. ["claude", "nova"].
- `prompts` (array, required): Questions to ask, e.g. "What are the best X?"
- `runs_per_prompt` (integer): Default 3.

### `add_geo_monitor` (~59 tokens)

Create a GEO monitor for a URL. Requires Basic plan or higher (the Basic plan runs weekly).

Input parameters:

- `alert_threshold` (integer)
- `frequency` (string)
- `url` (string, required)
- `webhook_url` (string)

### `list_geo_monitors` (~22 tokens)

List the active GEO monitors for the API key in use.

### `geo_monitor_history` (~52 tokens)

Score history for a GEO monitor.

Input parameters:

- `monitor_id` (integer, required): The monitor's id from list_geo_monitors.
- `page` (integer)
- `per_page` (integer): 1-100.

### `remove_geo_monitor` (~23 tokens)

Remove a GEO monitor by URL.

Input parameters:

- `url` (string, required)

### `crawl_site` (~169 tokens)

Crawl one site and wait for the result: follows same-site links plus the sitemap and reports broken pages, redirects, duplicate titles and headings, pages missing a title or heading, orphan pages and slow pages. Pro: 25 pages per crawl, 20 crawls a month. Ultra: 100 pages, 100 crawls a month. Any other plan: one Deep Audit credit covers a 25-page crawl. A failed crawl is not counted. For long waits use start_crawl + get_crawl.

Input parameters:

- `max_pages` (integer): Fewer pages than the plan's cap (1-100).
- `timeout_seconds` (integer): How long to wait before giving up (the crawl keeps running).
- `url` (string, required): Where to start (e.g. https://example.com).

### `start_crawl` (~68 tokens)

Start a site crawl and return immediately with a job_id and a shareable site_map link. Poll it with get_crawl. Same plans as crawl_site.

Input parameters:

- `max_pages` (integer): Fewer pages than the plan's cap (1-100).
- `url` (string, required)

### `get_crawl` (~68 tokens)

Get a site crawl's status: queued, running (pages_done counts up), completed (result: summary, issues, pages, links) or failed (error). Only the key that started a crawl can read it.

Input parameters:

- `job_id` (string, required): The job_id from start_crawl.

### `citation_starter_prompts` (~211 tokens)

Build a starter set of prompts to track for AI citations, from a topic plus optional brand, competitors and audience. Fixed templates, not a model: no AI check is spent. Works on every plan and is not metered. Returns `prompts`, ready to pass to create_citation_tracker.

Input parameters:

- `audience` (string): Who buys it, plural (e.g. "marketing agencies").
- `brand` (string)
- `competitors` (array): Up to 5 competitor names.
- `features` (array): Up to 6 features buyers ask about.
- `limit` (integer): Cut the list to this many (1-60).
- `per_category` (integer): Prompts per category, 1-10 (default 2 = 12 prompts).
- `topic` (string, required): What you sell, as a buyer would type it, singular (e.g. "SEO audit API").
- `use_cases` (array): Up to 6 jobs it is bought for.

### `citation_suggest_prompts` (~35 tokens)

Suggest AI-citation prompts to track, read off what a site says it does.

Input parameters:

- `domain` (string, required)

### `create_citation_tracker` (~222 tokens)

Track a brand's visibility in AI answers (ChatGPT, Gemini, Perplexity, Claude): mention rate, citation rate, share of voice and position over time. Requires Starter ($5/mo) or higher. Monthly allowance (checks / tracked prompts): Starter 150 / 15, Basic 500 / 30, Pro 1,500 / 75, Ultra 4,000 / 200. A check is one prompt on one engine, sampled once. With no prompts, pass `starter` and a starter set is generated to fit the plan.

Input parameters:

- `brand` (string, required)
- `cadence` (string)
- `competitors` (array)
- `domains` (array): The brand's domains (e.g. ["acme.com"]).
- `engines` (array)
- `prompts` (array): The questions buyers type.
- `samples` (integer): Samples per prompt per engine.
- `starter` (object): Use instead of prompts: {topic, audience?}.
- `webhook_url` (string): https URL.

### `list_citation_trackers` (~46 tokens)

List the key's citation trackers plus `usage`: the month's checks (limit, used, remaining), the top-up balance and checks_available (what a run can spend now).

### `get_citation_tracker` (~23 tokens)

Read one citation tracker.

Input parameters:

- `tracker_id` (integer, required)

### `update_citation_tracker` (~84 tokens)

Edit a citation tracker's prompts, engines, competitors, samples, cadence or webhook. Only the fields passed change.

Input parameters:

- `cadence` (string)
- `competitors` (array)
- `engines` (array)
- `prompts` (array)
- `samples` (integer)
- `tracker_id` (integer, required)
- `webhook_url` (string)

### `delete_citation_tracker` (~32 tokens)

Stop tracking a brand. Run history is kept until its retention expires.

Input parameters:

- `tracker_id` (integer, required)

### `run_citation_tracker` (~79 tokens)

Run a citation tracker now. Every prompt x engine x sample counts as one check. A run needs all of its checks up front (the month's remaining allowance plus any top-up balance); if that is short the run is refused and nothing is spent. A check whose engine returned an error is not counted.

Input parameters:

- `tracker_id` (integer, required)

### `get_citation_run` (~33 tokens)

A citation run's status plus every per-prompt, per-engine result.

Input parameters:

- `run_id` (integer, required)

### `citation_tracker_history` (~48 tokens)

Timeseries of mention rate, citation rate, share of voice and average position for a citation tracker.

Input parameters:

- `days` (integer): 1-365.
- `tracker_id` (integer, required)

### `citation_check` (~88 tokens)

One-off AI citation check for a brand and one prompt: no tracker, metered per check (one check per engine per sample). Paid plans only (Starter and up).

Input parameters:

- `brand` (string, required)
- `competitors` (array)
- `domains` (array)
- `engines` (array)
- `prompt` (string, required)
- `samples` (integer): Default 1.

### `citation_topups` (~73 tokens)

Top-up packs for AI citation checks (`packs` is the live list with prices) and this account's balance. Top-up checks are spent only after the plan's monthly allowance, do not reset on the 1st, and expire 12 months after purchase. `can_buy` is false on the free tier.

### `citation_topup_checkout` (~93 tokens)

Create a one-time Stripe Checkout link for a pack of top-up citation checks and return its URL. Paid plans only. This charges nothing: the user must open the link and pay by card, and the checks are added when the payment completes. Get the pack keys and prices from citation_topups first.

Input parameters:

- `pack` (string, required): A pack `key` from citation_topups (e.g. "500").

### `citation_auto_reload` (~75 tokens)

Read the auto-reload setting for AI citation checks and this month's reloads and charges. Read-only: auto-reload is off unless the account owner turns it on, and it can only be turned on or changed from the dashboard (signed in), never through the API or this server, because turning it on authorizes charges.

## Diagnostics

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

## Score history

- 2026-11-05: 76
- 2026-11-04: 75
- 2026-11-03: 75
- 2026-11-02: 74
- 2026-11-01: 74
- 2026-10-31: 73
- 2026-10-30: 73
- 2026-10-29: 73
- 2026-10-28: 72
- 2026-10-27: 72
- 2026-10-26: 71
- 2026-10-25: 71
- 2026-10-24: 70
- 2026-10-23: 70
- 2026-10-22: 69
- 2026-10-21: 66
- 2026-10-20: 66
- 2026-10-19: 66
- 2026-10-18: 66
- 2026-10-17: 66
- 2026-10-16: 66
- 2026-10-15: 66
- 2026-10-14: 38
- 2026-10-13: 38
- 2026-10-12: 38
- 2026-10-11: 38

## Common questions

### What is the io.github.SeoScoreAPI/seoscoreapi-mcp server?

io.github.SeoScoreAPI/seoscoreapi-mcp is listed in the public MCP registry as io.github.SeoScoreAPI/seoscoreapi-mcp. SEO audits, AI readability, accessibility, backlinks and score monitoring from SEO Score API. This page covers its npm package (seoscoreapi-mcp).

### Is the io.github.SeoScoreAPI/seoscoreapi-mcp server safe to use?

io.github.SeoScoreAPI/seoscoreapi-mcp scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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.github.SeoScoreAPI/seoscoreapi-mcp server expose?

io.github.SeoScoreAPI/seoscoreapi-mcp exposes 45 tools: audit, batch_audit, usage, report_url, add_monitor, and 40 more. Their descriptions and schemas cost roughly 3,660 tokens of context every time the server is loaded.

### Is the io.github.SeoScoreAPI/seoscoreapi-mcp server still maintained?

io.github.SeoScoreAPI/seoscoreapi-mcp 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.

### What licence is the io.github.SeoScoreAPI/seoscoreapi-mcp server under?

io.github.SeoScoreAPI/seoscoreapi-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.

## Links

- npm package: https://www.npmjs.com/package/seoscoreapi-mcp
- Socket report: https://socket.dev/npm/package/seoscoreapi-mcp
- Repository: https://github.com/SeoScoreAPI/seoscoreapi-mcp
- Website: https://seoscoreapi.com/
- Changelog RSS feed: https://verifymcp.io/servers/seoscoreapi-seoscoreapi-mcp/seoscoreapi-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/seoscoreapi-seoscoreapi-mcp/seoscoreapi-mcp.json
- HTML version of this page: https://verifymcp.io/servers/seoscoreapi-seoscoreapi-mcp/seoscoreapi-mcp