MCP servers observed by Lowdown
dev.nichedb/nichedb MCP server: daily status and tool changes
No successful response on the latest check (2026-11-17) (Lowdown checks this server every 3 days). Checked from one network location. 1 of 3 checks in the last 30 days had this result. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; 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:dev.nichedb/nichedb
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:dev.nichedb/nichedb?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: the server did not respond.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 2
- Required authentication: 0
- No response: 1
- 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?
Fewer than two days with a complete tools/list observation from the same remote, so nothing was compared.
What tools does it list?
48 tools on 2026-11-14:
add_sourceairplane_lookupbusiness_standingcheck_domainclaim_profilecreate_feedcreate_invitecreate_webhookdelete_webhookfeed_itemsfind_profile_by_linkedinfollow_feedget_itemget_profileget_tldlist_adapterslist_collectionslist_enricherslist_feedslist_inviteslist_sourceslist_webhooksmatch_itemspopulationrecent_itemsredeem_codereputation_lookuprotate_webhook_secretrun_sourcesatellite_lookupsearch_itemssearch_profilessearch_tldsship_lookupstatssubmit_feedtest_webhooktld_changestraffic_listtrain_lookuptransit_citytransit_stationupcomingupdate_profileupdate_webhookvuln_lookupwebhook_deliverieswhere_to_buy_book
MCP Registry declaration
- Registry name:
dev.nichedb/nichedb - Declared version: 0.1.0
- Status: active
- Declared hosts:
nichedb.dev
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:dev.nichedb/nichedb", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:dev.nichedb/nichedb?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:dev.nichedb/nichedb -- npx -y @profullstack/nichedb
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).