mcp-registry/io.futia/seo · v0.1.0
As of 2026-10-20 18:49 UTC, the Futia Seo MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 7 minutes.
SEO answers for AI agents: Search Console reads free, plus competitor, keyword, backlink, SERP data.
Claude Code
claude mcp add --transport http futia-seo-mcp-server https://futia.io/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"futia-seo-mcp-server": {
"type": "http",
"url": "https://futia.io/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
8 of 8 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Handshake + tools/list takes ~2,084 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.futia%2Fseo/fixes
{
"name": "account_status",
"description": "Free and instant: remaining monthly budget, credit balance, when the budget resets, and which endpoints stay free. Check this before a paid call if you are unsure the budget covers it.",
"inputSchema": {
"type": "object",
"required": [],
"properties": {}
},
"annotations": {
"readOnlyHint": true
},
"title": "Account status"
}{
"name": "query_match",
"description": "Which queries are one step away, and which were never yours. Returns queries stuck at ranks 11-20 with real volume, queries you rank well for but nobody clicks (intent mismatch), and queries several of your pages compete for without earning clicks.",
"inputSchema": {
"type": "object",
"required": [
"site"
],
"properties": {
"days": {
"type": "number",
"description": "Lookback window, 7 to 180"
},
"site": {
"type": "string",
"description": "Search Console property"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Query match"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.futia/seo"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.futia/seo"}) over MCP.
index_coverage ~163 tokenscompetitor_gap ~152 tokenskeyword_volume ~145 tokenspage_yield ~142 tokensquery_match ~135 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.futia%2Fseo?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.futia%2Fseo?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.futia%2Fseo.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.futia%2Fseo.svg :target: https://glimind.com/server/mcp-registry%2Fio.futia%2Fseo?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:f42bc9045e46ea5e…, first seen 2026-10-17, included at leaf 1760 of 34,527. Version history · verify what your client received.
Compare: most reliable account servers · most reliable data servers · most reliable knowledge servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-20 18:49 UTC, the Futia Seo MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 7 minutes.
Futia Seo MCP server advertises 8 tools, including account_status, backlink_profile, competitor_gap, index_coverage, keyword_volume.
Point your MCP client at this streamable-http endpoint: https://futia.io/api/mcp
Glimind scanned all 8 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.