FUTIA
REMOTE · FUTIA.IO · SCANNED AUG 21
SEO answers for AI agents: Search Console reads free, plus competitor, keyword, backlink, SERP data.
Available components
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety–
Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 4 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the FUTIA MCP server?
FUTIA is a hosted endpoint at https://futia.io/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · futia.io
claude mcp add --transport http io-futia-seo 'https://futia.io/api/mcp'
{
"mcpServers": {
"io-futia-seo": {
"url": "https://futia.io/api/mcp"
}
}
} {
"servers": {
"io-futia-seo": {
"type": "http",
"url": "https://futia.io/api/mcp"
}
}
} [mcp_servers.io-futia-seo] url = "https://futia.io/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-futia-seo": {
"type": "remote",
"url": "https://futia.io/api/mcp",
"enabled": true
}
}
} openclaw mcp add io-futia-seo --url 'https://futia.io/api/mcp' --transport streamable-http
mcp_servers:
io-futia-seo:
url: "https://futia.io/api/mcp" {
"McpServers": {
"io-futia-seo": {
"Transport": "http",
"Url": "https://futia.io/api/mcp"
}
}
} assistant mcp add io-futia-seo -t streamable-http -u 'https://futia.io/api/mcp'
{
"mcpServers": {
"io-futia-seo": {
"type": "http",
"url": "https://futia.io/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Aug 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Aug 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 15 Aug 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 13 Aug 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 7 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.30 → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 5 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Aug 2026 · Probed https://futia.io/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=futia.io | CN=YE2,O=Let's Encrypt,C=US | 28 Jul 2026 | 26 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6b7952044708c42dc61a58e56f8f47e0232 |
| SANs: futia.io, www.futia.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of futia.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| futia.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://futia.io/api/mcp | Verified | 200 | |
| http (plaintext) | http://futia.io/api/mcp | HTTPS enforced | 301 | https://futia.io/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
account_status Account status ~45
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
backlink_profile Backlink profile ~61
Referring domains, link count, domain rank and a reading of what they mean. Deliberately does not return the raw link list: a thousand rows of links fills an agent's context without producing a decision.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | Search Console property |
No output schema declared.
No examples provided.
competitor_gap Competitor gap ~86
Topics a real competitor ranks for and you do not. Competitors are chosen by how much of their keyword set overlaps with yours, not by raw overlap count: raw count returns social networks that rank for everything. Gap keywords are filtered against your existing vocabulary.
| Name | Type | Req | Description |
|---|---|---|---|
| competitor | string | – | Optional. If omitted we pick one by overlap ratio. |
| site | string | yes | Search Console property |
No output schema declared.
No examples provided.
index_coverage Index coverage ~97
Has Google seen your pages? Works with zero traffic data, so it is useful from a site's first day. Returns which URLs are indexed, which were crawled but not indexed, which were never discovered, and where Google picked a different canonical than you declared.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | Search Console property, e.g. sc-domain:example.com |
| urls | array | – | Optional. Defaults to URLs found in the site's sitemap. |
No output schema declared.
No examples provided.
keyword_volume Keyword volume ~73
Search volume and difficulty for keywords you name, each with a verdict on whether this particular site can realistically reach it. The verdict is measured against the difficulty of keywords the site already ranks for, not a universal threshold.
| Name | Type | Req | Description |
|---|---|---|---|
| keywords | array | yes | Up to 100 keywords |
| site | string | yes | Search Console property |
No output schema declared.
No examples provided.
page_yield Page yield ~95
Which of your pages are dead, why, and which to fix first. Splits pages into no_demand, title_not_earning and ranking_too_low, then orders the fix list by recoverable clicks using the site's own click-through curve rather than borrowed industry averages.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Lookback window, 7 to 180. Defaults to 90. |
| site | string | yes | Search Console property |
No output schema declared.
No examples provided.
query_match Query match ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Lookback window, 7 to 180 |
| site | string | yes | Search Console property |
No output schema declared.
No examples provided.
serp_position SERP position ~56
For queries you name: who is on the results page, where you sit among them, and which domains are consistently above you.
| Name | Type | Req | Description |
|---|---|---|---|
| keywords | array | yes | Up to 10 queries |
| site | string | yes | Search Console property |
No output schema declared.
No examples provided.
What is the FUTIA MCP server?
FUTIA is an MCP server listed in the public MCP registry as io.futia/seo. SEO answers for AI agents: Search Console reads free, plus competitor, keyword, backlink, SERP data. This page covers its hosted endpoint (https://futia.io/api/mcp).
Is the FUTIA MCP server safe to use?
FUTIA scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the FUTIA MCP server expose?
FUTIA exposes 8 tools: index_coverage, page_yield, query_match, competitor_gap, keyword_volume, and 3 more. Their descriptions and schemas cost roughly 597 tokens of context every time the server is loaded.
Does the FUTIA MCP server require authentication?
No. We connected to FUTIA without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FUTIA MCP server still maintained?
FUTIA has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 6 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.