Hosted MCP server/Development

SEO+GEO Audit MCP server

Hosted at mcp.apify.com·Streamable HTTP

SEO/GEO Audit MCP audits a URL for traditional SEO and generative-engine visibility. It returns a 0-100 visibility score, per-category scores, prioritized findings marked CRITICAL, WARNING or OK, and a remediation checklist. The four tools are audit_url, audit_deep, get_checklist and report_issue; audit_deep adds a Cloudflare Search/Agent-versus-Training crawler sweep and directory discovery. Run it through Apify with an API token. Pricing starts at $0.50 per 1,000 audit_url calls, and initialize and tools/list are free.

mcp.apify.com Streamable HTTP Apify API token (Bearer) Server not checked yet Reviewed 2026-11-16
About

Where it fits

SEO consultants and site owners who want both classic on-page checks and AI-search visibility signals from one agent call.

  • Audit a page with audit_url and read the 0-100 score.
  • Run audit_deep to check crawler access and GEO discovery.
  • Pull a severity-tagged remediation checklist with get_checklist.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds SEO+GEO Audit as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http seo-geo-audit https://mcp.apify.com/?actors=neeenja/seo-geo-audit-mcp --header "Authorization: Bearer YOUR_APIFY_TOKEN" --scope project
  2. 02

    Send the credential

    The provider expects the following header. Replace each placeholder with your own key or token before you connect.

    Required headers
    Authorization: Bearer YOUR_APIFY_TOKEN
  3. 03

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://mcp.apify.com/?actors=neeenja/seo-geo-audit-mcp
Host
mcp.apify.com
Transport
Streamable HTTP
Authentication
Apify API token (Bearer)
Server name
seo-geo-audit
Listing type
Community or directory listing

The installer uses the server name seo-geo-audit. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that seo-geo-audit appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Audit a page with audit_url and read the 0-100 score. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

SEO+GEO Audit documentationhttps://apify.com/neeenja/seo-geo-audit-mcp