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.

Visibly AI — SEO MCP Server

REMOTE · MCP.VISIBLY-AI.COM

Remote SEO/GEO MCP: Search Console, keyword research, backlinks, competitor & on-page audits.

0 this week 75 Trust /100

Last scanned (19 hours ago)

Scores higher than 64% of remote servers

Unreachable for 1 day in a row. Last reached 3 Nov 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 Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.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, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.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.

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.

  • 4 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • HSTS header: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 23 Oct 26 0
    • Server version: 0.13.1 → 0.14.0 functional
  • 29 Sept 26 0
    • Server version: 0.13.0 → 0.13.1 functional
  • 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
  • 12 Sept 26 0
    • Server version: 0.10.0 → 0.11.0 functional
  • 11 Sept 26 0
    • Server version: 0.9.0 → 0.10.0 functional
  • 9 Sept 26 0
    • Server version: 0.7.0 → 0.9.0 functional
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 4 Nov 2026 · Probed https://mcp.visibly-ai.com/mcp

TLS unreached
DNSSEC insecure

Validation of mcp.visibly-ai.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
visibly-ai.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.visibly-ai.com/mcp Unreachable
http (plaintext) http://mcp.visibly-ai.com/mcp HTTPS enforced
MCP tools · 7 exposed · ~440 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
analyze_url_structure ~44

Analyze a URL for SEO-friendliness. Checks length, structure, and common issues. Free - no API key required.

NameTypeReqDescription
urlstringyesURL to analyze

No output schema declared.

No examples provided.

classify_keywords_simple ~75

Classify keywords locally by intent, funnel stage, brand type, and topic. Free and available without an API key.

NameTypeReqDescription
brand_namestring––
brand_variationsarray––
competitorsarray––
keywordsarrayyesKeywords to classify
product_keywordsarray––

No output schema declared.

No examples provided.

get_google_guidelines ~28

Get official Google Search developer guidelines by category. Free.

NameTypeReqDescription
categorystring––

No output schema declared.

No examples provided.

get_skill ~118

Get an SEO workflow skill with step-by-step methodology, triggers, credits, and quality gates from the current seo_skills catalog. Use name='content-nss-optimize' to write with your own model and improve an article toward measured NSS 70/80 using free Visibly scoring, then save it and show the editor link. Use name='list' for all available skills. Free - no API key required.

NameTypeReqDescription
namestringyesSkill name (e.g. 'seo-audit') or 'list' for all available skills

No output schema declared.

No examples provided.

list_locations ~25

List available countries/locations for SEO data queries. Free - no API key required.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

seo_checklist ~63

Get an SEO checklist. Types: general, blog, ecommerce, discover, backlink, all. Available in English and German. Free - no API key required.

NameTypeReqDescription
checklist_typestring–Checklist type
languagestring–Language (en or de)

No output schema declared.

No examples provided.

seo_guidance ~87

Get SEO best practices on a topic. Topics: title_tags, meta_descriptions, heading_structure, internal_linking, core_web_vitals, eeat, keyword_research, schema_markup, image_optimization, local_seo. Use topic='list' for all. Free - no API key required.

NameTypeReqDescription
topicstringyesSEO topic or 'list' for all topics

No output schema declared.

No examples provided.

Install

How do I install the Visibly AI — SEO MCP Server server?

Visibly AI — SEO MCP Server is a hosted endpoint at https://mcp.visibly-ai.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.visibly-ai.com

# add to Claude Code
claude mcp add --transport http antonioblago-visibly-ai 'https://mcp.visibly-ai.com/mcp'
Common questions

What is the Visibly AI — SEO MCP Server server?

Visibly AI — SEO MCP Server is listed in the public MCP registry as io.github.AntonioBlago/visibly-ai. Remote SEO/GEO MCP: Search Console, keyword research, backlinks, competitor & on-page audits. This page covers its hosted endpoint (https://mcp.visibly-ai.com/mcp).

Is the Visibly AI — SEO MCP Server server safe to use?

Visibly AI — SEO MCP Server scores 75 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 Visibly AI — SEO MCP Server server expose?

Visibly AI — SEO MCP Server exposes 7 tools: classify_keywords_simple, seo_checklist, seo_guidance, analyze_url_structure, list_locations, and 2 more. Their descriptions and schemas cost roughly 440 tokens of context every time the server is loaded.

Does the Visibly AI — SEO MCP Server server require authentication?

Its publisher declares that Visibly AI — SEO MCP Server requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.

Is the Visibly AI — SEO MCP Server server still maintained?

Visibly AI — SEO MCP Server is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.