MCP servers observed by Lowdown
io.github.echopai/echopai-mcp MCP server: daily status and tool changes
Answered initialize and tools/list on the only check recorded in the last 30 days (2026-11-18) (Lowdown checks this server every 3 days); 82 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-18; 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.echopai/echopai-mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.echopai/echopai-mcp?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: 1
- Answered initialize and tools/list: 1
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 1 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?
82 tools on 2026-11-18:
announcements_detailannouncements_feedannouncements_searchannouncements_stockauctionbars_batchcalendar_reportscalendar_upcomingcapabilitieschartconcept_tagsconcepts_alertsconcepts_alerts_historyconcepts_daily_barsconcepts_fundflow_minuteconcepts_listconcepts_minute_barsconcepts_newsconcepts_ofconcepts_showconcepts_snapshotconcepts_viewsdigestdragon_tiger_dailydragon_tiger_seatdragon_tiger_seatsdragon_tiger_stockearnings_recentearnings_showetf_flowsetf_listetf_showevents_timelineevents_upcomingfinancials_pitfinancials_quote_snapshotfinancials_reportsfinancials_seriesfundflowglobal_index_snapshothotindex_snapshotlimit_up_analysislimit_up_historylimit_up_poollimit_up_promotionlimit_up_summarylookupmargin_collateralmargin_collateral_moversmargin_marketmargin_moversmargin_showmarket_calendarmarket_clockmarket_digestmarket_indicesmarket_moversmarket_statusnewsnews_getownership_lockupsownership_showquotereportscansearchsecurity_referencesentiment_breadthsentiment_overviewsentiment_pct_distributionsentiment_premiumsentiment_turnoversocial_hottechnicalstrades_minutetrades_tickstrading_daysusageviewsviews_getwhoami
MCP Registry declaration
- Registry name:
io.github.echopai/echopai-mcp - Declared version: 1.0.1
- Status: active
- Declared hosts:
mcp.huishengpai.com
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.echopai/echopai-mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.echopai/echopai-mcp?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:io.github.echopai/echopai-mcp -- npx -y @echopai/mcp
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).