MCP servers observed by Lowdown
io.github.SirPaul-code/eviduct MCP server: daily status and tool changes
No Lowdown check since 2026-11-14 (5 days ago), so no current connectivity is stated. MCP Registry entry recorded as removed; 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:io.github.SirPaul-code/eviduct
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.SirPaul-code/eviduct?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-14: the server required authentication (HTTP 401/403). That check is 5 days old, so it is not a current status.
- Observed days in the last 30: 2
- Answered initialize and tools/list: 1
- Required authentication: 1
- No response: 0
- Remotes differed: 0
Does it require authentication?
It returned HTTP 401/403 on 1 of 2 observed days. Lowdown checks without credentials, so the tools behind authentication were not listed.
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?
3 tools on 2026-11-11:
get_eviduct_network_statusget_mcp_server_metadatasearch_mcp_servers
MCP Registry declaration
- Registry name:
io.github.SirPaul-code/eviduct - Declared version: 1.1.0
- Status: active
- Declared hosts:
eviduct-mvp.onrender.com - Removed from the Registry: 2026-11-15
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.SirPaul-code/eviduct", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.SirPaul-code/eviduct?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).