Visibly AI — SEO MCP Server
REMOTE · MCP.VISIBLY-AI.COM · SCANNED AUG 3
Remote SEO/GEO MCP: Search Console, keyword research, backlinks, competitor & on-page audits.
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 →
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 7 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 Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 399 tokens (~57/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability check failed: schema churn in the 8 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 2 additions. See how to fix → Fail
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 55% of tool parameters carry a description.Partial
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.visibly-ai.com
claude mcp add --transport http antonioblago-visibly-ai https://mcp.visibly-ai.com/mcp
[mcp_servers.antonioblago-visibly-ai] url = "https://mcp.visibly-ai.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"antonioblago-visibly-ai": {
"type": "remote",
"url": "https://mcp.visibly-ai.com/mcp",
"enabled": true
}
}
} openclaw mcp add antonioblago-visibly-ai --url https://mcp.visibly-ai.com/mcp --transport streamable-http
mcp_servers:
antonioblago-visibly-ai:
url: "https://mcp.visibly-ai.com/mcp" {
"mcpServers": {
"antonioblago-visibly-ai": {
"type": "http",
"url": "https://mcp.visibly-ai.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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10.
- 2 Aug 26 −5
- Stability: 0.20 → fail ▼ security
- Tool “get_auth_status” was removed ▼ security
- Schema quality: 329 → 399 ▼ functional
- Tool coverage: 100% → 55% ▼ functional
- Server version: 0.6.0 → 0.7.0 functional
- New tool “classify_keywords_simple” functional
- New tool “get_google_guidelines” 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 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- 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 59
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 3 Aug 2026 · Probed https://mcp.visibly-ai.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.visibly-ai.com | CN=YR2,O=Let's Encrypt,C=US | 16 Jul 2026 | 14 Oct 2026 | RSA 2048 | SHA256-RSA | 515451288ac34ed18697aeef8ade8fe8de1 |
| SANs: mcp.visibly-ai.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 |
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 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.visibly-ai.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.visibly-ai.com/mcp | HTTPS enforced | 302 | https://mcp.visibly-ai.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.
analyze_url_structure ~44
Analyze a URL for SEO-friendliness. Checks length, structure, and common issues. Free - no API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL 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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_name | string | — | — |
| brand_variations | array | — | — |
| competitors | array | — | — |
| keywords | array | yes | Keywords to classify |
| product_keywords | array | — | — |
No output schema declared.
No examples provided.
get_google_guidelines ~28
Get official Google Search developer guidelines by category. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | — | — |
No output schema declared.
No examples provided.
get_skill ~77
Get an SEO workflow skill with step-by-step methodology, triggers, credits, and quality gates from the current seo_skills catalog. Use name='list' for all available skills. Free - no API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Skill 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.
| Name | Type | Req | Description |
|---|---|---|---|
| checklist_type | string | — | Checklist type |
| language | string | — | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | SEO topic or 'list' for all topics |
No output schema declared.
No examples provided.