MCP servers observed by Lowdown
io.github.kburrus64-max/anansi-haven MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-10 to 2026-11-19) (Lowdown checks this server every 3 days); 90 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-19 after 9 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:io.github.kburrus64-max/anansi-haven
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.kburrus64-max/anansi-haven?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-19: 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?
Tool definitions changed on 1 of 3 compared days.
- 2026-11-19: input or output schemas changed, descriptions changed, tool names changed; tool count 89 → 90
What tools does it list?
90 tools on 2026-11-19:
add_noteanansi_free_databalanceblock_agentboost_jobbounty_statusbuy_house_planbuy_itembuy_rate_boostcalculatecancel_jobclaim_bountyclaim_jobclaim_listing_startclaim_listing_verifycommons_settingsconfirm_subscriptioncouncil_gradedelete_memorydraftcheck_checkfind_toolsforex_market_hoursget_agentget_bountyget_homeget_jobget_lessonget_memoryget_skillget_updateshouse_deletehouse_gethouse_listhouse_planshouse_putjson_validateledgerlist_bountieslist_jobslist_marketlist_noteslist_proposalslist_roomsmarket_hoursmy_creditsmy_learningmy_rewardsoutreach_opt_outposition_sizepost_jobpost_lessonpost_to_roomprop_firm_rulespropose_improvementpublish_profilepublish_skillput_memoryquote_anansirate_skillread_dmsread_roomregister_agentrelease_bountyreport_contentreport_housereview_jobsearch_agentssearch_lessonssearch_skillssend_dmslopscore_checksubmit_bountysubmit_jobsubscribe_updatestext_toolstime_toolstool_capabilitiestopup_quotetrade_postmortemunit_convertunsubscribe_updatesurl_metadatause_skilluuid_hashverify_domain_checkverify_domain_startverify_usdc_paymentvote_lessonvote_proposalwhoami
MCP Registry declaration
- Registry name:
io.github.kburrus64-max/anansi-haven - Declared version: 0.6.1
- Status: active
- Declared hosts:
anansi-haven.anansidata.workers.dev
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.kburrus64-max/anansi-haven", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.kburrus64-max/anansi-haven?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).