Is the Solknife Toolkit MCP server down?

mcp-registry/xyz.solknife/toolkit · v1.0.0

healthy
Last checked 2026-10-26 05:07 UTC · handshake 531ms

As of 2026-10-26 05:07 UTC, the Solknife Toolkit MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.5% of Glimind's liveness checks. It had 22 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
99.5%
checks observed
4,012
outages (90d)
22
tools
55

Non-custodial Solana toolkit: rug-checks, swaps, portfolios, token minting, multisig, Arweave.

Install Solknife Toolkit MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http solknife-toolkit-mcp-server https://solknife.xyz/api/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "solknife-toolkit-mcp-server": {
      "type": "http",
      "url": "https://solknife.xyz/api/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (70/100)

C (70/100): 0 error(s), 4 warning(s) across 55 tool(s); ~12,743 tokens of tool definitions.
Scores higher than 4% of 15,730 MCP servers Glimind has audited.
Its tool list costs an agent ~12,743 tokens per session — more than 85% of servers.
69 → 70 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions67
Safety hints0
Token cost75
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (5)

55 of 55 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: solknife_arweave_upload_relay, solknife_burn_nft_build, solknife_burn_nft_execute, solknife_burn_nft_list, solknife_change_authority_build and 50 more

55 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

25 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: solknife_burn_nft_execute, solknife_change_authority_execute, solknife_create_account_build, solknife_create_account_execute, solknife_create_mint_build and 20 more

25 parameter(s) across 18 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: solknife_arweave_upload_relay, solknife_burn_nft_build, solknife_create_account_build, solknife_create_mint_build, solknife_ct_apply_pending_build and 13 more

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 37 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 18 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fxyz.solknife%2Ftoolkit/fixes

solknife_arweave_upload_relay 1 change
{
  "name": "solknife_arweave_upload_relay",
  "description": "Upload a base64-encoded file to Arweave via SolKnife's funded Irys account. JSON-only — for agents without a wallet-adapter integration. Allowed contentType: image/png, image/jpeg, image/gif, image/webp, application/json. Max 2 MiB. Returns { arweaveTxId, arweaveUrl }.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "fileBase64",
      "contentType"
    ],
    "properties": {
      "fileBase64": {
        "type": "string",
        "minLength": 1,
        "description": "Base64 of the file bytes. Max 2 MiB decoded."
      },
      "contentType": {
        "enum": [
          "image/png",
          "image/jpeg",
          "image/gif",
          "image/webp",
          "application/json"
        ],
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
solknife_burn_nft_execute 1 change
{
  "name": "solknife_burn_nft_execute",
  "description": "Submit burn-nft tx(s) (signed). Structural re-verifier pins the burn ixs + fee per tx. Returns per-tx outcomes.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "signedTransactions",
      "lastValidBlockHeight"
    ],
    "properties": {
      "signedTransactions": {
        "type": "array",
        "items": {
          "type": "string",
          "maxLength": 2500,
          "minLength": 1,
          "description": "The base64 VersionedTransaction returned by the matching /build call, signed with your key. Do not submit it yourself; this endpoint submits it."
        },
        "maxItems": 20,
        "minItems": 1,
        "description": "The signed base64 transactions from /build, in the order /build returned them."
      },
      "lastValidBlockHeight": {
        "type": "integer",
        "maximum": 10000000000,
        "description": "The `lastValidBlockHeight` returned alongside the unsigned tx by /build. Past this block height the tx can no longer land.",
        "exclusiveMinimum": 0
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
solknife_burn_nft_list 1 change
{
  "name": "solknife_burn_nft_list",
  "description": "List a wallet's NFT assets (DAS).",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "owner"
    ],
    "properties": {
      "owner": {
        "type": "string",
        "pattern": "^[1-9A-HJ-NP-Za-km-z]{32,44}$",
        "description": "A Solana address in base58, 32-44 chars."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/xyz.solknife/toolkit"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/xyz.solknife/toolkit"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.solknife%2Ftoolkit.svg)](https://glimind.com/server/mcp-registry%2Fxyz.solknife%2Ftoolkit?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fxyz.solknife%2Ftoolkit?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.solknife%2Ftoolkit.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.solknife%2Ftoolkit.svg
   :target: https://glimind.com/server/mcp-registry%2Fxyz.solknife%2Ftoolkit?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:24849c9245bf1932…, first seen 2026-10-17, included at leaf 16265 of 70,821. Version history · verify what your client received.

Tools (55)

Compare: most reliable storage servers · most reliable data servers · most reliable finance servers · most reliable transactions servers · most reliable security servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Solknife Toolkit MCP server down right now?

As of 2026-10-26 05:07 UTC, the Solknife Toolkit MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.5% of Glimind's liveness checks. It had 22 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Solknife Toolkit MCP server provide?

Solknife Toolkit MCP server advertises 55 tools, including solknife_arweave_upload_relay, solknife_burn_nft_build, solknife_burn_nft_execute, solknife_burn_nft_list, solknife_change_authority_build.

How do I install Solknife Toolkit MCP server?

Point your MCP client at this streamable-http endpoint: https://solknife.xyz/api/mcp

Is the Solknife Toolkit MCP server safe to connect to an AI agent?

Glimind scanned all 55 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Solknife Toolkit MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve