Skip to content

Tsoden AI Visibility Audit MCP server

ai.tsoden.serp/ai-visibility-auditserp.tsoden.aistreamable-httpv1.0.1Scanned

Live checks: AI crawler access, llms.txt, entity schema and AI-search readiness of any site.

6 tools: 2 change things and 4 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

2 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 Tsoden AI Visibility Audit MCP server can do

The Tsoden AI Visibility Audit MCP server is published by serp.tsoden.ai, a domain the MCP Registry verified. It has 6 tools. It can create or change data (2 tools: audit_ai_readiness and check_ai_crawler_access), but cannot delete data. 4 tools only read.

1 tool reads private data (check_schema_readiness); 4 tools bring in text other people can write (audit_ai_readiness, check_ai_crawler_access, check_schema_readiness and 1 more); 4 tools can send data out of your system (audit_ai_readiness, check_ai_crawler_access, check_schema_readiness and 1 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

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, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 22, 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.

6 tools

Changes things 2Claude Code: ask
  • audit_ai_readinessRun a live audit of a website's readiness to be found and quoted by answer engines (ChatGPT, Claude, Gemini, Perplexity, Google AI Overviews) and classic search.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The description's first verb is "run": 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 "audit_ai_readiness" 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 description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Run a live audit of a website's readiness to be found and quoted by answer engines (ChatGPT, Claude, Gemini, Perplexity, Google AI Overviews) and classic search. Fetches the home page and a few internal pages, robots.txt, sitemap.xml and llms.txt, then returns an AI-readiness score (0-100), an SEO hygiene score and pass/warn/fail checks with their meaning. Use it when the user asks whether their site is visible in AI answers or what to fix first.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
    • title: Audit a site's AI-search readiness
  • check_ai_crawler_accessCheck which AI crawlers (GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended and others) a site's robots.txt allows or blocks, and whether its /llms.txt exists and is …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
    Check which AI crawlers (GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended and others) a site's robots.txt allows or blocks, and whether its /llms.txt exists and is valid. Returns a shareable result page on https://serp.tsoden.ai.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
    • title: Check AI crawler access and llms.txt
Only reads 4Show 4 read-only tools
  • check_schema_readinessRead a page's JSON-LD structured data and report which entity signals an answer engine needs to describe the brand confidently (name, URL, logo, description, sameAs profiles, conta…Reads private dataReads text others writeCan send data outNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "contact": it reads contacts.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "read" and "url": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • 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
    Read a page's JSON-LD structured data and report which entity signals an answer engine needs to describe the brand confidently (name, URL, logo, description, sameAs profiles, contact) are present or missing. Returns a shareable result page.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
    • title: Check structured data for answer engines
  • find_prompt_opportunitiesRead a site and suggest the questions people ask answer engines where this brand could plausibly be recommended — the prompts worth tracking and writing content for.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "find_prompt_opportunities" says "find": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • 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
    Read a site and suggest the questions people ask answer engines where this brand could plausibly be recommended — the prompts worth tracking and writing content for. Returns a shareable result page.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
    • title: Find prompts a brand could be cited for
  • get_ai_readiness_benchmarkReturn the public aggregate benchmark from sites checked with these tools: how often AI crawlers are blocked, how common llms.txt is, and how complete entity structured data usuall…No findings

    Why it is in this group

    • The name "get_ai_readiness_benchmark" says "get": a word for reading.
    Description, as the server wrote it
    Return the public aggregate benchmark from sites checked with these tools: how often AI crawlers are blocked, how common llms.txt is, and how complete entity structured data usually is. Use it to put one site's result in context.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: AI-readiness benchmark across checked sites
  • get_startedExplain what Tsoden SERP Checker can check without an account, what a connected account adds (tracked rankings and answer-engine visibility for the user's own projects) and how to …No findings

    Why it is in this group

    • The name "get_started" says "get": a word for reading.
    Description, as the server wrote it
    Explain what Tsoden SERP Checker can check without an account, what a connected account adds (tracked rankings and answer-engine visibility for the user's own projects) and how to connect it. Use it when the user asks how to connect an account or how to track results over time.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: How to connect and what each server does

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.

16 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 private-data tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
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.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__ai-visibility-audit__check_schema_readiness"
    ]
  }
}

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 21, 2026, 19:18 UTC, unchanged since Nov 21, 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
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://serp.tsoden.ai/.well-known/oauth-protected-resource
Authorization servers
https://serp.tsoden.ai
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • WarnThe whole server

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

    Matched text

    https://serp.tsoden.ai/mcp/free: tools/list returned 6 tools to an anonymous client, including audit_ai_readiness (write), check_ai_crawler_access (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "audit_ai_readiness" 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 description's first verb is "run": a word for a change.

    What this check looks for

History

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

  1. Tools1 changed.~1 changedView diff

Install

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

claude mcp add --transport http ai-visibility-audit https://serp.tsoden.ai/mcp/free
claude mcp add --transport http ai-visibility-audit https://serp.tsoden.ai/mcp/free

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": [
      "mcp__ai-visibility-audit__get_ai_readiness_benchmark",
      "mcp__ai-visibility-audit__get_started"
    ],
    "ask": [
      "mcp__ai-visibility-audit__audit_ai_readiness",
      "mcp__ai-visibility-audit__check_ai_crawler_access",
      "mcp__ai-visibility-audit__check_schema_readiness",
      "mcp__ai-visibility-audit__find_prompt_opportunities"
    ],
    "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-audit. Review it before you use it.

Capability tags behind 4 rules
  • mcp__ai-visibility-audit__audit_ai_readiness untrusted-input, outbound
  • mcp__ai-visibility-audit__check_ai_crawler_access untrusted-input, outbound
  • mcp__ai-visibility-audit__check_schema_readiness private-data, untrusted-input, outbound
  • mcp__ai-visibility-audit__find_prompt_opportunities 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/ai.tsoden.serp/ai-visibility-audit/verify?hash=21cdf913ef3fdeb515acdd8898c238ea6b6fb2046681e42cee2e61419c226097" | jq -e '.changed == false'

Pinned hash 21cdf913ef3f, from Nov 22, 2026, 01:18 UTC.

Watch

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

https://radar.anlyon.com/servers/ai.tsoden.serp/ai-visibility-audit/changes.xml

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

Badge

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

Source: MCP Registry · repository. Synced Nov 22, 2026, 01:17 UTC.

Tsoden AI Visibility Audit MCP server: questions and answers

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

Is the Tsoden AI Visibility Audit MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 2 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 Tsoden AI Visibility Audit MCP server delete data?

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

Can the Tsoden AI Visibility Audit 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 Tsoden AI Visibility Audit MCP server have?

6 tools: 2 write, 4 read. audit_ai_readiness, check_ai_crawler_access, check_schema_readiness, find_prompt_opportunities, get_ai_readiness_benchmark and get_started.

Does the Tsoden AI Visibility Audit MCP server need sign-in or OAuth?

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

Does the Tsoden AI Visibility Audit 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): audit_ai_readiness, check_ai_crawler_access, check_schema_readiness and find_prompt_opportunities.

Has the Tsoden AI Visibility Audit MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 22, 2026. Every change is on this page and in its Atom feed.