refinex-mcp
Related Servers
Alternatives to refinex-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables querying AWS Cost Explorer spend data and Amazon Bedrock model invocation logs through CloudWatch in natural language. Supports EC2, Bedrock, and cross-account cost analysis via local or remote MCP transports.-
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code sessions to query fleet status, focus terminals, and manage sessions programmatically via MCP tools.2MIT
- AlicenseAqualityAmaintenanceEnables search, analytics, and visualization of Claude Code sessions with MCP tools for session management, recovery, and insights.1053 PyPI1MIT
- AlicenseNot gradedqualityDmaintenanceEnables natural language control of AWS resources (EC2, Security Groups, S3, Bedrock, etc.) directly from Claude Desktop or Claude Code.54 PyPIMIT
- AlicenseAqualityCmaintenanceExposes analytics from Claude Code transcripts as MCP tools, enabling cost, audit, safety, and efficiency queries through natural language.4MIT
- FlicenseNot gradedqualityAmaintenanceEnables users to analyze AWS cloud costs, audit for wasted resources like stopped EC2 instances and unattached EBS volumes, and check budget status through natural language in any MCP-compatible AI assistant. Supports multi-profile and multi-region querying while keeping AWS credentials local to the user's machine.-
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: health check, best signal, per-instance signal, aggregate summary, suppression log, and paginated list. No overlap in functionality.
All tool names follow a consistent verb_noun pattern using snake_case, e.g., get_health, get_live_signal, list_signals. No deviations.
With 6 tools, the set is well-scoped for a focused API providing spot arbitrage signals. Each tool earns its place without being excessive or insufficient.
The tool surface covers health, best signal, per-instance queries, summaries, suppression logs, and listing. A minor gap is the lack of a direct 'get_signal_by_id' endpoint, but list_signals with filtering can serve that purpose.