MCP servers observed by Lowdown
ai.stonewake/stonewake 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); 48 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-16 after 3 days without change; 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:ai.stonewake/stonewake
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.stonewake/stonewake?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?
Tool definitions changed on 2 of 2 compared days.
- 2026-11-16: input or output schemas changed, descriptions changed, tool names changed; tool count 43 → 48
- 2026-11-13: input or output schemas changed, descriptions changed, tool names changed; tool count 41 → 43
What tools does it list?
48 tools on 2026-11-16:
alert_channelsalert_deliveriesalert_eventsaudit_log_exportcompany_eventscompany_financialscompany_financingcompany_networkcompany_newscompany_overviewcompany_profilecompany_public_fundingcompany_recordscompany_regional_contextcompany_sector_contextcompany_socialcountry_profiledeal_binding_queuedeal_bookentity_risk_profileexposure_review_historyfetchlicensed_factsownership_chainportfolio_board_tableportfolio_bookportfolio_delivery_changesportfolio_fund_import_previewportfolio_fundsportfolio_groupsportfolio_import_previewportfolio_maturitiesportfolio_overviewportfolio_reviews_dueportfolio_securitiesportfolio_securities_import_previewportfolio_security_checkreport_downloadssanctions_person_candidatesscoring_rubricscreening_lookupsearchsearch_companiessearch_stonewake_docssocial_sentimenttender_export_previewtender_matchestender_profiles
MCP Registry declaration
- Registry name:
ai.stonewake/stonewake - Declared version: 1.0.0
- Status: active
- Declared hosts:
mcp.stonewake.ai
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:ai.stonewake/stonewake", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.stonewake/stonewake?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).