MCP servers observed by Lowdown
ai.tensorfeed/mcp-server MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-09 to 2026-11-18) (Lowdown checks this server every 3 days); 30 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; tool definitions last changed on 2026-11-18 after 9 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:ai.tensorfeed/mcp-server
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.tensorfeed/mcp-server?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: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 1 of 3 compared days.
- 2026-11-18: input or output schemas changed, descriptions changed, tool names changed
What tools does it list?
30 tools on 2026-11-18:
ask_tensorfeedbenchmark_seriesbenchmark_trust_verdictcheck_agent_reputationcheck_ai_supply_chain_riskcompare_modelsfailover_verdictget_agent_opportunitiesget_cve_recordget_epss_scoreget_kev_catalogget_modelsget_news_articlesget_osv_advisory_for_packageget_research_papersget_status_summarypricing_seriesprovider_deepdiveprovider_reliability_verdictregister_free_watchroute_verdictsearch_sec_edgarssvc_verdictstack_safety_verdictstatus_leaderboardstatus_uptimesubmit_wantlist_itemwhats_newx402_publisher_verdictx402_settlement_verdict
MCP Registry declaration
- Registry name:
ai.tensorfeed/mcp-server - Declared version: 2.1.0
- Status: active
- Declared hosts:
mcp.tensorfeed.ai
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:ai.tensorfeed/mcp-server", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.tensorfeed/mcp-server?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:ai.tensorfeed/mcp-server -- npx -y @tensorfeed/mcp-server
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).