MCP servers observed by Lowdown
io.firmops/firmops MCP server: daily status and tool changes
Answered initialize and tools/list on the latest check (2026-11-17) (Lowdown checks this server every 3 days); 88 tools listed. 1 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-11; 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.firmops/firmops
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.firmops/firmops?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 1
- Required authentication: 2
- No response: 0
- Remotes differed: 0
Does it require authentication?
It returned HTTP 401/403 on 2 of 3 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?
88 tools on 2026-11-17:
add_portal_packetcancel_intake_linkcreate_calendar_eventcreate_dropbox_file_requestcreate_dropbox_foldercreate_intake_linkcreate_mattercreate_matter_documentcreate_matter_expensecreate_matter_notecreate_matter_taskcreate_portal_workspacedecline_ticketdelete_calendar_eventdownload_matter_documentdraft_matter_emaildraft_outlook_emaildraft_outlook_replyfind_contactfind_grow_contactfind_matterfind_outlook_free_timeget_billget_callget_contactget_email_threadget_gmail_attachmentget_grow_inbox_leadget_grow_leadget_intake_submissionget_leadget_matterget_matter_timelineget_matter_trust_balanceget_matter_workspaceget_outlook_attachmentget_outlook_threadget_questionnaire_submissionget_taskissue_billlink_lead_to_matterlink_qbo_customerlist_calendar_eventslist_callslist_clio_custom_field_definitionslist_clio_expense_categorieslist_dropbox_folderlist_engagement_letterslist_grow_leadslist_intake_linkslist_invoiceslist_matter_billslist_matter_calendar_eventslist_matter_communicationslist_matter_custom_fieldslist_matter_documentslist_matter_noteslist_matter_taskslist_open_matterslist_outlook_eventslist_outstanding_balanceslist_paymentslist_portal_statuslist_recent_leadslist_staff_automationslist_text_messageslist_ticket_linksmove_dropbox_filepreview_add_portal_packetquote_ticketread_drive_fileread_dropbox_fileread_onedrive_filereply_to_matter_emailresend_intake_linkresend_portal_linksearch_dropboxsearch_my_drivesearch_my_emailsearch_onedrivesearch_outlook_emailsearch_tasksset_matter_practice_areaset_matter_stageset_up_matter_billingupdate_matter_custom_fieldupdate_taskupload_dropbox_file
MCP Registry declaration
- Registry name:
io.firmops/firmops - Declared version: 1.0.0
- Status: active
- Declared hosts:
mcp.firmops.io
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.firmops/firmops", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.firmops/firmops?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).