MCP servers observed by Lowdown
com.tomorrowcentral/aws-cloud-cost-sentinel MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-10 to 2026-11-19) (Lowdown checks this server every 3 days); 86 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-19 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:com.tomorrowcentral/aws-cloud-cost-sentinel
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:com.tomorrowcentral/aws-cloud-cost-sentinel?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-19: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 3 of 3 compared days.
- 2026-11-19: input or output schemas changed, descriptions changed, tool names changed; tool count 27 → 86
- 2026-11-16: input or output schemas changed, descriptions changed, tool names changed; tool count 42 → 27
- 2026-11-13: input or output schemas changed, descriptions changed, tool names changed; tool count 53 → 42
What tools does it list?
86 tools on 2026-11-19:
compare_architecturescompare_regionscreate_cloud_connectiondescribe_workloadestimate_costget_connectionget_jobget_job_resultlist_connectionslist_cost_building_blockslist_cost_findingslist_priced_serviceslist_tools_availableprice_lookupreport_feedbackrun_cost_scansearch_create_projectsearch_import_statussearch_list_projectssearch_projectsearch_public_cataloguesearch_start_importsearch_usagesubmit_ratingverify_connectionwebops_acceptwebops_ai_competitorswebops_ai_questionswebops_ai_visibilitywebops_analytics_healthwebops_breakdownwebops_classify_pagewebops_comparewebops_competitorswebops_dailywebops_draft_fixwebops_draftswebops_findingwebops_findingswebops_funnel_stepswebops_goalwebops_google_connectionwebops_indexingwebops_investigation_feedbackwebops_investigationswebops_journeyswebops_limitswebops_linkswebops_list_websiteswebops_look_up_searchwebops_mark_appliedwebops_measurementwebops_page_dossierwebops_pageswebops_pagespeedwebops_patternswebops_playbookwebops_position_changewebops_rankingswebops_rankings_comparewebops_record_investigationwebops_refresh_nowwebops_rejectwebops_run_ai_checkwebops_search_resultswebops_searcheswebops_set_ai_questionswebops_set_competitorswebops_set_conversionswebops_set_funnel_stepswebops_set_goalwebops_set_prioritieswebops_set_ranking_pinswebops_shopwebops_site_profilewebops_site_searchwebops_site_settingswebops_structured_datawebops_thresholdswebops_timelinewebops_visitorswebops_visitswebops_website_statuswebops_whoamiwhere_can_this_runwhoami
MCP Registry declaration
- Registry name:
com.tomorrowcentral/aws-cloud-cost-sentinel - Declared version: 1.2.0
- Status: active
- Declared hosts:
api.tomorrowcentral.com
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:com.tomorrowcentral/aws-cloud-cost-sentinel", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:com.tomorrowcentral/aws-cloud-cost-sentinel?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).