Skip to content

SeekinWeb — AI visibility MCP server

com.seekinweb/ai-visibilityseekinweb.comstreamable-httpv1.1.0Scanned

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

3 tools: 3 change things.

Tools: 0 delete, 0 irreversible, 3 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 3
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the SeekinWeb — AI visibility MCP server can do

The SeekinWeb — AI visibility MCP server is published by seekinweb.com, a domain the MCP Registry verified. It has 3 tools. It can create or change data (3 tools: check_ai_recommendations, scan_website and generate_llms_txt), but cannot delete data. None of its tools only reads.

3 tools bring in text other people can write (check_ai_recommendations, scan_website and generate_llms_txt); 3 tools can send data out of your system (check_ai_recommendations, scan_website and generate_llms_txt).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 14, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 3Claude Code: ask
  • check_ai_recommendationsChecks whether an AI assistant with live web search recommends a business when a customer asks for what it offers, without naming it.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check AI recommendations
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • generate_llms_txtDrafts 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.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The name "generate_llms_txt" says "generate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "generate_llms_txt" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "generate_llms_txt" says "generate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Generate llms.txt
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • scan_websiteScans a website and returns its AI Visibility Score (0-100): whether AI crawlers and agents can find, read and cite it.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Scan AI readability
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:46 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://seekinweb.com/api/mcp: tools/list returned 3 tools to an anonymous client, including check_ai_recommendations (write), scan_website (write), generate_llms_txt (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "generate_llms_txt" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "generate_llms_txt" says "generate": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http ai-visibility https://seekinweb.com/api/mcp
claude mcp add --transport http ai-visibility https://seekinweb.com/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__ai-visibility__check_ai_recommendations",
      "mcp__ai-visibility__scan_website",
      "mcp__ai-visibility__generate_llms_txt"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ai-visibility. Review it before you use it.

Capability tags behind 3 rules
  • mcp__ai-visibility__check_ai_recommendations untrusted-input, outbound
  • mcp__ai-visibility__scan_website untrusted-input, outbound
  • mcp__ai-visibility__generate_llms_txt untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.seekinweb/ai-visibility/verify?hash=b06cbc2b1cfd4370acd998390e73386cc38e8f13946042bdcdc03426f1d65820" | jq -e '.changed == false'

Pinned hash b06cbc2b1cfd, from Nov 14, 2026, 07:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.seekinweb/ai-visibility/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.seekinweb/ai-visibility
[![Anlyon Radar](https://radar.anlyon.com/badge/com.seekinweb/ai-visibility.svg)](https://radar.anlyon.com/servers/com.seekinweb/ai-visibility)

Source: MCP Registry. Synced Oct 21, 2026, 18:04 UTC.

SeekinWeb — AI visibility MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the SeekinWeb — AI visibility MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the SeekinWeb — AI visibility MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the SeekinWeb — AI visibility MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the SeekinWeb — AI visibility MCP server have?

3 tools: 3 write. check_ai_recommendations, scan_website and generate_llms_txt.

Does the SeekinWeb — AI visibility MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the SeekinWeb — AI visibility MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_ai_recommendations, scan_website and generate_llms_txt.

Has the SeekinWeb — AI visibility MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.