Skip to content

ai-visibility MCP server

com.lastminutedealshq/ai-visibilitylastminutedealshq.comstreamable-httpv1.0.1Scanned

AI-search-visibility tools: check crawler access, generate llms.txt, lint robots.txt, census data.

4 tools: 3 change things and 1 only read.

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

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 ai-visibility MCP server can do

The ai-visibility MCP server is published by lastminutedealshq.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (3 tools: check_site, generate_llms_txt and lint_robots_txt), but cannot delete data. 1 tool only reads.

4 tools can send data out of your system (check_site, generate_llms_txt, validate_llms_txt and 1 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 13, 2026, version 1.0.1.

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.

4 tools

Changes things 3Claude Code: ask
  • check_siteCheck a site's AI search visibility: which AI crawlers (OAI-SearchBot, PerplexityBot, GPTBot, ClaudeBot and more) robots.txt allows, whether the homepage ships readable text withou…Can 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.

    What it can reach

    • 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
    Check a site's AI search visibility: which AI crawlers (OAI-SearchBot, PerplexityBot, GPTBot, ClaudeBot and more) robots.txt allows, whether the homepage ships readable text without JavaScript, and whether an llms.txt exists.
  • generate_llms_txtGenerate an llms.txt file from a site's real pages and sitemap.Can send data outNo findings

    Why it is in this group

    • The name "generate_llms_txt" says "generate": a word for a change.

    What it can reach

    • 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
    Generate an llms.txt file from a site's real pages and sitemap.
  • lint_robots_txtLint a robots.txt for AI-crawler-specific mistakes.Can 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.

    What it can reach

    • 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
    Lint a robots.txt for AI-crawler-specific mistakes. Pass url to fetch it live, or robots_txt to lint pasted text directly.
Only reads 1Show 1 read-only tool
  • validate_llms_txtValidate an existing llms.txt against the spec.Can send data outNo findings

    Why it is in this group

    • The name "validate_llms_txt" says "validate": a word for reading.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Validate an existing llms.txt against the spec.

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 or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out4
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:41 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://ai-visibility.lastminutedealshq.com/mcp: tools/list returned 4 tools to an anonymous client, including check_site (write), generate_llms_txt (write), lint_robots_txt (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

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.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http ai-visibility https://ai-visibility.lastminutedealshq.com/mcp
claude mcp add --transport http ai-visibility https://ai-visibility.lastminutedealshq.com/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_site",
      "mcp__ai-visibility__generate_llms_txt",
      "mcp__ai-visibility__validate_llms_txt",
      "mcp__ai-visibility__lint_robots_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 4 rules
  • mcp__ai-visibility__check_site outbound
  • mcp__ai-visibility__generate_llms_txt outbound
  • mcp__ai-visibility__validate_llms_txt outbound
  • mcp__ai-visibility__lint_robots_txt 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.lastminutedealshq/ai-visibility/verify?hash=db1b7a5685ef6f46c608ef8990ae77158fa332dc0c392eee4d374f34c9f8f678" | jq -e '.changed == false'

Pinned hash db1b7a5685ef, from Nov 13, 2026, 15:18 UTC.

Watch

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

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

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

Badge

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

Source: MCP Registry. Synced Oct 21, 2026, 17:58 UTC.

ai-visibility MCP server: questions and answers

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

Is the ai-visibility MCP server safe?

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

Can the 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 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 ai-visibility MCP server have?

4 tools: 3 write, 1 read. check_site, generate_llms_txt, lint_robots_txt and validate_llms_txt.

Does the ai-visibility MCP server need sign-in or OAuth?

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

Does the ai-visibility MCP server send data to outside services?

4 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_site, generate_llms_txt, validate_llms_txt and lint_robots_txt.

Has the ai-visibility MCP server changed its tools?

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