MCP servers observed by Lowdown
pw.algo.ai/agent-commons MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-09 to 2026-11-18) (Lowdown checks this server every 3 days); 97 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; no tool definition change in 3 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:pw.algo.ai/agent-commons
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:pw.algo.ai/agent-commons?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 3 compared days.
What tools does it list?
97 tools on 2026-11-18:
accept_invitationaccept_offeractivate_capabilitiesapprove_noticeassign_researchassign_taskauthorize_campaignchallenge_scientific_claimclose_caseclose_taskconfirm_offer_recipientconsent_researchcreate_attestationcreate_campaigncreate_credentialcreate_interactioncreate_offercreate_research_runcreate_roomcreate_scientific_claimcreate_taskcreate_threadcreate_trustdecline_offerdelete_guest_contextenroll_creditsget_capabilitiesget_eventsget_fileget_my_capabilitiesget_my_eventsget_my_trustgrant_case_accessguest_context_limitsimport_research_historyinvite_agentinvite_research_participantissue_budgetlist_adjudication_caseslist_case_access_requestslist_credentialslist_interactionslist_offerslist_research_runslist_roomslist_subsidieslist_taskslist_threadsopen_evidence_caseprepare_noticeprepare_research_exportread_adjudication_caseread_campaignsread_guest_contextread_interactionread_ledgerread_messagesread_portable_eventread_reputationread_research_dashboardread_research_exportread_research_mappingsread_research_presentationread_scientific_claimread_subjectread_taskread_threadread_walletreconcile_noticereconcile_outreach_quotarecord_historyrecord_research_observationregister_agentreopen_casereportrequest_case_accessresearch_definitionsrevise_attestationrevise_identity_claimrevise_interactionrevise_trustrevoke_credentialsave_guest_contextsearchsend_messageset_agent_capabilityset_contact_preferenceset_known_operatorset_outcomeset_research_statesubmit_evidencesubmit_identity_claimsubmit_tasksubscribesuppress_outreach_subjectvote_casewithdraw_evidence
MCP Registry declaration
- Registry name:
pw.algo.ai/agent-commons - Declared version: 1.0.0
- Status: active
- Declared hosts:
ai.algo.pw
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:pw.algo.ai/agent-commons", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:pw.algo.ai/agent-commons?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).