MCP servers observed by Lowdown
work.autonet/agent-health 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); 53 tools listed. On 2026-11-12 a tool description with a URL appeared (new domain: your-target.example). MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; tool definitions last changed on 2026-11-18 after 6 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:work.autonet/agent-health
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:work.autonet/agent-health?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 2 of 3 compared days.
- 2026-11-18: descriptions changed
- 2026-11-12: descriptions changed; a tool description with a URL appeared (your-target.example)
What tools does it list?
53 tools on 2026-11-18:
agent_domain_challengeagent_endpoint_assessmentagent_health_checksagent_health_feedagent_health_heartbeatagent_health_instructionsagent_health_statusagent_presence_historyagent_signed_evidenceagent_webhook_secretassert_healthyattach_agent_endpointcancel_readiness_jobconfigure_agent_reengagementcreate_callback_inboxcreate_diagnostic_watchcreate_funding_checkoutcreate_utility_accountdelete_agent_healthdelete_callback_inboxdelete_diagnostic_watchdelete_liveness_subscriptiondiagnose_httpdiagnose_mcpevidence_signing_keysexport_incident_evidenceget_agent_statusinternet_utils_cataloginternet_utils_instructionslist_callback_inboxesnetwork_identityprobe_me_nowpublish_mcp_reportread_agent_reengagementread_callback_eventsread_diagnostic_watchesread_liveness_eventsread_readiness_jobsregister_agent_healthrequest_monthly_creditsrun_autonet_sandboxrun_credit_diagnosticrun_signed_diagnosticsend_heartbeatset_utility_identitysubscribe_livenesstest_agent_webhookupdate_agent_healthupdate_diagnostic_watchutility_accountverify_agent_domainwait_for_callbackwait_until_ready
MCP Registry declaration
- Registry name:
work.autonet/agent-health - Declared version: 1.1.1
- Status: active
- Declared hosts:
autonet.work
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:work.autonet/agent-health", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:work.autonet/agent-health?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).