# io.tranx/alice

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

- name: io.tranx/alice
- version: 0.1.0
- connection class: R0 (autonomous)
- trust: 83/100 flags: no-repository
- quality: 85/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.tranx%2Falice
- tools: https://api.protogrid.dev/v1/servers/io.tranx%2Falice/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "alice": {
      "type": "http",
      "url": "https://tranx.io/api/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% +updated-27d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 85/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 86 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 2 of 2 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: check_ai_visibility (idempotentHint); compare_ai_visibility (idempotentHint)
- pass `tools.token_cost`: about 1,333 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: 2 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 2, about 1,333 tokens to load them all
- tool set hash: eff8ebc4b129da5c054104ee1e1f0628
- tools last changed: 2026-10-14T08:15:44.443Z
- badge: [![protogrid quality](https://protogrid.dev/badge/io.tranx/alice.svg)](https://protogrid.dev/servers/io.tranx/alice)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-14 `compare_ai_visibility` changed (description, inputSchema)
  - before: 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.
  - after: 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.
- 2026-10-14 `check_ai_visibility` changed (inputSchema)

Full history: https://api.protogrid.dev/v1/servers/io.tranx%2Falice/changes

## Remotes

- https://tranx.io/api/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (2)

- `check_ai_visibility`: 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.
- `compare_ai_visibility`: 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.