
SEO-Ghost
io.github.EvozimPublished by GitHub account Evozimv1.0.0Updated Oct 24, 2026
AEO intent and search presence optimization engine.
Overview
A remote MCP endpoint for an AEO intent and search presence optimization engine, letting an assistant work on search visibility tasks.
- What you can do
- The server is described only as an AEO intent and search presence optimization engine, and no tools are listed in the manifest. It is a remote endpoint reached over SSE, so an assistant connects to it rather than running it locally. Premium settlement is mentioned, implying some capabilities are gated behind a payment step. Beyond that, the available material does not specify what actions the assistant can perform.
- When to use it
- Consider it when you want an assistant to help with answer-engine optimization, search intent, or search presence work and you are willing to connect to a third-party remote endpoint. It is not suitable if you need a documented, tool-by-tool description before connecting.
- Requirements
- A remote SSE endpoint at the provider's hosted address; nothing needs to be installed locally. Premium settlement requires a payment-signature header carrying a Base64-encoded EIP-3009 TransferWithAuthorization signature. No accounts, environment variables, or other credentials are declared.
Installation
In SourceWeft
- Open SEO-Ghost in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via SSE. 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/io.github.Evozim%2Fseo-ghost/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"seo-ghost": {
"type": "sse",
"url": "https://seo-ghost-mcp.vercel.app/api/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 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 listedRequired15 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.