UniSat OpenAPI MCP (official)
Capped at 70: no passing tool call yet; the tests add up to 90. Why scores are capped
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
Score 70/100 · Tools 4 · Token cost ~711 · 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 (official) completed an MCP handshake without credentials and exposed 4 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 4
- Context cost
- 711 model-visible tokens (name, description, inputSchema; tiktoken cl100k_base)
Extra payload (sent by the server, usually not read by the model): 60 tokens; raw tools/list total 771. Clients differ in what they forward. ranking · add up your servers' context cost - API key
- No key to connect (handshake passed)
- Tested
- 2026-10-30
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| 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. Automated check of the package's own README (README shipped in npm package). |
| license | pass | 10 | MIT (OSI-approved). |
Local-model readiness
Schema context cost: ~711 tokens for 4 tools (3,363 bytes) · about 9% of an 8k context. Method: tiktoken cl100k_base over compact JSON of name+description+inputSchema (approximate).
Small-model friendly (schema heuristic, not a model result): unknown.
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
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Tool-schema 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 it is safe to give it access to your data.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-10-30 test run; changes appear after the next test.
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.
Raw test record (JSON)
{
"name": "@unisat/openapi-mcp",
"version": "1.0.0",
"registry": "npm",
"status": "working",
"tested": "2026-10-30",
"tools_count": 4,
"tools_schema_tokens_est": 711,
"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. Automated check of the package's own README (README shipped in npm package)."
],
"license": [
"pass",
10,
"MIT (OSI-approved)."
]
}
}Install
npx -y @unisat/openapi-mcp
Tools listed
list_operations, get_operation, get_status, call_api
Quick config
{
"mcpServers": {
"unisat-openapi-mcp-official": {
"command": "npx",
"args": [
"-y",
"@unisat/openapi-mcp"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install @unisat/openapi-mcp(Node 20). This is the exact command we ran on 2026-10-30. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (4 in our test).
{
"mcpServers": {
"unisat-openapi-mcp-official": {
"command": "npx",
"args": [
"-y",
"@unisat/openapi-mcp"
]
}
}
}Test history
No dated events yet.
FAQ
Is UniSat OpenAPI MCP (official) deprecated?
No. @unisat/openapi-mcp was not deprecated or archived when we last tested it on 2026-10-30.
What replaces UniSat OpenAPI MCP (official)?
Nothing; UniSat OpenAPI MCP (official) is not deprecated as of 2026-10-30.
Does UniSat OpenAPI MCP (official) need an API key?
No. It completed an MCP handshake with no credentials and listed 4 tools.
Embed the badge
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.