MCP servers observed by Lowdown

app.connectmyshop/etsy MCP server: daily status and tool changes

No Lowdown daily check since 2026-11-03 (15 days ago), so no current connectivity is stated. MCP Registry entry recorded as removed; observed daily by Lowdown Scanner since 2026-10-29; 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:app.connectmyshop/etsy

Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.connectmyshop/etsy?menu=install-check · other questions: menu

Does it respond?

Latest daily check: 2026-11-03: the server required authentication (HTTP 401/403). That check is 15 days old, so it is not a current status.

Does it require authentication?

It returned HTTP 401/403 on 6 of 6 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?

No tool list is recorded (for example, the server required authentication or did not answer tools/list).

MCP Registry declaration

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:app.connectmyshop/etsy", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.connectmyshop/etsy?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).