io.tranx/alice
REMOTE · TRANX.IO · SCANNED SEP 27
Audit any site's AI visibility from your assistant: crawler access, rendering, and schema.
Available components
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 364 tokens (~182/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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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
claude mcp add --transport http io-tranx-alice 'https://tranx.io/api/mcp'
{
"mcpServers": {
"io-tranx-alice": {
"url": "https://tranx.io/api/mcp"
}
}
} {
"servers": {
"io-tranx-alice": {
"type": "http",
"url": "https://tranx.io/api/mcp"
}
}
} [mcp_servers.io-tranx-alice] url = "https://tranx.io/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-tranx-alice": {
"type": "remote",
"url": "https://tranx.io/api/mcp",
"enabled": true
}
}
} openclaw mcp add io-tranx-alice --url 'https://tranx.io/api/mcp' --transport streamable-http
mcp_servers:
io-tranx-alice:
url: "https://tranx.io/api/mcp" {
"McpServers": {
"io-tranx-alice": {
"Transport": "http",
"Url": "https://tranx.io/api/mcp"
}
}
} assistant mcp add io-tranx-alice -t streamable-http -u 'https://tranx.io/api/mcp'
{
"mcpServers": {
"io-tranx-alice": {
"type": "http",
"url": "https://tranx.io/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 25 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
- 24 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 23 Sept 26 71
First indexed and scored.
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 27 Sept 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. | present | 57355 | 8 | Verified |
| tranx.io. | absent | 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 |
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 →
check_ai_visibility Check AI visibility ~188
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 and Claude (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 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.
| Name | Type | Req | Description |
|---|---|---|---|
| full | boolean | – | Include classic SEO, crawlability and analytics-tag sections. Default returns AI visibility only. |
| url | string | yes | Site or page URL. Scheme optional; https:// is assumed. |
| Name | Type | Req | Description |
|---|---|---|---|
| ai_check | object | – | 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. |
| checks | object | yes | – |
| gated | boolean | – | – |
| next_step | string | yes | – |
| report_url | string | – | – |
| scanned_at | string | – | – |
| score | integer|null | yes | – |
| score_breakdown | object | – | – |
| top_actions | array | yes | – |
| url | string | yes | – |
No examples provided.
compare_ai_visibility Compare AI visibility ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| urls | array | yes | Two to four site URLs. Put the user’s own site first; results are returned ranked by score. |
| Name | Type | Req | Description |
|---|---|---|---|
| gated | boolean | – | – |
| next_step | string | yes | – |
| rows | array | yes | – |
No examples provided.
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 73 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 301 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 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.