Aws Safe MCP Server
aws-safe-mcp
PyPI
v0.3.0
Published by harryhazza77 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Read-only, opinionated MCP server for safely investigating AWS resources.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 0
Tools 82
Each tool and what it can reach — statically extracted from the published source.
analyze_api_gateway_authorizer_failuresno sensitive capabilityanalyze_cross_account_lambda_invocationno sensitive capabilityanalyze_queue_dlq_replay_readinessno sensitive capabilityanalyze_resource_policy_condition_mismatchesno sensitive capabilityaudit_async_lambda_failure_pathno sensitive capabilityaudit_eventbridge_target_retry_dlq_safetyno sensitive capabilityaudit_multi_region_drift_failover_readinessno sensitive capabilityaudit_sns_fanout_delivery_readinessno sensitive capabilityaudit_step_function_retry_catch_safetyno sensitive capabilitybuild_log_signal_correlation_timelineno sensitive capability
Show 72 more tools ↓
check_cloudwatch_logs_writeabilityno sensitive capabilitycheck_dynamodb_stream_lambda_readinessno sensitive capabilitycheck_kms_dependent_pathno sensitive capabilitycheck_lambda_permission_pathno sensitive capabilitycheck_lambda_to_sqs_sendabilityno sensitive capabilitycheck_s3_notification_destination_readinessno sensitive capabilitycheck_sqs_to_lambda_deliveryno sensitive capabilitydiagnose_region_partition_mismatchesno sensitive capabilityexplain_api_gateway_dependenciesno sensitive capabilityexplain_event_driven_flowno sensitive capabilityexplain_eventbridge_rule_dependenciesno sensitive capabilityexplain_iam_simulation_denialno sensitive capabilityexplain_lambda_dependenciesno sensitive capabilityexplain_lambda_network_accessno sensitive capabilityexplain_sns_topic_dependenciesno sensitive capabilityexplain_sqs_queue_dependenciesno sensitive capabilityexplain_step_function_dependenciesno sensitive capabilityexport_application_dependency_graphno sensitive capabilityfind_cloudwatch_alarm_coverage_gapsno sensitive capabilityfind_kms_key_lifecycle_blast_radiusno sensitive capabilitygenerate_application_health_narrativeno sensitive capabilityget_api_gateway_authorizer_summaryno sensitive capabilityget_api_gateway_summaryno sensitive capabilityget_aws_auth_statusno sensitive capabilityget_aws_identityno sensitive capabilityget_cloudwatch_alarm_summaryno sensitive capabilityget_cross_service_incident_briefno sensitive capabilityget_dynamodb_table_summaryno sensitive capabilityget_ecs_service_summaryno sensitive capabilityget_eventbridge_time_sourcesno sensitive capabilityget_iam_role_summaryno sensitive capabilityget_kms_key_summaryno sensitive capabilityget_lambda_alias_version_summaryno sensitive capabilityget_lambda_event_source_mapping_diagnosticsno sensitive capabilityget_lambda_recent_errorsno sensitive capabilityget_lambda_summaryno sensitive capabilityget_risk_scored_dependency_health_summaryno sensitive capabilityget_s3_bucket_summaryno sensitive capabilityget_sns_topic_summaryno sensitive capabilityget_sqs_queue_summaryno sensitive capabilityget_step_function_execution_summaryno sensitive capabilityinvestigate_api_gateway_routeno sensitive capabilityinvestigate_eventbridge_rule_deliveryno sensitive capabilityinvestigate_lambda_cold_start_initno sensitive capabilityinvestigate_lambda_concurrency_bottlenecksno sensitive capabilityinvestigate_lambda_deployment_driftno sensitive capabilityinvestigate_lambda_failureno sensitive capabilityinvestigate_lambda_timeout_root_causeno sensitive capabilityinvestigate_sqs_backlog_stallno sensitive capabilityinvestigate_step_function_failureno sensitive capabilitylist_api_gatewaysno sensitive capabilitylist_cloudwatch_alarmsno sensitive capabilitylist_cloudwatch_log_groupsno sensitive capabilitylist_dynamodb_tablesno sensitive capabilitylist_ecs_clustersno sensitive capabilitylist_ecs_servicesno sensitive capabilitylist_eventbridge_rulesno sensitive capabilitylist_kms_keysno sensitive capabilitylist_lambda_functionsno sensitive capabilitylist_s3_bucketsno sensitive capabilitylist_s3_objectsno sensitive capabilitylist_sns_topicsno sensitive capabilitylist_sqs_queuesno sensitive capabilitylist_step_functionsno sensitive capabilityplan_end_to_end_transaction_traceno sensitive capabilityprove_lambda_invocation_pathno sensitive capabilityquery_cloudwatch_logs_insightsno sensitive capabilityrun_first_blocked_edge_incidentno sensitive capabilitysearch_aws_resourcesno sensitive capabilitysearch_aws_resources_by_tagno sensitive capabilitysearch_cloudwatch_logsno sensitive capabilitysimulate_lambda_security_group_pathno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (82 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.3.0 latest |
A 99/100 | 0 | 1.13.0 | 2026-08-25 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan aws-safe-mcp --online --registry pypiMore in Cloud & DevOps
Operator control CLI for AdGuard Home with an MCP adapter
interacting with Aliyun (Alibaba Cloud) services through This MCP server provides tools.
MCP server for the Aspro.Cloud REST API
MCP server for Atlassian Confluence and Jira Cloud APIs
AuroraCloud-first MCP server that exposes AuroraDocs workspace data to Claude Desktop and other AI agents
The official AWS Knowledge Base retrieval server using Bedrock Agent Runtime.