Foldkit DevTools MCP

70/100

Capped at 70: core tools not tested: no backing service on the test box; the tests add up to 95. Why scores are capped

Last tested 2026-11-13 UTC (Fresh: tested within 30 days) Connects · tools listedNo tool call tested yet No key to connect

Advisories: not yet checked

Security review: not tested

Test points add up to 95; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology

Test points before the cap (95/100)

  • Install20/20
  • Handshake30/30
  • Maintenance25/25
  • Docs10/15
  • License10/10

Tested npm @foldkit/devtools-mcp 0.26.0 (MIT; repo foldkit/foldkit). Installed pinned with scripts off (npm --ignore-scripts) and launched: initialize and tools/list over stdio succeeded with no credentials and listed 15 tools (no tool annotations). Real calls: 0 of 3 real function calls passed. No passing real call: needs a running Foldkit Vite dev server. Core tools not tested: 70 cap.
Tool-call test (2026-11-13 UTC, direct MCP stdio client, no LLM): fail. 0 of 3 real function calls passed. No passing real call: needs a running Foldkit Vite dev server. Evidence: local test run, Nov 13, 2026 UTC.

Transport (tested 2026-11-13 UTC): stdio

Token cost (estimate): approx. 4930 tokens, cl100k estimate (15 tools, measured 2026-11-13 UTC, version 0.26.0). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.

Permissions: 10 read, 0 write (state-changing), 5 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown

Auth: none. Rate limit: unknown. Pricing unit: unknown.

  • foldkit_count_messages_by_tag — unclassified
  • foldkit_diff_models — read
  • foldkit_dispatch_message — unclassified
  • foldkit_dispatch_messages — unclassified
  • foldkit_get_init — read
  • foldkit_get_message — read
  • foldkit_get_message_schema — read
  • foldkit_get_model — read
  • foldkit_get_model_at — read
  • foldkit_get_runtime_state — read
  • foldkit_list_keyframes — read
  • foldkit_list_messages — read
  • foldkit_list_runtimes — read
  • foldkit_replay_to_keyframe — unclassified
  • foldkit_resume — unclassified

handshake and tools listed without a recorded key or OAuth

Score 70/100 · Tools 15 · Token cost approx. 4,930 tokens · Compare · Last tested 2026-11-13 UTC · Version tested 0.26.0 · Package @foldkit/devtools-mcp · Repo foldkit/foldkit

Summary: Foldkit DevTools MCP completed an MCP handshake without credentials and exposed 15 tools.

Evidence summary

Handshake
pass
Tools listed
15
Context cost
approx. 4930 tokens, cl100k estimate (15 tools, measured 2026-11-13 UTC, version 0.26.0; an estimate) ranking · add up your servers' context cost
API key
No key to connect (handshake passed)
Tested
2026-11-13 UTC

Test results

TestResultPointsEvidence
installpass20npm install @foldkit/devtools-mcp (Node 20, Linux) succeeded in 2s.
handshakepass30MCP initialize + tools/list over stdio succeeded with no credentials; 15 tools listed in 0.8s.
maintenancepass25Repo pushed 4 days before test; 1,230 GitHub stars.
docspartial10README over 3,000 chars; install instructions present. Check of the package's own README (README shipped in npm package).
licensepass10MIT (OSI-approved).

Local-model readiness

Token cost (estimate): approx. 4930 tokens, cl100k estimate for 15 tools · about 60% of an 8k context. This is an estimate from our testing (counted with cl100k_base).

Small-model friendly (schema heuristic, not a model result): unknown.

Not tested

Small-model task runs: Not yet tested.

What we tested and what we didn't

Tested on 2026-11-13 UTC

  • Install from the registry
  • We connected with no credentials and asked for its tool list: it listed 15 tools (Method details: MCP initialize then tools/list)
  • Maintenance signals (last push, archived/deprecated status)
  • Docs (README length, install and config example)
  • License (OSI-approved or not)
  • Token cost (estimate)

Not tested

  • Security: not audited (no code review, no permission or data-flow analysis)
  • Real tasks (no functional task runs yet)
  • Behaviour with real credentials or a real account
  • Performance, rate limits or load
  • Correctness of results beyond the listed tasks

Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.

Known security issues

Not yet checked.

Monthly roundup: MCP security issues, October 2026.

Tool list changes

Baseline recorded from the 2026-11-13 UTC test run; changes appear after the next test.

Snapshot hash (fingerprint of the tool list)

7b2999465e7b: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.

Feeds: RSS · JSON.

Raw test record (JSON)
{
  "name": "@foldkit/devtools-mcp",
  "version": "0.26.0",
  "registry": "npm",
  "status": "working",
  "tested": "2026-11-13",
  "tools_count": 15,
  "deprecated": false,
  "archived": false,
  "tests": {
    "install": [
      "pass",
      20,
      "`npm install @foldkit/devtools-mcp` (Node 20, Linux) succeeded in 2s."
    ],
    "handshake": [
      "pass",
      30,
      "MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 15 tools listed in 0.8s."
    ],
    "maintenance": [
      "pass",
      25,
      "Repo pushed 4 days before test; 1,230 GitHub stars."
    ],
    "docs": [
      "partial",
      10,
      "README over 3,000 chars; install instructions present. Check of the package's own README (README shipped in npm package)."
    ],
    "license": [
      "pass",
      10,
      "MIT (OSI-approved)."
    ]
  }
}

Install

npx -y @foldkit/devtools-mcp

Pin the version we tested

npx -y @foldkit/devtools-mcp@0.26.0

tested 2026-11-13 UTC. Newer versions may differ and were not tested by us.

{
  "mcpServers": {
    "foldkit-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@foldkit/devtools-mcp@0.26.0"
      ]
    }
  }
}

Tools listed

foldkit_get_model, foldkit_get_model_at, foldkit_list_messages, foldkit_count_messages_by_tag, foldkit_diff_models, foldkit_get_message, foldkit_get_init, foldkit_get_runtime_state, foldkit_list_keyframes, foldkit_replay_to_keyframe, foldkit_resume, foldkit_get_message_schema, foldkit_dispatch_message, foldkit_dispatch_messages, foldkit_list_runtimes

Quick config

{
  "mcpServers": {
    "foldkit-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@foldkit/devtools-mcp"
      ]
    }
  }
}

Add to config Opens the config generator with this server selected.

Setup

  1. Install. Run npm install @foldkit/devtools-mcp (Node 20). This is the exact command we ran on 2026-11-13 UTC.
  2. Configure. Add the mcpServers entry below to your MCP client config.
  3. Verify. Restart the client and check that tools/list returns tools (15 in our test).
{
  "mcpServers": {
    "foldkit-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@foldkit/devtools-mcp"
      ]
    }
  }
}

Test history

Follow this server (RSS) · Monthly changelog

Related: Best dev MCP servers

FAQ

Is Foldkit DevTools MCP deprecated?

No. @foldkit/devtools-mcp was not deprecated or archived when we last tested it on 2026-11-13 UTC.

What replaces Foldkit DevTools MCP?

Nothing; Foldkit DevTools MCP is not deprecated as of 2026-11-13 UTC.

Does Foldkit DevTools MCP need an API key?

No. It completed an MCP handshake with no credentials and listed 15 tools.

Embed the badge

TestedMCP: 70/100, tested 2026-11-13 UTC

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Claim this listing · Report an issue