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.

stillindexed SEO checkers

REMOTE · API.STILLINDEXED.COM

Indexability, robots.txt, sitemap, TLS, domain expiry and Googlebot-vs-browser checks. No account.

+3 this week 73 Trust /100

Last scanned (23 hours ago)

Scores higher than 64% of remote servers

Reachable. Last reached 22 Oct 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

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 Security74
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 735 tokens (~81/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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.

  • 22 Oct 26 +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.

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

  • 17 Oct 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.

  • 15 Oct 26 +1

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

  • 13 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 12 Oct 26 68

    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 22 Oct 2026 · Probed https://api.stillindexed.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.stillindexed.com CN=YR2,O=Let's Encrypt,C=US 23 Aug 2026 21 Nov 2026 RSA 4096 SHA256-RSA 614be0db67491a1f1a0ade0adf3b99f9ef3
SANs: api.stillindexed.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.stillindexed.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
stillindexed.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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.stillindexed.com/mcp Verified 200
http (plaintext) http://api.stillindexed.com/mcp HTTPS enforced 301 https://api.stillindexed.com/mcp
MCP tools · 9 exposed · ~681 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
stillindexed_bulk_check ~68

Indexability check for up to 20 URLs in one call. Order preserved. Invalid URLs become per-row errors; HTTP status stays 200. Counts against the 60 fetches/hour budget, one per URL.

NameTypeReqDescription
urlsarrayyesUp to 20 http(s) URLs.

No output schema declared.

No examples provided.

stillindexed_check_ai_crawlers ~148

Check robots.txt for the 13 tracked AI crawlers (ChatGPT search, Claude, Perplexity, Gemini grounding, and the training crawlers) and report, per crawler, whether the given URL's path is allowed or blocked, naming the deciding group and rule. Also probes the edge once as each of the three AI search crawlers (OAI-SearchBot, Claude-SearchBot, PerplexityBot) against a browser request. Costs up to 5 fetches. Same check as https://stillindexed.com/tools/ai-crawler-checker.

NameTypeReqDescription
urlstringyesAbsolute http(s) URL, or a hostname (https is assumed).

No output schema declared.

No examples provided.

stillindexed_check_domain ~58

Domain registration expiry via RDAP. Many ccTLDs have no RDAP; the tool says so instead of inventing an expiry.

NameTypeReqDescription
urlstringyesAbsolute http(s) URL, or a hostname (https is assumed).

No output schema declared.

No examples provided.

stillindexed_check_robots ~71

Fetch robots.txt for the host and report the effective allow/disallow for each path, wildcard group vs Googlebot separately.

NameTypeReqDescription
pathsarray–Paths to evaluate. Defaults to ["/"].
urlstringyesAbsolute http(s) URL, or a hostname (https is assumed).

No output schema declared.

No examples provided.

stillindexed_check_sitemap ~55

Fetch a sitemap (or the host's /sitemap.xml) and report status, XML validity, and URL count.

NameTypeReqDescription
urlstringyesAbsolute http(s) URL, or a hostname (https is assumed).

No output schema declared.

No examples provided.

stillindexed_check_tls ~45

TLS certificate for the host: days remaining, chain validity, hostname match.

NameTypeReqDescription
urlstringyesAbsolute http(s) URL, or a hostname (https is assumed).

No output schema declared.

No examples provided.

stillindexed_check_url ~79

Fetch one URL and report HTTP status, redirect chain, meta robots, X-Robots-Tag, canonical, title, H1, and whether it is indexable. Same check as https://stillindexed.com/tools/indexability-checker.

NameTypeReqDescription
urlstringyesAbsolute http(s) URL, or a hostname (https is assumed).

No output schema declared.

No examples provided.

stillindexed_crawler_diff ~64

Fetch the same URL as Googlebot, Bingbot, GPTBot and a browser, then compare status, indexability directives and content. Costs 4 fetches.

NameTypeReqDescription
urlstringyesAbsolute http(s) URL, or a hostname (https is assumed).

No output schema declared.

No examples provided.

stillindexed_generate_seo_skill ~93

Fetch the URL, robots.txt, sitemap (with index expansion), host variants, a four-persona crawler diff and TLS, then return a SKILL.md an agent can install for that host. Up to 12 fetches. Same generator as https://stillindexed.com/tools/seo-skill-generator.

NameTypeReqDescription
urlstringyesAbsolute http(s) URL, or a hostname (https is assumed).

No output schema declared.

No examples provided.

Install

How do I install the stillindexed SEO checkers MCP server?

stillindexed SEO checkers is a hosted endpoint at https://api.stillindexed.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 · api.stillindexed.com

# add to Claude Code
claude mcp add --transport http com-stillindexed-seo-checkers 'https://api.stillindexed.com/mcp'
Common questions

What is the stillindexed SEO checkers MCP server?

stillindexed SEO checkers is an MCP server listed in the public MCP registry as com.stillindexed/seo-checkers. Indexability, robots.txt, sitemap, TLS, domain expiry and Googlebot-vs-browser checks. No account. This page covers its hosted endpoint (https://api.stillindexed.com/mcp).

Is the stillindexed SEO checkers MCP server safe to use?

stillindexed SEO checkers scores 73 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 stillindexed SEO checkers MCP server expose?

stillindexed SEO checkers exposes 9 tools: stillindexed_check_url, stillindexed_bulk_check, stillindexed_check_robots, stillindexed_check_sitemap, stillindexed_check_tls, and 4 more. Their descriptions and schemas cost roughly 681 tokens of context every time the server is loaded.

Does the stillindexed SEO checkers MCP server require authentication?

No. We connected to stillindexed SEO checkers without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the stillindexed SEO checkers MCP server still maintained?

stillindexed SEO checkers is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.