INDIVIDUAL MCP TOOL

check_schema

Fetch a LIVE URL and extract all structured data: every JSON-LD block (with @types, flagging invalid JSON) plus microdata itemtypes.

pocketseo.ainone authenticationAvailability not checked

LIVE ENDPOINT

https://pocketseo.ai/mcp

No auth detected

Connect to this endpoint to inspect the live schema for check_schema and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

A tool name or description suggests retrieving external content.

Parent server

pocketseo.ai

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.pocketseo]
url = "https://pocketseo.ai/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "pocketseo": {
      "type": "http",
      "url": "https://pocketseo.ai/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: pocketseo
Remote MCP URL: https://pocketseo.ai/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "pocketseo": {
      "url": "https://pocketseo.ai/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "pocketseo": {
      "type": "http",
      "url": "https://pocketseo.ai/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "pocketseo",
  "transport": "streamable-http",
  "url": "https://pocketseo.ai/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

audit_page — Fetch a LIVE URL and run an on-page SEO audit: title & meta-description length, single-H1 & heading hierarchy, word count / thin-content, image-alt coverage, canonical, viewport, html lang, robots-meta indexability, Open Graph + Twitter tags, and a JS-rendered content warning.
check_ai_readiness — Fetch a LIVE URL and score it for AI search / GEO / AEO: are AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot) allowed, is there an /llms.txt, is the content server-rendered (not JS-only), does it open answer-first, are there question headings and citable schema (FAQ/Article), and is it fresh (dateModified).
check_technical — Fetch a LIVE URL and report technical SEO signals: HTTPS, status code, redirect chain, response time, HSTS + security headers, compression, and hreflang.
analyze_headings — Fetch a LIVE URL and return its heading outline, word count, thin-content flag, and readability.
check_meta_tags — Fetch a LIVE URL and dump every meta / Open Graph / Twitter / canonical / robots tag with issues flagged (missing title/description, over-length description, duplicate canonical, noindex, bare social preview).
suggest_meta — Fetch a LIVE URL and return its current title/description plus page signals (H1, first paragraph, optional target keyword) and the length/keyword rules, so YOU can rewrite an improved title and meta description.
check_robots — Fetch and parse a site's /robots.txt and report whether the given URL path is crawlable by Googlebot, Bingbot, and AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot).
check_sitemap — Locate a site's XML sitemap (via robots.txt, /sitemap.xml, /sitemap_index.xml), validate the XML, count URLs, follow a sitemap index, and report whether the given URL is listed.