Tomorrow Central: Cloud Cost Sentinel

Name: Tomorrow Central: Cloud Cost Sentinel
Author: com.tomorrowcentral

MCP serverMCP

AWS pricing and cost estimates with no signup, plus read-only idle-resource scans of your account.

by com.tomorrowcentralhomepage ↗v1.2.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"tomorrow-central-cloud-cost-sentinel","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability107/107 checks ok

when	check	result	http	latency	detail
7 h ago	mcp initialize	ok	200	163 ms	server tomorrowcentral 1.30.0 · protocol 2025-06-18 · 20 tools
14 h ago	mcp initialize	ok	200	172 ms	server tomorrowcentral 1.30.0 · protocol 2025-06-18 · 20 tools
21 h ago	mcp initialize	ok	200	157 ms	server tomorrowcentral 1.30.0 · protocol 2025-06-18 · 20 tools
28 h ago	mcp initialize	ok	200	229 ms	server tomorrowcentral 1.30.0 · protocol 2025-06-18 · 20 tools
34 h ago	mcp initialize	ok	200	236 ms	server tomorrowcentral 1.30.0 · protocol 2025-06-18 · 20 tools
2 d ago	mcp initialize	ok	200	159 ms	server tomorrowcentral 1.30.0 · protocol 2025-06-18 · 20 tools
2 d ago	mcp initialize	ok	200	173 ms	server tomorrowcentral 1.30.0 · protocol 2025-06-18 · 20 tools
2 d ago	mcp initialize	ok	200	167 ms	server tomorrowcentral 1.30.0 · protocol 2025-06-18 · 20 tools
3 d ago	mcp initialize	ok	200	204 ms	server tomorrowcentral 1.30.0 · protocol 2025-06-18 · 20 tools
3 d ago	mcp initialize	ok	200	161 ms	server tomorrowcentral 1.30.0 · protocol 2025-06-18 · 20 tools

Tools observed via MCP handshake

get_job — Check the status of a Tomorrow Central job. Poll this after starting any scan. Status goes QUEUED → RUNNING → COMPLETED (or FAILED). A typical scan tak
get_job_result — Get the full raw result of a COMPLETED job. Returns an error telling you to keep polling if the job hasn't finished. The result contains data read from
list_connections — List the cloud accounts this API key can scan, with their status. Only a connection with status CONNECTED or VERIFIED can be scanned. PENDING means the
get_connection — Get one cloud account connection: status, region, and last error if any.
create_cloud_connection — Start linking a cloud account so it can be scanned. `provider` is "aws", the only provider supported today; `account_id` is the 12-digit AWS account number.
verify_connection — Check whether the read-only role for a connection exists yet and mark it VERIFIED if so. Expect this to fail while the human's CloudFormation stack is
list_tools_available — List the Tomorrow Central tools this platform offers (id, name, what it does).
whoami — Identify the account this API key belongs to, and its plan. Useful for confirming the key works before doing real work.
report_feedback — Report, in plain English, something Tomorrow Central could not do, did badly, or documented unclearly. Use this when you hit a wall: a capability that does
submit_rating — Rate a result you were given, from 1 (useless) to 5 (exactly what was needed). `rating_token` comes back alongside the result itself, from get_job_result o
run_cost_scan — Start a cloud cost / FinOps scan of a linked account and return a job_id. Use this when the user wants to find idle, unused or underutilized cloud resources
list_cost_findings — Get the findings from a completed cost scan, newest analysis first. Call this once `get_job` reports COMPLETED. Returns, per finding: `kind` (e.g. nat_
price_lookup — Look up current AWS on-demand list prices. No account, key or signup needed. Use this to answer "what does X cost", to sanity-check a bill, or to price a
compare_regions — Compare the same thing's price across AWS regions, cheapest first. Use this when a user asks where something is cheapest, or what moving a workload to
list_priced_services — The services and regions `price_lookup` can answer for, plus how current the book is. Call this first if a lookup returned nothing and you want to check the
estimate_cost — Price a list of cloud components at real list prices. No account or signup. Use this when the user can name the pieces: "two m5.large servers, a Postgres
compare_architectures — Price every shape that delivers a capability, and say where they cross over. This is the tool for "should we move to serverless", "is Lambda cheaper than
describe_workload — Price a workload described the way a person would describe it. Use this when the user does not know cloud: "a website with a database for my shop", "an
where_can_this_run — Apply requirements FIRST, then price only the regions that survive. Use this for "the data has to stay in India", "we cannot use US-owned jurisdictions
list_cost_building_blocks — Everything the estimator can be asked about, by name. Call this BEFORE the other estimator tools. They select from a closed set and reject anything els

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrycom.tomorrowcentral/aws-cloud-cost-sentinel

first seen 1 mo ago · fetched 12 h agoopen ↗

Field history (10 recent events)

28 d ago · declared · summary → "AWS pricing and cost estimates with no signup, plus read-only idle-resource scans of your account."
28 d ago · declared · description → "AWS pricing and cost estimates with no signup, plus read-only idle-resource scans of your account."
28 d ago · declared · version → "1.2.0"
1 mo ago · declared · version → "1.1.0"
1 mo ago · declared · version → "1.0.0"
1 mo ago · declared · summary → "Read-only AWS cost analysis: find idle and underutilized resources, with evidence."
1 mo ago · declared · protocols → ["mcp"]
1 mo ago · declared · description → "Read-only AWS cost analysis: find idle and underutilized resources, with evidence."
1 mo ago · declared · publisherName → "com.tomorrowcentral"
1 mo ago · declared · homepageUrl → "https://tomorrowcentral.com/agents"

Tomorrow Central: Cloud Cost Sentinel

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from