Amazon Web Services MCP
Get a non-expert from zero to a Slack-delivered, plain-English, waste-flagged AWS bill breakdown
The current version, v0.1.5, was published to the official MCP registry on 2026-10-16. It is distributed through a declared package, filed under AWS by this index, and declares 6 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.
Using Amazon Web Services MCP in Claude, Cursor, Gemini CLI, Cline, or Zed?
MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).
Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less
uv tool install mcpindex-gate && mcpindex-config-wireSemantic screen found no manipulation pattern in the description. Conformance probe not yet run.
mcpindex.integrity.descriptionpassINFOevidence“No hidden instructions”via static_description
- - Semantic screen only - the deterministic conformance probe has not run on this server
- - Confidence is reported but not yet calibrated (v1)
- - Screen reads the tool description, not the live behavior
- - advisory
- - registry description only no input schema
- - screen model 8b
- - Still current: the description we screened is unchanged, re-checked against the registry
- - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not
Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.
Own this server? Test a description on the public screen → It is a separate check from the verdict above, so the two can differ.
That verdict was true at screening time (snapshot 2026-10-19).
Contracts can change after screening, with no version bump. The gate pins Amazon Web Services MCP’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.
See your first HOLD in 2 minutes →
Related: how to trust an MCP server · screen before install · silent contract drift
People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.
[Independent trust record for Amazon Web Services MCP](https://mcpindex.ai/server/io-github-servosity-aws-billing-mcp) - screening verdict, registry provenance, and contract drift monitoring.<a href="https://mcpindex.ai/server/io-github-servosity-aws-billing-mcp">Independent trust record for Amazon Web Services MCP</a> - screening verdict, registry provenance, and contract drift monitoring.A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.
[](https://mcpindex.ai/server/io-github-servosity-aws-billing-mcp)<a href="https://mcpindex.ai/server/io-github-servosity-aws-billing-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-servosity-aws-billing-mcp" alt="mcpindex verdict" height="20" /></a>AWS_ACCESS_KEY_IDAccess key ID for an IAM principal with Cost Explorer read access. Resolved by the AWS SDK's default credential chain.
AWS_BILLING_BASE_URLBase URL for the AWS Billing Intelligence API. Leave the prefilled default unless your account uses a different regional or self-hosted host.
AWS_BILLING_SLACK_CHANNELSlack channel or DM ID that `report --slack` posts to by default (the --slack-channel flag overrides it). Leave blank to pass the destination on every run.
AWS_REGIONRegion for the EC2, CloudWatch and S3 calls. Cost Explorer is always served from us-east-1 regardless of this value.
AWS_SECRET_ACCESS_KEYSecret access key paired with AWS_ACCESS_KEY_ID.
AWS_SESSION_TOKENSession token, required only when the keys above are temporary STS or SSO credentials. Leave blank for long-lived IAM user keys.
Cloud cost, inventory and governance on AWS/Azure/GCP. Read-only by default, optional scoped writes
FinOps agent MCP: allocated AWS, GCP, Azure, Kubernetes, SaaS & AI cost for Claude or any agent
Search instances across GCP, AWS, K8s, Consul & Proxmox