WebAISEO - AI-search readiness check MCP server
uk.truetest/ai-searchtruetest.ukstreamable-httpv1.0.1Scanned
FREE check: can AI search engines find, read and trust your web page? Fixes listed per page
1 tool: 1 change things.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 1
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. anlyon.dev only lists and labels, and these labels are the same either way.
What the WebAISEO - AI-search readiness check MCP server can do
The WebAISEO - AI-search readiness check MCP server is published by truetest.uk, a domain the MCP Registry verified. It has 1 tool. It can create or change data (1 tool: check_ai_readiness), but cannot delete data. None of its tools only reads.
1 tool brings in text other people can write (check_ai_readiness); 1 tool can send data out of your system (check_ai_readiness).
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.dev first saw them.
Last scanned Nov 10, 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.
1 tool
Changes things 1Claude Code: ask
check_ai_readinessCall when: a user asks whether a web page can be found, read and trusted by AI search engines (ChatGPT search, Claude, Perplexity, Copilot, Gemini).Reads text others writeCan send data out1 finding
Why it is in this group
- The description's first verb is "call": 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 "check_ai_readiness" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "call": a word for a change.
Description, as the server wrote it Call when: a user asks whether a web page can be found, read and trusted by AI search engines (ChatGPT search, Claude, Perplexity, Copilot, Gemini). Fetches that one public page once. Returns score, grade, top fixes and every check. Do not call: for private or intranet addresses (refused), to monitor a site repeatedly, or to measure actual AI citations.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Check a web page's AI-search readiness
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 write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- 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.
Looked at Nov 11, 2026, 09:20 UTC, unchanged since Nov 11, 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
- 1
- 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 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://truetest.uk/mcp/ai-search: tools/list returned 1 tool to an anonymous client, including check_ai_readiness (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "check_ai_readiness" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "call": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:check_ai_readinessChanges thingsinputSchema
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http ai-search https://truetest.uk/mcp/ai-searchclaude mcp add --transport http ai-search https://truetest.uk/mcp/ai-searchRun 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.
{
"permissions": {
"allow": [],
"ask": [
"mcp__ai-search__check_ai_readiness"
],
"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-search. Review it before you use it.
Capability tags behind 1 rule
- mcp__ai-search__check_ai_readiness 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://anlyon.dev/api/v1/servers/uk.truetest/ai-search/verify?hash=c817ca0aefdaeb871e18f64df85d9a7140e8fefc75ab99f0daa0318ca9243e87" | jq -e '.changed == false'Pinned hash c817ca0aefda, from Nov 10, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/uk.truetest/ai-search/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/uk.truetest/ai-search)Source: MCP Registry · repository. Synced Nov 10, 2026, 16:18 UTC.
WebAISEO - AI-search readiness check MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the WebAISEO - AI-search readiness check MCP server safe?
- No scan can promise that. What its definitions show: 1 tool, 1 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 WebAISEO - AI-search readiness check MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the WebAISEO - AI-search readiness check 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 WebAISEO - AI-search readiness check MCP server have?
- 1 tool: 1 write. check_ai_readiness.
Does the WebAISEO - AI-search readiness check MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the WebAISEO - AI-search readiness check MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_ai_readiness.
Has the WebAISEO - AI-search readiness check MCP server changed its tools?
- Yes, once since anlyon.dev started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.