MCP servers observed by Lowdown
io.github.trypostit/trypost MCP server: daily status and tool changes
Required authentication (HTTP 401/403) on all 4 checks recorded in the last 30 days (2026-11-09 to 2026-11-18) (Lowdown checks this server every 3 days). Lowdown checks without credentials, so no tools were listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; 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.trypostit/trypost
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.trypostit/trypost?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server required authentication (HTTP 401/403).
- Observed days in the last 30: 4
- Answered initialize and tools/list: 0
- Required authentication: 4
- No response: 0
- Remotes differed: 0
Does it require authentication?
It returned HTTP 401/403 on 4 of 4 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
- Registry name:
io.github.trypostit/trypost - Declared version: 2.0.0
- Status: active
- Declared hosts:
app.trypost.it
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.trypostit/trypost", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.trypostit/trypost?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).