MCP servers observed by Lowdown
net.letsbot/mcp MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-10 to 2026-11-16) (Lowdown checks this server every 3 days); 95 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; no tool definition change in 2 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:net.letsbot/mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:net.letsbot/mcp?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-16: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 2 compared days.
What tools does it list?
95 tools on 2026-11-16:
add_noteai_analyze_contactai_dashboard_summaryai_improve_messageai_sentiment_analysisai_suggest_replyai_summarize_conversationai_translate_messagearchive_contactassign_labelassign_moderatorblock_contactcancel_campaigncancel_scheduled_activitycreate_campaigncreate_contactcreate_interactive_conversationcreate_labelcreate_quick_replycreate_simple_conversationcreate_whatsapp_templatedelete_bot_conversationdelete_contactdelete_labeldelete_quick_replydiagnose_messagingdraft_bot_flowduplicate_bot_conversationforward_messageget_abandoned_cartsget_account_overviewget_ad_lead_settingsget_ai_assistant_settingsget_assignment_rulesget_bot_conversationsget_bot_settingsget_bot_statusget_campaign_statusget_campaignsget_contactget_contactsget_conversations_awaiting_replyget_group_messagesget_groupsget_label_contactsget_labelsget_message_statusget_messagesget_moderatorsget_my_chatsget_notification_templateget_order_statusget_owner_briefingget_quick_repliesget_reportget_store_setup_checklistlist_scheduled_activitylist_store_automationslist_whatsapp_templatesmark_as_readpin_contactreassign_conversationsreply_to_messageresend_campaignresume_campaignsave_cart_remindersearch_messagessearch_productssend_audiosend_buttonssend_carouselsend_contact_cardsend_filesend_group_filesend_group_messagesend_imagesend_listsend_locationsend_reactionsend_templatesend_text_messagesend_videoset_bot_conversation_activeset_store_automation_activetoggle_botupdate_ad_lead_settingsupdate_ai_assistant_settingsupdate_assignment_rulesupdate_bot_conversationupdate_bot_settingsupdate_contactupdate_labelupdate_notification_templateupdate_quick_replyupload_file
MCP Registry declaration
- Registry name:
net.letsbot/mcp - Declared version: 1.0.0
- Status: active
- Declared hosts:
letsbot.net
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:net.letsbot/mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:net.letsbot/mcp?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).