Skip to content
hey-eye logo

hey-eye MCP server

Which MCP servers are hey-eye's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-13

← Back to hey-eye

Whose server it is
  • Addresshttps://hey-eye.gr/mcpnot in the official registry: answered when asked

No entry in the official MCP registry names this server. It answered on hey-eye.gr when the Atlas asked at the address servers are usually mounted on, so it is the vendor's own. Clients and catalogues that list servers from the registry do not show it.

When we asked itchecked 2026-10-28
  • Stateanswerschecked 2026-10-28
  • Tools2
  • Server calls itselfhey-eye
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 63 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 6 of the 7 days it takes to judge reliability.

Once connected

  • For "Analyze pages to get LLM visibility scores and identify content issues", the likely first call is analyze_url.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 6, the first on 2026-10-28
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
  • Answeredmeasuring6 of the 7 daily checks it takes to print a share
  • Median first answer289 ms
  • Space in an agent's context≈ 433 tokensthe definitions of all its tools (2), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results0 of 2 toolsdeclared outputSchema: results come typed, read once
  • Not saying whether it only reads or can destroy: 2 of 2

What an agent can do with it

  • can do · Analyze pages to get LLM visibility scores and identify content issues
  • not sure · Compare two pages to see competitive differences across visibility pillars
  • not sure · Crawl entire sitemaps and track visibility scores over time

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers2 tools · read 2026-10-28
  • analyze_url

    Analyze any public web page for LLM and AI-search visibility (GEO, Generative Engine Optimization) using hey-eye.gr. Returns an overall score out of 100, a breakdown across four weighted pillars (Structural Integrity, AI Extractability…

  • test_ai_crawler_access

    Test whether AI crawlers and LLM bots (GPTBot, ChatGPT-User, ClaudeBot, Claude-Web, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Bytespider, cohere-ai, Amazonbot) can actually reach a given web page. Checks both the site's…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "hey-eye": {
      "type": "http",
      "url": "https://hey-eye.gr/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http hey-eye https://hey-eye.gr/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://hey-eye.gr/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.