Skip to content

VS Code mcp crypto_dapp_check

How to: VS Code mcp crypto_dapp_check

client:VS Code transport:streamable-http tool:crypto_dapp_check

Add mcp to VS Code

  1. 01

    Open .vscode/mcp.json and merge this in. Keep any servers already there.

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://dechonet.com/mcp"
    }
  }
}
  1. 02

    Save the file and restart VS Code.

  2. 03

    Ask for something crypto_dapp_check does. VS Code lists the server's tools on connect and calls crypto_dapp_check itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that mcp's identifier in your config matches the one above exactly.

Requires agent mode. MCP: Open User Configuration puts the same block in every workspace. VS Code docs

Set these first

mcp will not start until these are set, so crypto_dapp_check never becomes available.

  • DECHONET_URL
  • DECHONET_LOCALE
  • DECHONET_API_KEY
  • DECHONET_SESSION_COOKIE

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.