MCP servers observed by Lowdown
ai.taasky/taasky MCP server: daily status and tool changes
On the latest daily check (2026-11-18) its remotes differed: 1 answered tools/list, 1 required authentication. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-27; tool definitions last changed on 2026-11-11 after 12 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.taasky/taasky
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.taasky/taasky?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server its remotes gave different results.
- Observed days in the last 30: 23
- Answered initialize and tools/list: 0
- Required authentication: 0
- No response: 0
- Remotes differed: 23
Does it require authentication?
It did not return HTTP 401/403 on any of the 23 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 2 of 22 compared days.
- 2026-11-11: input or output schemas changed
- 2026-10-30: input or output schemas changed, descriptions changed
What tools does it list?
7 tools on 2026-11-18:
negotiation_cancelnegotiation_joinnegotiation_listnegotiation_opennegotiation_proposenegotiation_readnegotiation_respond
MCP Registry declaration
- Registry name:
ai.taasky/taasky - Declared version: 0.2.2
- Status: active
- Declared hosts:
mcp.taasky.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.taasky/taasky", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.taasky/taasky?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).