MCP servers observed by Lowdown
io.github.valetdotdev/valet 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); 64 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 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.github.valetdotdev/valet
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.valetdotdev/valet?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 3 of 3 compared days.
- 2026-11-18: input or output schemas changed, descriptions changed, tool names changed; tool count 63 → 64
- 2026-11-15: input or output schemas changed, descriptions changed, tool names changed
- 2026-11-12: input or output schemas changed, descriptions changed
What tools does it list?
64 tools on 2026-11-18:
attach_channelattach_connectorattach_resourceattach_skillcreate_channelcreate_connectorcreate_pushcreate_servicedestroy_channeldestroy_checkerdestroy_connectordestroy_memorydestroy_policydestroy_resourcedestroy_servicedestroy_sessiondetach_channeldetach_connectordetach_resourcedetach_skillfind_skillget_buildget_connectorget_evaluationget_logsget_requestget_serviceget_sessionget_skillget_sourcelist_catalog_channelslist_catalog_connectorslist_catalog_resourceslist_channelslist_connector_toolslist_connectorslist_env_varslist_memorieslist_orgslist_policieslist_releaseslist_resourceslist_serviceslist_sessionslist_skillspublish_agentpublish_apppublish_sitepublish_skillreauthorize_channelreauthorize_connectorrename_servicerestart_servicerollback_servicescale_serviceset_checkerset_env_varsset_memoryset_policyset_resource_planset_service_accessshare_serviceunset_env_varsunshare_service
MCP Registry declaration
- Registry name:
io.github.valetdotdev/valet - Declared version: 1.0.0
- Status: active
- Declared hosts:
api.valet.dev
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.valetdotdev/valet", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.valetdotdev/valet?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).