MCP servers observed by Lowdown
help.awning/awning MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-09 to 2026-11-18) (Lowdown checks this server every 3 days); 36 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; no tool definition change in 3 compared days; 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:help.awning/awning
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:help.awning/awning?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: 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?
No change in tool schemas, descriptions or names across 3 compared days.
What tools does it list?
36 tools on 2026-11-18:
cancel_bookingcreate_bookingcreate_holdget_availabilityget_bookingget_businesslogoutmy_bookingsmy_profileop_analyticsop_applicationsop_businessesop_connect_telegramop_decide_applicationop_decide_leadop_leadsop_suspend_businessowner_add_offeringowner_block_timeowner_cancel_bookingowner_decide_bookingowner_get_scheduleowner_import_sourceowner_list_bookingsowner_pauseowner_photosowner_previewowner_remove_photosowner_set_scheduleowner_setupowner_statusowner_submitowner_update_businessowner_update_offeringowner_upsert_sessionssearch_businesses
MCP Registry declaration
- Registry name:
help.awning/awning - Declared version: 0.1.0
- Status: active
- Declared hosts:
api.awning.help
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:help.awning/awning", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:help.awning/awning?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).