TestSprite MCP

70/100

Capped at 70: no passing tool call yet; the tests add up to 93. Why scores are capped

Last tested 2026-11-18 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 93; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology

Test points before the cap (93/100)

  • Install20/20
  • Handshake30/30
  • Maintenance25/25
  • Docs15/15
  • License3/10

Tested npm @testsprite/testsprite-mcp 0.0.48 (BUSL-1.1; no source repo linked in package metadata). Installed pinned with scripts off (npm --ignore-scripts) and launched: initialize and tools/list over stdio succeeded with no credentials and listed 8 tools (no tool annotations). Real calls: No real function call could be made without credentials or a backing app (the server's only tools are setup/status checks). Core tools not tested: 70 cap.
Tool-call test (2026-11-18 UTC, direct MCP stdio client, no LLM): fail. No real function call could be made without credentials or a backing app (the server's only tools are setup/status checks). Evidence: local test run, Nov 18, 2026 UTC.

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

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

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

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

  • testsprite_bootstrap — unclassified
  • testsprite_check_account_info — read
  • testsprite_generate_backend_test_plan — unclassified
  • testsprite_generate_code_and_execute — unclassified
  • testsprite_generate_code_summary — unclassified
  • testsprite_generate_frontend_test_plan — unclassified
  • testsprite_generate_standardized_prd — unclassified
  • testsprite_open_test_result_dashboard — unclassified

handshake and tools listed without a recorded key or OAuth

Score 70/100 · Tools 8 · Token cost approx. 1,265 tokens · Compare · Last tested 2026-11-18 UTC · Version tested 0.0.48 · Package @testsprite/testsprite-mcp

Summary: TestSprite MCP completed an MCP handshake without credentials and exposed 8 tools.

Evidence summary

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

Test results

TestResultPointsEvidence
installpass20npm install @testsprite/testsprite-mcp --ignore-scripts (Node v24.22.1, Linux) succeeded in 2s.
handshakepass30MCP initialize + tools/list over stdio succeeded with no credentials; 8 tools listed in 6.0s.
maintenancepass25Latest release published 18 days before test.
docspass15README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (README shipped in npm package).
licensepartial3License not machine-detected as OSI (BUSL-1.1).

Local-model readiness

Token cost (estimate): approx. 1265 tokens, cl100k estimate for 8 tools · about 15% 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-18 UTC

  • Install from the registry
  • We connected with no credentials and asked for its tool list: it listed 8 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-18 UTC test run; changes appear after the next test.

Snapshot hash (fingerprint of the tool list)

69899c70a7aa: 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": "@testsprite/testsprite-mcp",
  "version": "0.0.48",
  "registry": "npm",
  "status": "working",
  "tested": "2026-11-18",
  "tools_count": 8,
  "deprecated": false,
  "archived": null,
  "tests": {
    "install": [
      "pass",
      20,
      "`npm install @testsprite/testsprite-mcp --ignore-scripts` (Node v24.22.1, Linux) succeeded in 2s."
    ],
    "handshake": [
      "pass",
      30,
      "MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 8 tools listed in 6.0s."
    ],
    "maintenance": [
      "pass",
      25,
      "Latest release published 18 days before test."
    ],
    "docs": [
      "pass",
      15,
      "README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (README shipped in npm package)."
    ],
    "license": [
      "partial",
      3,
      "License not machine-detected as OSI (BUSL-1.1)."
    ]
  },
  "testedAt": "2026-11-18T04:17:03.741Z"
}

Install

npx -y @testsprite/testsprite-mcp

Pin the version we tested

npx -y --ignore-scripts @testsprite/testsprite-mcp@0.0.48

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

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

Tools listed

testsprite_bootstrap, testsprite_generate_code_summary, testsprite_generate_standardized_prd, testsprite_generate_frontend_test_plan, testsprite_generate_backend_test_plan, testsprite_generate_code_and_execute, testsprite_open_test_result_dashboard, testsprite_check_account_info

Quick config

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

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

Setup

  1. Install. Run npm install @testsprite/testsprite-mcp --ignore-scripts (Node v24.22.1). This is the exact command we ran on 2026-11-18 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 (8 in our test).
{
  "mcpServers": {
    "testsprite-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@testsprite/testsprite-mcp"
      ]
    }
  }
}

Test history

Follow this server (RSS) · Monthly changelog

FAQ

Is TestSprite MCP deprecated?

No. TestSprite MCP was not deprecated or archived when we last tested it on 2026-11-18 UTC.

What replaces TestSprite MCP?

Nothing; TestSprite MCP is not deprecated as of 2026-11-18 UTC.

Does TestSprite MCP need an API key?

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

Embed the badge

TestedMCP: 70/100, tested 2026-11-18 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