# AI Readiness Kit (remote · ai.silverbackmarketing.com)

Generate 18 AI readiness files (llms.txt, ai.txt, RAG indexes, schema) for any website.

- Trust score: 71/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `ai.silverbackmarketing.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/silverbackmarketing-ai-readiness/api-mcp.md), [page](https://verifymcp.io/servers/silverbackmarketing-ai-readiness/api-mcp)

## Channel facts

- Endpoint: `https://ai.silverbackmarketing.com/api/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-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 280 tokens (~35/item across 8 items; 6 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http silverbackmarketing-ai-readiness https://ai.silverbackmarketing.com/api/mcp
```

### Codex

```toml
[mcp_servers.silverbackmarketing-ai-readiness]
url = "https://ai.silverbackmarketing.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "silverbackmarketing-ai-readiness": {
      "type": "remote",
      "url": "https://ai.silverbackmarketing.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add silverbackmarketing-ai-readiness --url https://ai.silverbackmarketing.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  silverbackmarketing-ai-readiness:
    url: "https://ai.silverbackmarketing.com/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "silverbackmarketing-ai-readiness": {
      "type": "http",
      "url": "https://ai.silverbackmarketing.com/api/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-08-03 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 69, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 69, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 66)

First indexed and scored.

## MCP tools (6)

### `generate_ai_readiness_files` (~66 tokens)

Start generating the 18 AI Readiness Kit files for a website. Returns the full workflow for the connected agent to execute (research, classify, write files).

Input parameters:

- `url` (string, required): Website URL or domain, e.g. shopify.com or https://example.com

### `list_output_files` (~24 tokens)

List all 18 AI readiness files in generation order with filenames and purposes

### `get_file_spec` (~56 tokens)

Get the detailed specification for one AI readiness output file (e.g. llms.txt, ai-entities.json)

Input parameters:

- `filename` (string, required): Output filename, e.g. llms.txt or .well-known/ai-plugin.json

### `get_skill_instructions` (~26 tokens)

Return the full AI Readiness skill workflow (research, classification, file generation)

### `get_site_classification_guide` (~23 tokens)

Return the site-type classification table used before generating files

### `generate_rag_jsonl` (~53 tokens)

Convert rag-index.json content (JSON array) to rag-index.jsonl (one JSON object per line)

Input parameters:

- `rag_index_json` (string, required): String contents of rag-index.json (must be a JSON array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/silverbackmarketing-ai-readiness/api-mcp#diagnostics

## Score history

- 2026-08-03: 71
- 2026-08-02: 70
- 2026-08-01: 70
- 2026-07-31: 69
- 2026-07-30: 69
- 2026-07-29: 68
- 2026-07-28: 68
- 2026-07-27: 67
- 2026-07-26: 66

## Links

- Remote endpoint: https://ai.silverbackmarketing.com/api/mcp
- Repository: https://github.com/silverbackmarketing/ai-readiness
- Website: https://ai.silverbackmarketing.com/
- Changelog RSS feed: https://verifymcp.io/servers/silverbackmarketing-ai-readiness/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/silverbackmarketing-ai-readiness/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/silverbackmarketing-ai-readiness/api-mcp