MCP servers observed by Lowdown
app.saber.mcp/saber MCP server: daily status and tool changes
Answered initialize and tools/list on all 21 daily checks recorded in the last 30 days (2026-10-29 to 2026-11-18); 76 tools listed. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-29; tool definitions last changed on 2026-11-13 after 15 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:app.saber.mcp/saber
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.saber.mcp/saber?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: 21
- Answered initialize and tools/list: 21
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 21 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 1 of 20 compared days.
- 2026-11-13: input or output schemas changed
What tools does it list?
76 tools on 2026-11-18:
companies-enrich_customcompanies-enrich_custom_batchcompanies-enrich_firmographicscompanies-enrich_fundingcompanies-enrich_mnacompanies-enrich_open_jobscompanies-enrich_tech_stackcompanies-generate_summarycompanies-list_summariescompanies-resolve-domaincompany_lists-count_previewcompany_lists-createcompany_lists-deletecompany_lists-exportcompany_lists-getcompany_lists-get_companiescompany_lists-importcompany_lists-listcompany_lists-searchcompany_lists-updateconnectors-listcontact_lists-createcontact_lists-deletecontact_lists-getcontact_lists-get_contactscontact_lists-listcontact_lists-updatecontacts-create_researchcontacts-enrich_customcontacts-enrich_work_emailcontacts-enrich_work_email_batchcontacts-enrich_work_email_batch_getcontacts-get_researchcontacts-get_research_by_external_idcontacts-searchcredits-get_balanceenrichment_runs-getenrichment_runs-listenrichment_templates-createenrichment_templates-deleteenrichment_templates-getenrichment_templates-listenrichment_templates-updateenrichment_types-listmonitors-createmonitors-create_actionmonitors-deletemonitors-delete_actionmonitors-getmonitors-get_actionmonitors-listmonitors-list_actionsmonitors-list_signalsmonitors-pausemonitors-pause_actionmonitors-resumemonitors-resume_actionmonitors-triggermonitors-updatemonitors-update_actionorganisation-getorganisation-updatescoring-assignment-bulk-createscoring-assignment-createscoring-assignment-deletescoring-assignment-listscoring-computescoring-profile-createscoring-profile-deletescoring-profile-getscoring-profile-listscoring-profile-updatescoring-rule-deletescoring-rule-listscoring-rule-upsertscoring-scores-get
MCP Registry declaration
- Registry name:
app.saber.mcp/saber - Declared version: 1.0.0
- Status: active
- Declared hosts:
mcp.saber.app
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:app.saber.mcp/saber", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.saber.mcp/saber?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).