MCP servers observed by Lowdown
io.alion/alion MCP server: daily status and tool changes
On the latest check (2026-11-16) its remotes differed: 1 answered tools/list, 2 required authentication. (Lowdown checks this server every 3 days) On 2026-11-13 a tool description with a URL appeared. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-13 after 3 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.alion/alion
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.alion/alion?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-16: the server its remotes gave different results.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 0
- Required authentication: 0
- No response: 0
- Remotes differed: 3
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-13: input or output schemas changed, descriptions changed, tool names changed; tool count 33 → 34; a tool description with a URL appeared
What tools does it list?
34 tools on 2026-11-16:
agent_statuscheck_counterpartycheck_employercheck_fitcheck_watchcompany_inbox_settingscontact_companydelete_watchdraft_profile_changeget_agentget_companyget_conversationget_indexget_investorget_jobget_personlist_conversationslist_watchesmarket_statsmatch_peoplemy_matchesregister_agentreport_problemresolve_companysearch_companiessearch_investorssearch_jobssearch_peoplesend_messageset_webhooksimilar_companiessimilar_peopleverify_companywatch_search
MCP Registry declaration
- Registry name:
io.alion/alion - Declared version: 1.5.1
- Status: active
- Declared hosts:
alion.io
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.alion/alion", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.alion/alion?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.alion/alion -- npx -y @alion-io/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).