MCP servers observed by Lowdown
xyz.solknife/toolkit 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); 57 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-13 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:xyz.solknife/toolkit
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:xyz.solknife/toolkit?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-13: input or output schemas changed, descriptions changed, tool names changed; tool count 55 → 57
What tools does it list?
57 tools on 2026-11-19:
solknife_arweave_upload_relaysolknife_burn_nft_buildsolknife_burn_nft_executesolknife_burn_nft_listsolknife_change_authority_buildsolknife_change_authority_executesolknife_change_authority_readsolknife_check_scansolknife_create_account_buildsolknife_create_account_executesolknife_create_mint_buildsolknife_create_mint_executesolknife_ct_apply_pending_buildsolknife_ct_configure_buildsolknife_ct_deposit_buildsolknife_ct_empty_and_close_buildsolknife_ct_orphans_buildsolknife_ct_orphans_listsolknife_ct_statesolknife_ct_submitsolknife_ct_transfer_buildsolknife_ct_withdraw_buildsolknife_mint_supply_buildsolknife_mint_supply_executesolknife_mint_supply_readsolknife_multisig_approve_buildsolknife_multisig_approve_executesolknife_multisig_config_buildsolknife_multisig_config_executesolknife_multisig_create_buildsolknife_multisig_create_executesolknife_multisig_execute_buildsolknife_multisig_execute_executesolknife_multisig_listsolknife_multisig_propose_buildsolknife_multisig_propose_executesolknife_multisig_statesolknife_owned_mints_listsolknife_pool_checksolknife_pool_comparesolknife_portfolio_compose_buildsolknife_portfolio_compose_executesolknife_portfolio_compose_plansolknife_portfolio_holdingssolknife_positions_listsolknife_reclaim_rent_buildsolknife_reclaim_rent_executesolknife_reclaim_rent_listsolknife_revoke_authority_buildsolknife_revoke_authority_executesolknife_revoke_authority_readsolknife_swap_executesolknife_swap_ordersolknife_token_metasolknife_token_metadata_buildsolknife_token_metadata_executesolknife_token_metadata_read
MCP Registry declaration
- Registry name:
xyz.solknife/toolkit - Declared version: 1.1.0
- Status: active
- Declared hosts:
solknife.xyz
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:xyz.solknife/toolkit", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:xyz.solknife/toolkit?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).