Tomorrow Central: Cloud Cost Sentinel
Read-only AWS cost analysis: find idle and underutilized resources, with evidence.
https://api.tomorrowcentral.com/mcpCurrent observation
This endpoint answered at its latest recorded check.
What this server reports about itself
Self-reported at initialize. Not verified by Licium.
- Server name
- tomorrowcentral
- Version
- 1.29.0
- Capability keys
- experimental, prompts, resources, tools
- Tool names
- get_job, get_job_result, list_connections, get_connection, create_cloud_connection, verify_connection, list_tools_available, whoami, report_feedback, submit_rating, run_cost_scan, list_cost_findings
Tomorrow Central runs cloud-infrastructure tools an agent can drive end to end. Today: Cloud Cost Sentinel, a cloud cost / FinOps scanner. AWS is the only provider supported so far. Use these tools when the user wants to analyze AWS spend or cloud cost, find idle, unused or underutilized resources, estimate savings, or run an infrastructure or FinOps review. On AWS it covers EC2 instances, EBS volumes and snapshots, RDS instances, Elastic IPs, NAT Gateways, load balancers, VPC endpoints, VPN and Transit Gateway attachments, Secrets Manager secrets, CloudFront distributions and WAF web ACLs. READ-ONLY with respect to your cloud: the scanner reads resource metadata and monitoring metrics and reports. Nothing here can create, modify, stop or delete a cloud resource. Typical flow: whoami -> list_connections -> run_cost_scan(connection_id) -> poll get_job about every 10s until COMPLETED (1-3 min) -> list_cost_findings(job_id). With no connection, run_cost_scan returns sample data. Linkin
Reported Aug 17, 2026, 04:59 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- respondsMCP initialize · 8s limit · HTTP 200 · 796ms