MCP servers observed by Lowdown
io.github.tripsyapp/tripsy MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-10 to 2026-11-16) (Lowdown checks this server every 3 days); 54 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; no tool definition change in 2 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:io.github.tripsyapp/tripsy
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.tripsyapp/tripsy?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: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 2 compared days.
What tools does it list?
54 tools on 2026-11-16:
tripsy_activities_createtripsy_activities_deletetripsy_activities_listtripsy_activities_showtripsy_activities_updatetripsy_categories_createtripsy_categories_deletetripsy_categories_listtripsy_categories_showtripsy_categories_updatetripsy_collaborators_deletetripsy_collaborators_invitetripsy_collaborators_listtripsy_collaborators_updatetripsy_documents_attachtripsy_documents_deletetripsy_documents_gettripsy_documents_listtripsy_documents_showtripsy_documents_updatetripsy_documents_uploadtripsy_documents_upload_preparetripsy_emails_listtripsy_emails_showtripsy_expenses_createtripsy_expenses_deletetripsy_expenses_listtripsy_expenses_showtripsy_expenses_updatetripsy_guests_favorites_listtripsy_hostings_createtripsy_hostings_deletetripsy_hostings_listtripsy_hostings_showtripsy_hostings_updatetripsy_inbox_deletetripsy_inbox_listtripsy_inbox_showtripsy_inbox_updatetripsy_itinerary_guidancetripsy_me_showtripsy_me_updatetripsy_statustripsy_transportations_createtripsy_transportations_deletetripsy_transportations_listtripsy_transportations_showtripsy_transportations_updatetripsy_trips_createtripsy_trips_deletetripsy_trips_following_listtripsy_trips_listtripsy_trips_showtripsy_trips_update
MCP Registry declaration
- Registry name:
io.github.tripsyapp/tripsy - Declared version: 2.2.1
- Status: active
- Declared hosts:
mcp.tripsy.app
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.tripsyapp/tripsy", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.tripsyapp/tripsy?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).