# AISeeWhy

> Can ChatGPT, Claude and Perplexity crawlers read your page? Audit, fixes, compare, monitoring.

- name: com.aiseewhy/aiseewhy
- version: 1.1.1
- connection class: R0 (autonomous)
- trust: 98/100
- quality: 94/100 (new)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.aiseewhy%2Faiseewhy
- tools: https://api.protogrid.dev/v1/servers/com.aiseewhy%2Faiseewhy/tools

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

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "aiseewhy": {
      "type": "http",
      "url": "https://api.aiseewhy.com/mcp",
      "headers": {
        "x-api-key": "${X_API_KEY}"
      }
    }
  }
}
```

Placeholders to fill: `${X_API_KEY}`.

## Trust

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

## Quality 94/100 (new)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### 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: 100 (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`: 6 of 6 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 1,177 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump
- pass `tools.hidden_text`: no hidden text in tool names, descriptions, schemas or annotations

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

- n/a `stability.changes`, `stability.rug_pull`, `stability.new_links`: tool history recorded for 1 of the 7 days needed

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

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

- tools: 6, about 1,177 tokens to load them all
- tool set hash: 1577440c29d133ead162b21e271d35f7
- badge: [![protogrid quality](https://protogrid.dev/badge/com.aiseewhy/aiseewhy.svg)](https://protogrid.dev/servers/com.aiseewhy/aiseewhy)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://api.aiseewhy.com/mcp (streamable-http, auth none, reachable true, uptime30d 0.8333333)

## Packages

_none_

## Tools (6)

- `audit_sitemap`: Audit up to 10 pages listed in a sitemap or sitemap index. Returns one summary line per page plus the full report of every page with findings. Needs an API key.
- `audit_url`: Audit one URL: fetch it as 16 AI and search crawlers plus curl and a browser, check robots.txt, structured data, answer-first content, freshness, hreflang and llms.txt. Returns a Markdown report with findings and fixes. language: report language code (en, de, ja, …).
- `compare_urls`: Audit 2 or 3 URLs (yours and competitors') and compare them side by side: score, P1/P2/P3 counts, blocked crawlers, llms.txt, structured data, text without JavaScript. Needs an API key.
- `explain_finding`: Explain a finding id (e.g. access.blocked, robots.disallowed, schema.software_no_offers) in the given language: what it means, why it matters for AI search and how to fix it.
- `list_watched_sites`: List the URLs this account monitors, with the frequency, last score and last check time. Needs an API key.
- `watch_site`: Add a URL to the account's scheduled monitoring (freq: daily or weekly). The owner gets an email when a check finds a new P1 problem or the score drops by 10 or more. Needs an API key; adding the same URL again only changes the frequency.