SEO Tools
REMOTE · API.TIMZININ.COM
5 pay-per-call SEO tools over MCP. Free discovery, tool calls settle in USDC on Base via x402.
Available components
Last scanned (2 hours ago)
Scores higher than 87% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1715 tokens (~245/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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.
- 28 Sept 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
- 25 Sept 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 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
- 16 Aug 26 0
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 218 → 245 ▼ functional
- Tool “ai-answer-change-alert” changed its title: AI Answer Change Alert cosmetic
- Tool “ai-crawler-access-checker” changed its title: AI Crawler Access Checker cosmetic
- Tool “ai-overview-tracker” changed its title: AI Overview Citation Tracker cosmetic
- Tool “llm-brand-visibility” changed its title: LLM Brand Visibility Tracker cosmetic
- Tool “llms-txt-auditor” changed its title: llms.txt Compliance Checker cosmetic
- Tool “pricing_info” changed its title: Pricing — SEO / GEO / AEO Tools cosmetic
- Tool “social-preview-checker” changed its title: Social Preview Checker cosmetic
- 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
- 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
- 29 Jul 26 0
- Tool “ai-overview-tracker” rewrote its description, which is the text the model reads security
- Tool “llm-brand-visibility” rewrote its description, which is the text the model reads security
- Schema quality: 193 → 218 ▼ functional
- New tool “ai-answer-change-alert” functional
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 5 Nov 2026 · Probed https://api.timzinin.com/mcp/seo-tools
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.timzinin.com | CN=YE2,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6a81be6512ce92fb1cd3c146aae5613dac3 |
| SANs: api.timzinin.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 api.timzinin.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| timzinin.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.timzinin.com/mcp/seo-tools | Verified | 200 | |
| http (plaintext) | http://api.timzinin.com/mcp/seo-tools | HTTPS enforced | 301 | https://api.timzinin.com/mcp/seo-tools |
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 →
ai-answer-change-alert AI Answer Change Alert ~367
Ask an LLM the queries that matter to you, compare each answer against its stored baseline and get told what changed — the answer itself and which domains it now cites or stopped citing. One row per query x model. — $0.10/call, x402 (USDC on base).
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Answer language (e.g. en, ru, tr). |
| maxConcurrency | integer | – | Parallel LLM calls (kept low to respect rate limits and to bound how many LLM calls can be wasted — uncharged — if a run's spend limit is hit mid-run). |
| models | array | – | OpenRouter model IDs to check. Grounded options: `perplexity/sonar`, `openai/gpt-4o-mini:online`, `google/gemini-2.0-flash-001:online`. Every model you add multiplies the number of billed rows: rows… |
| openrouterApiKey | string | – | Your OpenRouter API key (https://openrouter.ai/keys). Optional: without it the built-in key is used and the LLM cost is covered by the per-row price. Pass your own key to have tokens billed to your a… |
| queries | array | yes | The prompts a real user would ask (e.g. `best crm for small business`). Each query is run against every model in `models` below and compared against the previous run's stored answer for the same quer… |
No output schema declared.
No examples provided.
ai-crawler-access-checker AI Crawler Access Checker ~124
Check which AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended & more) can access your website. Bulk audit of robots.txt rules, llms.txt presence and sitemap for AI search visibility (GEO/AEO). — $0.01/call, x402 (USDC on base).
| Name | Type | Req | Description |
|---|---|---|---|
| maxConcurrency | integer | – | How many websites to check in parallel. |
| websites | array | yes | List of website URLs or domains to audit (e.g. `example.com` or `https://example.com`). |
No output schema declared.
No examples provided.
ai-overview-tracker AI Overview Citation Tracker ~358
For each query that matters, see which sources and domains AI assistants cite in their answer — grounded via Perplexity Sonar, GPT or Gemini through your own OpenRouter key. GEO citation tracking: the backlink profile of the AI-answer era. — $0.10/call, x402 (USDC on base).
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Answer language (e.g. en, ru, tr). |
| maxConcurrency | integer | – | Parallel LLM calls (kept low to respect rate limits). |
| models | array | – | OpenRouter model IDs to test. Grounded options: `perplexity/sonar`, `openai/gpt-4o-mini:online`, `google/gemini-2.0-flash-001:online`. Every model you add here multiplies the number of billed rows: r… |
| openrouterApiKey | string | – | Your OpenRouter API key (https://openrouter.ai/keys). LLM token cost is billed to YOUR account; this Actor only orchestrates and scores. Optional to start the Actor: without it the run finishes clean… |
| queries | array | yes | The prompts a real user would ask (e.g. `best project management software`, `how to choose a CRM`). Each query is run against EVERY model in `models` below, and you are charged per query × model pair… |
No output schema declared.
No examples provided.
llm-brand-visibility LLM Brand Visibility Tracker ~379
For each query that matters, check whether AI assistants recommend YOUR brand — and which competitors they cite instead. Grounded answers from Perplexity Sonar, GPT and Gemini via your own OpenRouter key. This is GEO: the SEO of the AI era. — $0.10/call, x402 (USDC on base).
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | The brand, product or company you want to track in AI answers. |
| lang | string | – | Answer language (e.g. en, ru, tr). |
| maxConcurrency | integer | – | Parallel LLM calls (kept low to respect rate limits). |
| models | array | – | OpenRouter model IDs to test. Grounded options: `perplexity/sonar`, `openai/gpt-4o-mini:online`, `google/gemini-2.0-flash-001:online`. Every model you add here multiplies the number of billed rows: r… |
| openrouterApiKey | string | – | Your OpenRouter API key (https://openrouter.ai/keys). LLM token cost is billed to YOUR account; this Actor only orchestrates and scores. Optional to start the Actor: without it the run finishes clean… |
| queries | array | yes | The prompts a real user would ask (e.g. `best note-taking app`, `Notion alternatives`). Each query is run against EVERY model in `models` below, and you are charged per query × model pair, not per qu… |
No output schema declared.
No examples provided.
llms-txt-auditor llms.txt Compliance Checker ~143
Give it a domain. It checks whether the site publishes a valid llms.txt / llms-full.txt (the emerging AI-crawler-friendly-docs convention) and whether robots.txt blocks GPTBot, ClaudeBot, Google-Extended, PerplexityBot and 5 other AI crawlers. llms.txt-first, no browser, no LLM, no API key. — $0.01/call, x402 (USDC on base).
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | List of domains to audit for llms.txt presence and AI-crawler robots.txt policy. |
| maxConcurrency | integer | – | How many domains to audit in parallel. |
No output schema declared.
No examples provided.
pricing_info Pricing — SEO / GEO / AEO Tools ~43
Free — list every paid tool in the 'seo-tools' bundle with its price, payTo address and network. Call this first if you don't have a wallet ready yet.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
social-preview-checker Social Preview Checker ~115
See exactly how your links look when shared on Telegram, WhatsApp, X, LinkedIn, Slack, Facebook & Discord. Bulk-audit Open Graph and Twitter Card tags, validate preview images, and find what breaks your link previews. — $0.01/call, x402 (USDC on base).
| Name | Type | Req | Description |
|---|---|---|---|
| maxConcurrency | integer | – | How many URLs to check in parallel. |
| urls | array | yes | List of page URLs to check (e.g. `example.com/article` or a full https URL). |
No output schema declared.
No examples provided.
How do I install the SEO Tools MCP server?
SEO Tools is a hosted endpoint at https://api.timzinin.com/mcp/seo-tools, 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.timzinin.com
claude mcp add --transport http com-timzinin-api-seo-tools 'https://api.timzinin.com/mcp/seo-tools'
What is the SEO Tools MCP server?
SEO Tools is an MCP server listed in the public MCP registry as com.timzinin.api/seo-tools. 5 pay-per-call SEO tools over MCP. Free discovery, tool calls settle in USDC on Base via x402. This page covers its hosted endpoint (https://api.timzinin.com/mcp/seo-tools).
Is the SEO Tools MCP server safe to use?
SEO Tools scores 83 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 SEO Tools MCP server expose?
SEO Tools exposes 7 tools: pricing_info, ai-answer-change-alert, ai-crawler-access-checker, ai-overview-tracker, llm-brand-visibility, and 2 more. Their descriptions and schemas cost roughly 1,529 tokens of context every time the server is loaded.
Does the SEO Tools MCP server require authentication?
No. We connected to SEO Tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SEO Tools MCP server still maintained?
SEO Tools 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.