SeekinWeb — AI visibility

Does AI recommend a business? Who it names instead, which sources it uses, plus AI readability.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
100%
Naming quality
93%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~635Tokens (tool definitions)
~981 BTypical response size
Minimal attention impact (0.50% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "ai-visibility": {
      "url": "https://seekinweb.com/api/mcp"
    }
  }
}

Remote endpoints

https://seekinweb.com/api/mcpstreamable-http

What it can do

Tool inventory

Tools (3)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢check_ai_recommendations(url, lang)

Checks whether an AI assistant with live web search recommends a business when a customer asks for what it offers, without naming it. Returns how many answers named the business, which brands were named instead, which websites the assistant relied on (the sources to be present on), and what the assistant says about the business. Runs in the background on first use (about a minute): if it reports that the test is running, call it again shortly. Free, no account.

Input Schema

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "Domain or URL of the site, e.g. \"example.com\" or \"https://example.com\". Use your own site or one you are authorized to review."
    },
    "lang": {
      "type": "string",
      "enum": [
        "en",
        "es"
      ],
      "description": "Output language: \"en\" (default) or \"es\"."
    }
  },
  "required": [
    "url"
  ]
}
🟢scan_website(url, lang)

Scans a website and returns its AI Visibility Score (0-100): whether AI crawlers and agents can find, read and cite it. Eight weighted signals (content readable without JavaScript, AI crawler access in robots.txt, structured data, semantic structure, metadata, performance, llms.txt, sitemap), each with a concrete fix when it fails. Free, no account.

Input Schema

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "Domain or URL of the site, e.g. \"example.com\" or \"https://example.com\". Use your own site or one you are authorized to review."
    },
    "lang": {
      "type": "string",
      "enum": [
        "en",
        "es"
      ],
      "description": "Output language: \"en\" (default) or \"es\"."
    }
  },
  "required": [
    "url"
  ]
}
🟢generate_llms_txt(url, lang)

Drafts an llms.txt file (llmstxt.org convention) for the root of a domain: a structured summary of the site for language models and agents, derived from the page's real content. Returns the file text. Note: llms.txt is an emerging convention with unproven impact.

Input Schema

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "Domain or URL of the site, e.g. \"example.com\" or \"https://example.com\". Use your own site or one you are authorized to review."
    },
    "lang": {
      "type": "string",
      "enum": [
        "en",
        "es"
      ],
      "description": "Output language: \"en\" (default) or \"es\"."
    }
  },
  "required": [
    "url"
  ]
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded3 tools