MCP servers observed by Lowdown
io.github.databuddy-analytics/databuddy 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); 46 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-16 after 6 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:io.github.databuddy-analytics/databuddy
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.databuddy-analytics/databuddy?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?
Tool definitions changed on 1 of 2 compared days.
- 2026-11-16: input or output schemas changed, descriptions changed, tool names changed, server version changed; tool count 35 → 46
- 2026-11-13: server version changed
What tools does it list?
46 tools on 2026-11-16:
add_users_to_flagcapabilitiescheck_trackingcreate_annotationcreate_flagcreate_funnelcreate_goalcreate_linkdelete_annotationdelete_flagdelete_funneldelete_goaldelete_linkdismiss_investigationexecute_sql_queryget_accountget_business_contextget_dataget_experiment_resultsget_funnel_analyticsget_funnel_analytics_by_referrerget_goal_analyticsget_investigationget_link_analyticsget_schemalist_accountslist_annotationslist_changeslist_flagslist_funnelslist_goalslist_insightslist_investigationslist_linkslist_profile_traitslist_replay_issueslist_websitesreply_to_investigationsearch_linkssearch_replayssubmit_feedbackupdate_annotationupdate_flagupdate_funnelupdate_goalupdate_link
MCP Registry declaration
- Registry name:
io.github.databuddy-analytics/databuddy - Declared version: 1.0.1
- Status: active
- Declared hosts:
api.databuddy.cc
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:io.github.databuddy-analytics/databuddy", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.databuddy-analytics/databuddy?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).