MCP server for retrieving and analyzing AWS content from aws.amazon.com
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"aws-content-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# AWS Content MCP Server A comprehensive Model Context Protocol (MCP) server for retrieving and analyzing content from aws.amazon.com. This server provides dynamic, real-time access to AWS blogs, product information, solutions, pricing, and other content without hallucination. ## Features - **Dynamic Content Retrieval**: Real-time fetching from aws.amazon.com - **Comprehensive Search**: Search across blogs, products, solutions, and pricing - **Full Content Analysis**: Extract complete content with detailed analysis - **Duplicate Detection**: Identify similar content and prevent duplication - **Content Comparison**: Compare different AWS content pieces - **Service Overview**: Get comprehensive AWS service listings - **No Hallucination**: All information is fetched directly from AWS sources ## Installation ### Using uvx (Recommended) ```bash uvx aws-content-mcp ``` ### Using pip ```bash pip install aws-content-mcp ``` ### From Source ```bash git clone https://github.com/yourusername/aws-content-mcp.git cd aws-content-mcp pip install -e . ``` ## Usage ### As MCP Server Add to your MCP client configuration: ```json { "mcpServers": { "aws-content": { "command": "uvx", "args": ["aws-content-mcp"] } } } ``` ### Available Tools #### 1. search_aws_content Search for AWS content across different categories. **Parameters:** - `query` (required): Search query - `content_type` (optional): "all", "blogs", "products", "solutions", or "pricing" **Example:** ```json { "query": "serverless computing", "content_type": "blogs" } ``` #### 2. get_full_aws_content Get complete content from a specific AWS URL with detailed analysis. **Parameters:** - `url` (required): AWS URL to fetch content from **Example:** ```json { "url": "https://aws.amazon.com/blogs/compute/serverless-computing-with-lambda/" } ``` #### 3. analyze_aws_blog_ideas Analyze blog ideas for duplication and provide content recommendations. **Parameters:** - `topic` (requ…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.