AI & Machine Learning
silverbackmarketing.com
Generates and manages AI readiness assessment files and instructions for websites.
ENDPOINT 1
https://ai.silverbackmarketing.com/api/mcp
MCP server metadata
- Name
- ai-readiness
- Version
- 1.0.0
Known tools 6
generate_ai_readiness_filesStart generating the 18 AI Readiness Kit files for a website.
Inferred read-onlylist_output_filesList all 18 AI readiness files in generation order with filenames and purposes
Inferred read-onlyget_skill_instructionsReturn the full AI Readiness skill workflow (research, classification, file generation)
Inferred read-onlyget_site_classification_guideReturn the site-type classification table used before generating files
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.ai-readiness]
url = "https://ai.silverbackmarketing.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"ai-readiness": {
"type": "http",
"url": "https://ai.silverbackmarketing.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: ai-readiness
Remote MCP URL: https://ai.silverbackmarketing.com/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"ai-readiness": {
"url": "https://ai.silverbackmarketing.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"ai-readiness": {
"type": "http",
"url": "https://ai.silverbackmarketing.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "ai-readiness",
"transport": "streamable-http",
"url": "https://ai.silverbackmarketing.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.