Home / MCP registry index / io.usefulapi/spyfu

SpyFu MCP by usefulapi

io.usefulapi/spyfu in the official MCP registry. Endpoint https://spyfu.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.

The registry describes it as: Read domain stats, competitors, keywords, rankings and ad history in SpyFu.

We read its 19 tools on 2026-11-02. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again about every two weeks.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http spyfu https://spyfu.usefulapi.io/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "spyfu": {
      "url": "https://spyfu.usefulapi.io/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"spyfu","type":"http","url":"https://spyfu.usefulapi.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

spyfu_get_domain_stats spyfu_get_domain_stats_history spyfu_get_domain_stats_for_month spyfu_get_bulk_domain_stats spyfu_find_matching_domains spyfu_get_top_competitors spyfu_get_competing_keywords spyfu_get_seo_keywords spyfu_get_outranking_keywords spyfu_get_top_pages spyfu_get_serp_analysis spyfu_get_ranking_history spyfu_get_keyword_information spyfu_get_related_keywords spyfu_get_ppc_keywords spyfu_get_paid_serps spyfu_get_domain_ad_history spyfu_get_term_ad_history spyfu_get_api_usage

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-02): 30815e7ad53774a0. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-usefulapi-spyfu/badge.svg)](https://lazaretto.dev/mcp-registry/io-usefulapi-spyfu)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.