AI Readiness Kit
REMOTE · AI.SILVERBACKMARKETING.COM · SCANNED AUG 3
Generate 18 AI readiness files (llms.txt, ai.txt, RAG indexes, schema) for any website.
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 →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- 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 Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 280 tokens (~35/item across 8 items; 6 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · ai.silverbackmarketing.com
claude mcp add --transport http silverbackmarketing-ai-readiness https://ai.silverbackmarketing.com/api/mcp
[mcp_servers.silverbackmarketing-ai-readiness] url = "https://ai.silverbackmarketing.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"silverbackmarketing-ai-readiness": {
"type": "remote",
"url": "https://ai.silverbackmarketing.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add silverbackmarketing-ai-readiness --url https://ai.silverbackmarketing.com/api/mcp --transport streamable-http
mcp_servers:
silverbackmarketing-ai-readiness:
url: "https://ai.silverbackmarketing.com/api/mcp" {
"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.
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.
- 3 Aug 26 +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.
- 1 Aug 26 +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.
- 31 Jul 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
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 66
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 3 Aug 2026 · Probed https://ai.silverbackmarketing.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ai.silverbackmarketing.com | CN=YR2,O=Let's Encrypt,C=US | 18 Jun 2026 | 16 Sept 2026 | RSA 2048 | SHA256-RSA | 54a1e6fbe11cb2d749736ae4451f25beece |
| SANs: ai.silverbackmarketing.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of ai.silverbackmarketing.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| silverbackmarketing.com. | 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 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://img.shields.io https://www.googletagmanager.com https://www.google-analytics.com; font-src 'self'; connect-src 'self' https://www.googletagmanager.com https://www.google-analytics.com https://region1.google-analytics.com; frame-src https://www.googletagmanager.com; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ai.silverbackmarketing.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://ai.silverbackmarketing.com/api/mcp | HTTPS enforced | 308 | https://ai.silverbackmarketing.com/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.
generate_ai_readiness_files ~66
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).
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Website URL or domain, e.g. shopify.com or https://example.com |
No output schema declared.
No examples provided.
generate_rag_jsonl ~53
Convert rag-index.json content (JSON array) to rag-index.jsonl (one JSON object per line)
| Name | Type | Req | Description |
|---|---|---|---|
| rag_index_json | string | yes | String contents of rag-index.json (must be a JSON array) |
No output schema declared.
No examples provided.
get_file_spec ~56
Get the detailed specification for one AI readiness output file (e.g. llms.txt, ai-entities.json)
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | yes | Output filename, e.g. llms.txt or .well-known/ai-plugin.json |
No output schema declared.
No examples provided.
get_site_classification_guide ~23
Return the site-type classification table used before generating files
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_skill_instructions ~26
Return the full AI Readiness skill workflow (research, classification, file generation)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_output_files ~24
List all 18 AI readiness files in generation order with filenames and purposes
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.