aws-health-mcp-server

v2.0.0 safe
4.0
Medium Risk

Production-ready MCP server for monitoring AWS Health events and service status

🤖 AI Analysis

Final verdict: SAFE

The package poses minimal risks with no network, shell execution, or obfuscation concerns. The moderate credential and metadata risks are manageable given the common practices used for handling AWS credentials.

  • Moderate credential risk due to fetching AWS credentials from environment variables.
  • Metadata risk due to limited maintainer information.
Per-check LLM notes
  • Network: No network calls detected, which is normal if the package does not require external communication.
  • Shell: No shell execution patterns detected, indicating the package does not execute commands on the host system.
  • Obfuscation: No obfuscation patterns detected.
  • Credentials: The code is fetching environment variables for AWS credentials and region which is common practice but could pose a risk if not handled securely.
  • Metadata: The maintainer has a new or inactive account and lacks detailed author information, raising some concerns.

📦 Package Quality Overall: Medium (6.6/10)

✦ High Test Suite 9.0

Test suite present — 1 test file(s) found

  • Test runner config found: pyproject.toml
  • 1 test file(s) detected (e.g. test_server.py)
◈ Medium Documentation 7.0

Some documentation present

  • Documentation URL: "Documentation" -> https://github.com/aws-samples/sample-health-mcp-server/blob
  • Detailed PyPI description (4106 chars)
○ Low Contributing Guide 4.0

No contributing guide or governance files found

  • Development Status classifier >= Beta
◈ Medium Type Annotations 5.0

Partial type annotation coverage

  • 30 type-annotated function signatures detected in source
✦ High Multiple Contributors 8.0

Active multi-contributor project

  • 4 unique contributor(s) across 24 commits in aws-samples/sample-health-mcp-server
  • Small but multi-author team (3–4 contributors)

🔬 Heuristic Checks

✓ Outbound Network Calls

No suspicious network call patterns found

✓ Code Obfuscation

No obfuscation patterns detected

✓ Shell / Subprocess Execution

No shell execution patterns detected

⚠ Credential Harvesting score 5.0

Found 2 credential access pattern(s)

  • uration AWS_REGION: str = os.getenv("AWS_REGION", "us-east-1") AWS_PROFILE: Optional[str] = os.ge
  • AWS_PROFILE: Optional[str] = os.getenv("AWS_PROFILE") # Logging Configuration LOG_LEVEL: str =
✓ Typosquatting

No typosquatting candidates detected

✓ Registered Email Domain

Email domain looks legitimate: amazon.com>

✓ Suspicious Page Links

All external links appear legitimate

✓ Git Repository History

Repository aws-samples/sample-health-mcp-server appears legitimate

⚠ Maintainer History score 4.0

2 maintainer concern(s) found

  • Author name is missing or very short
  • Author "" appears to have only 1 package on PyPI (new or inactive account)
✓ Known CVE Vulnerabilities

No known vulnerabilities found in OSV database.

💡 AI App Starter Prompt

Use this prompt to build a project with aws-health-mcp-server 
Create a real-time AWS Health Monitoring Dashboard using the 'aws-health-mcp-server' package. This dashboard will allow users to monitor the health and status of various AWS services in real-time, providing alerts for any incidents or issues affecting these services.

### Project Scope:
- **Real-Time Updates**: Ensure the dashboard updates in real-time as soon as there are changes in AWS service statuses.
- **Service Filtering**: Allow users to filter services based on their regions, types, or specific services they're interested in.
- **Alert System**: Implement a notification system that sends alerts via email/SMS when critical incidents occur.
- **Historical Data**: Provide a feature to view historical data about past incidents for analysis purposes.
- **User Interface**: Design a clean, user-friendly interface that allows easy navigation and quick access to information.

### Core Features:
1. **Integration with AWS Health Events**: Utilize the 'aws-health-mcp-server' package to integrate your application with AWS Health events, ensuring it fetches real-time data.
2. **Dynamic Service Status Display**: Display the current status of each AWS service on the dashboard dynamically.
3. **Incident Notification**: Set up notifications for critical incidents. Users should be able to customize which services they want to receive alerts for.
4. **Incident History**: Store and display historical data about incidents, including start time, end time, and description.
5. **Customizable Alerts**: Users should have the ability to set up custom alerts based on specific criteria, such as service type, region, or severity level.

### Implementation Steps:
1. **Setup Environment**: Install necessary packages including 'aws-health-mcp-server', Flask for web framework, and any other required libraries.
2. **Fetch Data**: Use 'aws-health-mcp-server' to fetch real-time data from AWS Health APIs.
3. **Design UI/UX**: Create a simple yet effective user interface using HTML/CSS/JavaScript for the frontend.
4. **Backend Development**: Develop the backend using Flask to handle data fetching, filtering, and storing.
5. **Notification System**: Integrate a third-party service like Twilio for SMS alerts and SMTP for email alerts.
6. **Testing & Deployment**: Test all functionalities thoroughly and deploy the application to a cloud platform like AWS or Heroku.
7. **Documentation**: Provide clear documentation on how to use the dashboard and how to customize alert settings.

💬 Discussion Feed

Leave a comment

No discussion yet. Be the first to share your thoughts!