mcp tested by Argusic Runner

What the test found

58 AWS MCP server projects install and build with uv; ~15,000 unit tests pass across 50+ servers; the aws-documentation-mcp-server launches, responds to MCP initialize over stdio, and makes real API calls to AWS Documentation Search and docs.aws.amazon.com

58 MCP server projects installed and built with uv. ~15,000 unit tests passed across 50+ servers. The aws-documentation-mcp-server made real API calls to AWS Documentation Search API (returned 3 search results with query_id) and read real content from docs.aws.amazon.com (694 chars of S3 documentation). Multiple servers launched and responded to MCP initialize requests over stdio including aws-documentation, aws-pricing, aws-serverless, iam, aws-api, cloudtrail, cloudwatch, elasticache, memcached, finch, amazon-mq, amazon-neptune, aws-location, aws-transform, amazon-kendra-index, stepfunctions, aurora-dsql, amazon-sns-sqs, aws-healthomics. The sagemaker-unified-studio-spark-* directories contain only README docs for remote managed MCP servers, not local code. The mcp-lambda-handler is a Lambda handler module (81 tests passed) rather than a CLI-runnable server.

Argusic installed mcp in 8 minutes and launched it; verification reached Verified running for real. 5 of 7 recorded errors were worked through (see the timeline below).

Runsall runs of mcp

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.