Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.tranx/alice

REMOTE · TRANX.IO

Audit any site's AI visibility from your assistant: crawler access, rendering, and schema.

Available components

+2 this week 86 Trust /100

Last scanned (21 hours ago)

Scores higher than 88% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 466 tokens (~233/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 16 Nov 26 +2
    • Schema quality: 274 → 233 ▲ functional
    • MCP protocol: fail → pass ▲ functional
    • Schema quality: good → excellent functional
    • MCP protocol version: 2025-06-18 → 2026-07-28 functional
    • Server version: 0.1.0 → 0.2.0 functional
    • “compare_ai_visibility” dropped the optional parameter “country” cosmetic
    • “compare_ai_visibility” dropped the optional parameter “language” cosmetic
    • “compare_ai_visibility” dropped the optional parameter “locale” cosmetic
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “check_ai_visibility” rewrote its description, which is the text the model reads security
  • 23 Oct 26 84
    • Stability: 0.97 → pass security
  • 15 Oct 26 0
    • Tool “compare_ai_visibility” rewrote its description, which is the text the model reads security
    • Schema quality: 182 → 271 ▼ functional
    • Schema quality: excellent → good functional
    • “check_ai_visibility” added an optional parameter “country” cosmetic
    • “check_ai_visibility” added an optional parameter “language” cosmetic
    • “check_ai_visibility” added an optional parameter “locale” cosmetic
    • “compare_ai_visibility” added an optional parameter “country” cosmetic
    • “compare_ai_visibility” added an optional parameter “language” cosmetic
    • “compare_ai_visibility” added an optional parameter “locale” cosmetic
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://tranx.io/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.tranx.io CN=Amazon RSA 2048 M04,O=Amazon,C=US 5 Aug 2026 18 Feb 2027 RSA 2048 SHA256-RSA cfbfb979776ea63567c110ce568152a
SANs: *.tranx.io, tranx.io
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of tranx.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
tranx.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://tranx.io/api/mcp Verified 200
http (plaintext) http://tranx.io/api/mcp HTTPS enforced 301 https://tranx.io/api/mcp
MCP tools · 2 exposed · ~401 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_ai_visibility ~274

Check whether AI names a website when buyers ask, and whether AI can read it. Starts a live check of one brand-name question and one buyer question on Google AI Overviews, ChatGPT, Claude and Gemini (results fill in on the report link within about a minute), and returns a 0-100 AI readability score: which AI crawlers the site allows or blocks, whether content is server-rendered, structured-data coverage, and the highest-impact fixes. Use when someone asks whether ChatGPT, Claude, Gemini or Google AI mention or cite their site, how their site appears to AI, whether AI can read or find it, or asks for an SEO or AI visibility audit of a URL.

NameTypeReqDescription
countrystring–Scan market country code. Defaults to the page language’s market: us, tw or jp.
fullboolean–Include classic SEO, crawlability and analytics-tag sections. Default returns AI visibility only.
languagestring–AI question/probe language code, e.g. en, zh-tw or ja. Defaults to the selected country’s language.
localestring–Saved-report page language: en, zh-TW or ja. Independent of the scan market.
urlstringyesSite or page URL. Scheme optional; https:// is assumed.
NameTypeReqDescription
ai_checkobject–The live brand-name / buyer-question check across the AI engines. status "checking" means the engines are still answering; the report_url shows the settled result.
checksobjectyes–
gatedboolean––
next_stepstringyes–
report_urlstring––
scanned_atstring––
scoreinteger|nullyes–
score_breakdownobject––
top_actionsarrayyes–
urlstringyes–

No examples provided.

compare_ai_visibility ~127

Compare how visible several websites are to AI answer engines, side by side. Scans 2-4 URLs and ranks them by AI visibility score, showing which blocks AI crawlers, which is server-rendered, and which has answer-ready structured data. Use when someone wants to benchmark their site against competitors, or asks why a competitor gets recommended by AI assistants and they do not. This compares technical readability only; it does not test live AI mentions.

NameTypeReqDescription
urlsarrayyesTwo to four site URLs. Put the user’s own site first; results are returned ranked by score.
NameTypeReqDescription
gatedboolean––
next_stepstringyes–
rowsarrayyes–

No examples provided.

Install

How do I install the io.tranx/alice MCP server?

io.tranx/alice is a hosted endpoint at https://tranx.io/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · tranx.io

# add to Claude Code
claude mcp add --transport http io-tranx-alice 'https://tranx.io/api/mcp'
Common questions

What is the io.tranx/alice MCP server?

io.tranx/alice is an MCP server listed in the public MCP registry as io.tranx/alice. Audit any site's AI visibility from your assistant: crawler access, rendering, and schema. This page covers its hosted endpoint (https://tranx.io/api/mcp).

Is the io.tranx/alice MCP server safe to use?

io.tranx/alice scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.tranx/alice MCP server expose?

io.tranx/alice exposes 2 tools: check_ai_visibility, compare_ai_visibility. Their descriptions and schemas cost roughly 401 tokens of context every time the server is loaded.

Does the io.tranx/alice MCP server require authentication?

No. We connected to io.tranx/alice without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.tranx/alice MCP server still maintained?

io.tranx/alice is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.tranx/alice MCP server?

VerifyMCP ran 13 checks on io.tranx/alice, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.