MCP servers observed by Lowdown
dev.testsy/testsy MCP server: daily status and tool changes
Answered initialize and tools/list on the last 2 consecutive checks (2026-11-13 to 2026-11-16) (Lowdown checks this server every 3 days); 48 tools listed. 2 of 3 checks in the last 30 days had this result. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; no tool definition change in 1 compared days; 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:dev.testsy/testsy
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:dev.testsy/testsy?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-16: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 2
- Required authentication: 1
- No response: 0
- Remotes differed: 0
Does it require authentication?
It returned HTTP 401/403 on 1 of 3 observed days. Lowdown checks without credentials, so the tools behind authentication were not listed.
Did its tools change recently?
No change in tool schemas, descriptions or names across 1 compared days.
What tools does it list?
48 tools on 2026-11-16:
add_credentialadd_endpointadd_test_filecomplete_build_uploadcreate_build_uploadcreate_projectcreate_schedulecreate_share_linkcreate_testcreate_watch_linkdelete_builddelete_credentialdelete_endpointdelete_projectdelete_scheduledelete_share_linkdelete_testdelete_test_fileduplicate_testfind_buildget_buildget_networkget_projectget_runget_testget_usageget_workspaceimport_buildlist_buildslist_credentialslist_deviceslist_endpointslist_projectslist_runslist_scheduleslist_share_linkslist_test_fileslist_testsplan_testrevoke_watch_linkrun_projectrun_testset_browse_fromstop_runupdate_projectupdate_scheduleupdate_testwait_run
MCP Registry declaration
- Registry name:
dev.testsy/testsy - Declared version: 1.1.1
- Status: active
- Declared hosts:
app.testsy.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:dev.testsy/testsy", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:dev.testsy/testsy?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).