# Wake site readiness (remote · agent-observatory-desk-production.up.railway.app)

How an AI agent sees a public website: robots, llms.txt, sitemap, agent card, scored fixes. Host in.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `agent-observatory-desk-production.up.railway.app`: 70/100 (this document), [markdown](https://verifymcp.io/servers/sadri-dridi-wake-site-readiness/api-wake-v1-public-mcp.md), [page](https://verifymcp.io/servers/sadri-dridi-wake-site-readiness/api-wake-v1-public-mcp)

## Channel facts

- Endpoint: `https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Wake site readiness MCP server?

Wake site readiness is a hosted endpoint at https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/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.

### Claude

```bash
claude mcp add --transport http sadri-dridi-wake-site-readiness 'https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "sadri-dridi-wake-site-readiness": {
      "url": "https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "sadri-dridi-wake-site-readiness": {
      "type": "http",
      "url": "https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.sadri-dridi-wake-site-readiness]
url = "https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sadri-dridi-wake-site-readiness": {
      "type": "remote",
      "url": "https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add sadri-dridi-wake-site-readiness --url 'https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  sadri-dridi-wake-site-readiness:
    url: "https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "sadri-dridi-wake-site-readiness": {
      "Transport": "http",
      "Url": "https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add sadri-dridi-wake-site-readiness -t streamable-http -u 'https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp'
```

### Other

```json
{
  "mcpServers": {
    "sadri-dridi-wake-site-readiness": {
      "type": "http",
      "url": "https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 70, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.10 → unverified
- [security regression] HSTS header: fail → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-03 (score 70, +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.

### 2026-11-01 (score 69, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-31 (score 68)

First indexed and scored.

## MCP tools (2)

### `wake_check_site` (~91 tokens)

Check a site's agent readiness

Probe a public hostname the way an AI agent sees it (homepage, robots.txt, llms.txt, sitemap, agent card) and return scores out of 100 with concrete recommendations and publish-ready llms.txt / robots files. Input is a hostname only; the probe keeps structural signals, never page bodies. No account needed.

Input parameters:

- `host` (string): Public hostname, e.g. docs.example.com

### `wake_about` (~36 tokens)

What Wake is

One paragraph on Wake (agent experience observability + agent engine optimisation for a website), with links to docs, API, MCP and signup.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/sadri-dridi-wake-site-readiness/api-wake-v1-public-mcp#diagnostics

## Score history

- 2026-11-05: 70
- 2026-11-04: 70
- 2026-11-03: 70
- 2026-11-02: 69
- 2026-11-01: 69
- 2026-10-31: 68

## Common questions

### What is the Wake site readiness MCP server?

Wake site readiness is an MCP server listed in the public MCP registry as io.github.sadri-dridi/wake-site-readiness. How an AI agent sees a public website: robots, llms.txt, sitemap, agent card, scored fixes. Host in. This page covers its hosted endpoint (https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp).

### Is the Wake site readiness MCP server safe to use?

Wake site readiness scores 70 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 Wake site readiness MCP server expose?

Wake site readiness exposes 2 tools: wake_check_site, wake_about. Their descriptions and schemas cost roughly 127 tokens of context every time the server is loaded.

### Does the Wake site readiness MCP server require authentication?

Its publisher declares no required credentials for Wake site readiness. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Wake site readiness MCP server still maintained?

Wake site readiness is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 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 Wake site readiness MCP server?

VerifyMCP ran 3 checks on Wake site readiness, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about Wake site readiness: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.

## Links

- Remote endpoint: https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp
- Website: https://agent-observatory-desk-production.up.railway.app/wake/docs/index.md
- Changelog RSS feed: https://verifymcp.io/servers/sadri-dridi-wake-site-readiness/api-wake-v1-public-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/sadri-dridi-wake-site-readiness/api-wake-v1-public-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/sadri-dridi-wake-site-readiness/api-wake-v1-public-mcp.json
- HTML version of this page: https://verifymcp.io/servers/sadri-dridi-wake-site-readiness/api-wake-v1-public-mcp