com.metricspot/seo-mcp
REMOTE · MCP.METRICSPOT.COM · 2 COMPONENTS · SCANNED SEP 20
Six tools for SEO and AI-readability audits. 91 checks, 11 score modules.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the com.metricspot/seo-mcp server?
com.metricspot/seo-mcp is a hosted endpoint at https://mcp.metricspot.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.metricspot.com
claude mcp add --transport http com-metricspot-seo-mcp 'https://mcp.metricspot.com/mcp'
{
"mcpServers": {
"com-metricspot-seo-mcp": {
"url": "https://mcp.metricspot.com/mcp"
}
}
} {
"servers": {
"com-metricspot-seo-mcp": {
"type": "http",
"url": "https://mcp.metricspot.com/mcp"
}
}
} [mcp_servers.com-metricspot-seo-mcp] url = "https://mcp.metricspot.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-metricspot-seo-mcp": {
"type": "remote",
"url": "https://mcp.metricspot.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-metricspot-seo-mcp --url 'https://mcp.metricspot.com/mcp' --transport streamable-http
mcp_servers:
com-metricspot-seo-mcp:
url: "https://mcp.metricspot.com/mcp" {
"McpServers": {
"com-metricspot-seo-mcp": {
"Transport": "http",
"Url": "https://mcp.metricspot.com/mcp"
}
}
} assistant mcp add com-metricspot-seo-mcp -t streamable-http -u 'https://mcp.metricspot.com/mcp'
{
"mcpServers": {
"com-metricspot-seo-mcp": {
"type": "http",
"url": "https://mcp.metricspot.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.37 → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
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 20 Sept 2026 · Probed https://mcp.metricspot.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.metricspot.com | CN=YE2,O=Let's Encrypt,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5c3fb07d7c4a46856bfe562e958bb9169b3 |
| SANs: mcp.metricspot.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.metricspot.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| metricspot.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15724800; includeSubdomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.metricspot.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.metricspot.com/mcp | HTTPS enforced | 301 | https://mcp.metricspot.com:443/mcp |
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 →
get_audit ~73
Fetch a previously-run audit by id. Returns module scores (0-100), total score, all findings with severity, recommendation text, and links to the HTML report. Use this to poll a queued `run_audit` until `status: complete`. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| audit_id | string | yes | – |
No output schema declared.
No examples provided.
get_audit_pdf ~72
Return a signed download URL for the branded PDF report for a given audit id. If no PDF has been rendered yet, queues a render and returns `status: queued` — poll the same tool again, or fetch the URL directly once ready. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| audit_id | string | yes | – |
No output schema declared.
No examples provided.
get_organic_traffic ~84
If the user has linked GA4 + Google Search Console, return the 28-day organic traffic snapshot for an audit: session count, daily trend, top landing pages, top queries, and indexing health. Returns `connected: false` if Google is not linked. Cached 24h server-side. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| audit_id | string | yes | – |
No output schema declared.
No examples provided.
list_audits ~82
List the user's audits (most recent first, deduplicated by URL). Returns `audit_id`, `url`, `status`, `total_score`, `created_at`. Default limit 24, max 100. Use the returned `audit_id` with `get_audit` for full findings. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
run_audit ~117
Queue a full SEO + AI-readability audit (includes Core Web Vitals from Google PSI and organic traffic if Google is linked). Returns the audit envelope immediately with `status: queued` and an `audit_id`. Poll `get_audit` with the returned `audit_id` until `status` becomes `complete` (typical 10-30s). Counts against the user's plan allowance. Requires an API key as a Bearer token. Quota and per-domain cooldowns mirror the dashboard.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
run_audit_anonymous ~121
Run a one-shot SEO + AI-readability audit on any public URL. Returns scores across 11 modules and ~90 checks, plus actionable findings with rule docs. Limited to 1 audit per IP per 24 hours — for higher volume, get an API key at https://app.metricspot.com/settings/api-keys and use `run_audit`. Synchronous: blocks until the audit completes. Does NOT include Core Web Vitals (use `run_audit` for full PSI scoring). No auth required.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
What is the com.metricspot/seo-mcp server?
com.metricspot/seo-mcp is listed in the public MCP registry as com.metricspot/seo-mcp. Six tools for SEO and AI-readability audits. 91 checks, 11 score modules. This page covers its hosted endpoint (https://mcp.metricspot.com/mcp).
Is the com.metricspot/seo-mcp server safe to use?
com.metricspot/seo-mcp scores 35 out of 100 on VerifyMCP. 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 com.metricspot/seo-mcp server expose?
com.metricspot/seo-mcp exposes 6 tools: run_audit_anonymous, run_audit, get_audit, list_audits, get_audit_pdf, get_organic_traffic. Their descriptions and schemas cost roughly 549 tokens of context every time the server is loaded.
Does the com.metricspot/seo-mcp server require authentication?
No. We connected to com.metricspot/seo-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.metricspot/seo-mcp server still maintained?
com.metricspot/seo-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.