CallAI SEO
REMOTE · API.CALLAIAPI.COM
Live SEO data: Google/Bing SERP, AI Overview sources, keyword difficulty, backlinks, page audits.
Available components
Last scanned (1 hour ago)
Scores higher than 44% 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 Security57
- 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 call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2683 tokens (~134/item across 20 items; 20 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 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
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 5 Nov 26 +30
- Authorization: fail → unverified ▼ security
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 3 Nov 26 33
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 5 Nov 2026 · Probed https://api.callaiapi.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.callaiapi.com | CN=YR2,O=Let's Encrypt,C=US | 13 Oct 2026 | 11 Jan 2027 | RSA 4096 | SHA256-RSA | 54b92ebcad3e7818260af4e76e8d6893cab |
| SANs: api.callaiapi.com, claude.callaiapi.com, deepseek.callaiapi.com, gemini.callaiapi.com, openai.callaiapi.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.callaiapi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| callaiapi.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.callaiapi.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.callaiapi.com/mcp | HTTPS enforced | 301 | https://api.callaiapi.com/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 →
backlinks_summary Backlink profile summary ~63
Backlink totals for a domain: domain rank (0–1000), backlinks, referring domains, nofollow share, broken backlinks, spam score and first-seen date. About $0.02 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Domain such as example.com. |
No output schema declared.
No examples provided.
bing_serp Bing SERP ~189
Live Bing organic search results for a keyword in a given country and language: ranks, titles, URLs, snippets. Billed per call (about $0.002 for depth 10).
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | Number of results to fetch, 10–100 (default 10). Cost grows with depth. |
| device | string | – | Default desktop. |
| keyword | string | yes | Search query. Supports operators such as site:example.com. |
| language_code | string | – | Language code, e.g. en (default), de, fr, ja, es, pt, zh-CN. |
| location_code | integer | – | DataForSEO location code. 2840 = United States (default), 2826 = UK, 2276 = Germany, 2250 = France, 2392 = Japan, 2356 = India, 2076 = Brazil. |
No output schema declared.
No examples provided.
check_robots Read robots.txt ~50
Fetches a site's robots.txt and returns its status and contents. Free: needs an API key but no balance.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL or domain, such as https://example.com/page. |
No output schema declared.
No examples provided.
check_sitemap Find and read sitemaps ~69
Finds a site's sitemaps through robots.txt (falling back to /sitemap.xml) and returns each one's status, number of URLs and a sample. Free: needs an API key but no balance.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL or domain, such as https://example.com/page. |
No output schema declared.
No examples provided.
dataforseo_request Any DataForSEO v3 endpoint ~187
Calls any DataForSEO v3 endpoint directly when no dedicated tool fits (Google Maps, YouTube, Amazon keywords, Google Trends, LLM mentions, WHOIS, technologies, task_post/task_get and more). Body and response follow the DataForSEO v3 docs at https://docs.dataforseo.com/v3/. Billed at the endpoint's DataForSEO price; task_get and tasks_ready calls are free. Always set a limit or filters: endpoints without them can be expensive.
| Name | Type | Req | Description |
|---|---|---|---|
| body | array | – | Array of task objects for POST requests. |
| method | string | – | POST for live and task_post endpoints (default), GET for task_get and tasks_ready. |
| path | string | yes | Path below /v3/, e.g. "serp/google/maps/live/advanced" or "serp/google/organic/task_get/advanced/<task_id>". |
No output schema declared.
No examples provided.
dns_lookup DNS records ~53
A, AAAA, CNAME, MX, NS and TXT records of a domain, from public resolvers. Free: needs an API key but no balance.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain such as example.com. |
No output schema declared.
No examples provided.
domain_check_results Read a domain check ~124
Progress and per-domain verdicts of a check started with domain_check_start: verdict, reason, first archive year, stable years, Baidu results, referring domains and spam score. A check can take minutes; rows stay pending until their steps finish. Reading is free.
| Name | Type | Req | Description |
|---|---|---|---|
| after | integer | – | The "next" value of the previous page. |
| check_id | string | yes | The id from domain_check_start. |
| limit | integer | – | Rows per page, up to 200 (default 50). |
| verdict | string | – | Only rows with this verdict. |
No output schema declared.
No examples provided.
domain_check_start Start a domain check ~183
Checks up to 100 domains (for buying expired or used domains): web archive history, Baidu index and backlinks, ending in a clean, suspect or rejected verdict with reasons. Charged per domain, about $0.02. Set dry_run first to see the exact cost and show it to the user. Runs in the background; read progress with domain_check_results.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | Domains to check (max 100). |
| dry_run | boolean | – | Only return the cost; nothing is started or charged. |
| rules | object | – | Optional pass rules; anything left out uses the defaults. Fields: tlds (string[]), firstSeenBy (year), minStableYears, noHistory (pass|suspect|reject), minBaiduIndexed (0–10), minReferringDomains, ma… |
No output schema declared.
No examples provided.
domain_overview Domain organic traffic overview ~140
Estimated Google organic traffic, number of ranking keywords and their position distribution for a domain, plus paid search totals. About $0.01 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| language_code | string | – | Language code, e.g. en (default), de, fr, ja, es, pt, zh-CN. |
| location_code | integer | – | DataForSEO location code. 2840 = United States (default), 2826 = UK, 2276 = Germany, 2250 = France, 2392 = Japan, 2356 = India, 2076 = Brazil. |
| target | string | yes | Domain such as example.com. |
No output schema declared.
No examples provided.
email_auth_check SPF, DKIM and DMARC audit ~103
Checks a domain's MX, SPF, DKIM, DMARC and MTA-STS records and says whether it can be spoofed, with the issues to fix. Without dkim_selector it tries the common selectors, so a missing DKIM result is not proof of absence. Free: needs an API key but no balance.
| Name | Type | Req | Description |
|---|---|---|---|
| dkim_selector | string | – | The DKIM selector, if known. |
| domain | string | yes | Domain such as example.com. |
No output schema declared.
No examples provided.
google_serp Google SERP ~200
Live Google organic search results for a keyword in a given country and language: ranks, titles, URLs, snippets, plus the AI Overview text and the sources it cites. Billed per call (about $0.002 for depth 10).
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | Number of results to fetch, 10–100 (default 10). Cost grows with depth. |
| device | string | – | Default desktop. |
| keyword | string | yes | Search query. Supports operators such as site:example.com. |
| language_code | string | – | Language code, e.g. en (default), de, fr, ja, es, pt, zh-CN. |
| location_code | integer | – | DataForSEO location code. 2840 = United States (default), 2826 = UK, 2276 = Germany, 2250 = France, 2392 = Japan, 2356 = India, 2076 = Brazil. |
No output schema declared.
No examples provided.
keyword_gap Competitor keyword gap ~176
Keywords the competitor ranks for on Google that your domain does not, sorted by search volume: the content gap to target. About $0.01 per call plus $0.0001 per row.
| Name | Type | Req | Description |
|---|---|---|---|
| competitor | string | yes | Competitor domain. |
| language_code | string | – | Language code, e.g. en (default), de, fr, ja, es, pt, zh-CN. |
| limit | integer | – | Rows to return, 1–200 (default 50). |
| location_code | integer | – | DataForSEO location code. 2840 = United States (default), 2826 = UK, 2276 = Germany, 2250 = France, 2392 = Japan, 2356 = India, 2076 = Brazil. |
| your_domain | string | yes | Your domain. |
No output schema declared.
No examples provided.
keyword_ideas Long-tail keyword ideas ~197
Long-tail keywords that contain the seed keyword, with search volume, CPC, keyword difficulty and intent. Use it to find low-difficulty commercial keywords. About $0.01 per call plus $0.0001 per keyword returned.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | Seed keyword. |
| language_code | string | – | Language code, e.g. en (default), de, fr, ja, es, pt, zh-CN. |
| limit | integer | – | Keywords to return, 1–200 (default 50). |
| location_code | integer | – | DataForSEO location code. 2840 = United States (default), 2826 = UK, 2276 = Germany, 2250 = France, 2392 = Japan, 2356 = India, 2076 = Brazil. |
| max_difficulty | integer | – | Only return keywords with keyword difficulty at or below this value (0–100). |
No output schema declared.
No examples provided.
keyword_overview Keyword metrics ~158
Google search volume, CPC, competition, keyword difficulty (0–100) and main search intent for up to 100 keywords in one call. About $0.01 per call plus $0.0001 per keyword.
| Name | Type | Req | Description |
|---|---|---|---|
| keywords | array | yes | Keywords to look up (max 100). |
| language_code | string | – | Language code, e.g. en (default), de, fr, ja, es, pt, zh-CN. |
| location_code | integer | – | DataForSEO location code. 2840 = United States (default), 2826 = UK, 2276 = Germany, 2250 = France, 2392 = Japan, 2356 = India, 2076 = Brazil. |
No output schema declared.
No examples provided.
keyword_suggestions Search-box keyword suggestions ~127
Autocomplete suggestions from Google, Bing, YouTube, Amazon, Baidu, DuckDuckGo, Yahoo and Yandex, merged and de-duplicated. No search volume; pass the results to keyword_overview for metrics. Free: needs an API key but no balance.
| Name | Type | Req | Description |
|---|---|---|---|
| engines | array | – | Default google and bing. |
| keyword | string | yes | Seed keyword. |
| market | string | – | Default us. |
| mode | string | – | seed: the keyword only (default). questions: with question words. az: with each letter a–z, the most results. |
No output schema declared.
No examples provided.
page_audit On-page SEO audit ~77
Fetches one URL and reports its on-page SEO: status code, title, meta description, canonical, headings, word count, link and image counts, load timing, on-page score and all on-page checks. About $0.0002 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Absolute URL starting with https:// or http://. |
No output schema declared.
No examples provided.
page_meta Read a page’s SEO tags ~126
Fetches one URL and returns its status, final URL, title, meta description, canonical, meta robots, X-Robots-Tag, hreflang and H1s, as a browser or as Googlebot. Reads the raw HTML without running JavaScript. For a full audit use page_audit. Free: needs an API key but no balance.
| Name | Type | Req | Description |
|---|---|---|---|
| fetch_as | string | – | Identify as our bot (default) or with Googlebot’s user agent, to spot cloaking. |
| url | string | yes | URL or domain, such as https://example.com/page. |
No output schema declared.
No examples provided.
ranked_keywords Keywords a domain ranks for ~176
Google organic keywords a domain (or URL) currently ranks for, sorted by estimated traffic: keyword, volume, difficulty, position, ranking URL and estimated traffic. About $0.01 per call plus $0.0001 per row.
| Name | Type | Req | Description |
|---|---|---|---|
| language_code | string | – | Language code, e.g. en (default), de, fr, ja, es, pt, zh-CN. |
| limit | integer | – | Rows to return, 1–200 (default 50). |
| location_code | integer | – | DataForSEO location code. 2840 = United States (default), 2826 = UK, 2276 = Germany, 2250 = France, 2392 = Japan, 2356 = India, 2076 = Brazil. |
| target | string | yes | Domain such as example.com. |
No output schema declared.
No examples provided.
redirect_chain Trace redirects ~57
Follows a URL's redirects and returns the status and target of every hop, up to 5. Free: needs an API key but no balance.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL or domain, such as https://example.com/page. |
No output schema declared.
No examples provided.
referring_domains Referring domains ~75
Domains linking to the target, strongest first: rank, backlink count, spam score and first-seen date. About $0.02 per call plus a small per-row fee.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows to return, 1–200 (default 50). |
| target | string | yes | Domain such as example.com. |
No output schema declared.
No examples provided.
How do I install the CallAI SEO MCP server?
CallAI SEO is a hosted endpoint at https://api.callaiapi.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.callaiapi.com
claude mcp add --transport http com-callaiapi-seo 'https://api.callaiapi.com/mcp'
What is the CallAI SEO MCP server?
CallAI SEO is an MCP server listed in the public MCP registry as com.callaiapi/seo. Live SEO data: Google/Bing SERP, AI Overview sources, keyword difficulty, backlinks, page audits. This page covers its hosted endpoint (https://api.callaiapi.com/mcp).
Is the CallAI SEO MCP server safe to use?
CallAI SEO scores 63 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 CallAI SEO MCP server expose?
CallAI SEO exposes 20 tools: google_serp, bing_serp, keyword_overview, keyword_ideas, ranked_keywords, and 15 more. Their descriptions and schemas cost roughly 2,530 tokens of context every time the server is loaded.
Does the CallAI SEO MCP server require authentication?
No. We connected to CallAI SEO without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CallAI SEO MCP server still maintained?
CallAI SEO 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.