FUTIA
io.futia/seo · 0.1.0
SEO answers for AI agents: Search Console reads free, plus competitor, keyword, backlink, SERP data.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://futia.io/api/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 8 tools.
- Protocol
- 2025-06-18
- Calls itself
- futia 0.1.0
- Handshake time
- 375 ms
- HTTP status
- 200
The tools it lists (8, as of 8 hours ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
index_coverageHas 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.
page_yieldWhich 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.
query_matchWhich 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.
competitor_gapTopics 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.
keyword_volumeSearch 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.
backlink_profileReferring 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.
serp_position
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
io.futia/seo, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 73 days ago. The registry entry · futia.io