UniSat OpenAPI MCP

70/100

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

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

No advisories in range for tested 1.0.0 (checked 2026-11-09)

Security review: not tested

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

Test points before the cap (90/100)

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

Tested version: @unisat/openapi-mcp 1.0.0 (npm latest, published 2026-10-30). Its package.json requires Node ^22.23.4, ^24.22.1 or ^26.12.1; our test box runs Node 20.19.2, where it installed and listed its 4 tools anyway. Not tested on Node 22 or later.

Transport (tested 2026-10-30): stdio

Tested version: 1.0.0 · tested 2026-10-30

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

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

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

  • call_api — unclassified
  • get_operation — read
  • get_status — read
  • list_operations — read

handshake and tools listed without a recorded key or OAuth

Score 70/100 · Tools 4 · Token cost approx. 705 tokens · Compare · Last tested 2026-10-30 · Version tested 1.0.0 · Package @unisat/openapi-mcp · Repo unisat-wallet/unisat-ai-kit

Summary: UniSat OpenAPI MCP completed an MCP handshake without credentials and exposed 4 tools.

Evidence summary

Handshake
pass
Tools listed
4
Context cost
approx. 705 tokens, cl100k estimate (4 tools, measured 2026-11-11, version 1.0.0; an estimate) ranking · add up your servers' context cost
API key
No key to connect (handshake passed)
Tested
2026-10-30

Test results

TestResultPointsEvidence
installpass20npm install @unisat/openapi-mcp (Node 20, Linux) succeeded in 2s.
handshakepass30MCP initialize + tools/list over stdio succeeded with no credentials; 4 tools listed in 12.4s.
maintenancepass25Repo pushed 2 days before test; 1 GitHub star.
docspartial5install instructions present. Check of the package's own README (README shipped in npm package).
licensepass10MIT (OSI-approved).

Local-model readiness

Token cost (estimate): approx. 705 tokens, cl100k estimate for 4 tools · about 9% 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-10-30

  • Install from the registry
  • We connected with no credentials and asked for its tool list: it listed 4 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

Checked on 2026-11-09 for version 1.0.0 against OSV, GitHub advisories, GitHub repository advisories. Scope: the package itself; dependencies not scanned.

No published advisories found in OSV and GitHub advisories for @unisat/openapi-mcp 1.0.0 as of 2026-11-09. This is not a security audit.

Monthly roundup: MCP security issues, October 2026.

Tool list changes

Unchanged since the previous snapshot (latest 2026-11-11).

Snapshot hash (fingerprint of the tool list)

dbbac4084d32: 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": "@unisat/openapi-mcp",
  "version": "1.0.0",
  "registry": "npm",
  "status": "working",
  "tested": "2026-10-30",
  "tools_count": 4,
  "deprecated": false,
  "archived": false,
  "tests": {
    "install": [
      "pass",
      20,
      "`npm install @unisat/openapi-mcp` (Node 20, Linux) succeeded in 2s."
    ],
    "handshake": [
      "pass",
      30,
      "MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 4 tools listed in 12.4s."
    ],
    "maintenance": [
      "pass",
      25,
      "Repo pushed 2 days before test; 1 GitHub star."
    ],
    "docs": [
      "partial",
      5,
      "install instructions present. Check of the package's own README (README shipped in npm package)."
    ],
    "license": [
      "pass",
      10,
      "MIT (OSI-approved)."
    ]
  }
}

Install

npx -y @unisat/openapi-mcp

Pin the version we tested

npx -y @unisat/openapi-mcp@1.0.0

tested 2026-10-30. Newer versions may differ and were not tested by us.

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

Tools listed

call_api, get_operation, get_status, list_operations

Tool history: captured Nov 11, 2026. All tool history.

Quick config

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

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

Setup

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

Test history

Follow this server (RSS) · Monthly changelog

FAQ

Is UniSat OpenAPI MCP deprecated?

No. @unisat/openapi-mcp was not deprecated or archived when we last tested it on 2026-10-30.

What replaces UniSat OpenAPI MCP?

Nothing; UniSat OpenAPI MCP is not deprecated as of 2026-10-30.

Does UniSat OpenAPI MCP need an API key?

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

Embed the badge

TestedMCP: 70/100, tested 2026-10-30

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