SeoPerseo

com.seoperseoPublished by seoperseo.comOfficial publisherv1.0.0Updated Oct 24, 2026

SEO, GEO & AI Visibility intelligence directly inside AI assistants.

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

A remote MCP server that brings SEO, GEO and AI visibility intelligence into AI assistants.

What you can do
SeoPerseo is a hosted MCP endpoint that connects an AI assistant to SEO, GEO and AI visibility intelligence. The manifest lists no tools, so the specific capabilities are not documented in the supplied material. Access is over streamable HTTP at a remote endpoint.
When to use it
Consider it when you want an assistant to work with SEO, generative engine optimization or AI visibility insights without leaving the chat. It is not a fit if you need documented tool behavior before connecting, since no tool list is provided.
Requirements
A remote MCP client that supports streamable HTTP, plus OAuth authentication with the provider. No packages, environment variables or headers are declared.
Before you install
Authentication is OAuth-based and required, so you will grant the service access to your account. No tool list is published, so what data the server reads or changes is unclear; review the OAuth scopes before authorizing.

Installation

In SourceWeft

  1. Open SeoPerseo in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.seoperseo%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "seoperseo": {
      "type": "http",
      "url": "https://seoperseo.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 14, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.