Sharpe Terminal
NPM · @SHARPE-TERMINAL/MCP-SERVER · 2 COMPONENTS
Live crypto derivatives data: funding rates, open interest, basis, arbitrage and listings
Available components
Last scanned (22 hours ago)
Scores higher than 37% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability72
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 13439 tokens (~268/item across 50 items; 45 tools + 5 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (93% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_arbitrage_cex_spot_transfer" implies "transfer" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 47 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Nov 26 +10
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.84 ▲ functional
- 19 Nov 26 −10
- Known CVEs: pass → unverified ▼ security
- Dependency health: 0.85 → unverified ▼ functional
- Package version: 4.1.0 → 4.3.0 functional
- Package version: 4.1.0 → 4.2.0 functional
- 18 Nov 26 +1
- Tool coverage: 100% → 95% ▼ functional
- Stability: unverified → 0.07 ▲ functional
- Package version: 4.0.1 → 4.1.0 functional
- 16 Nov 26 63
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/@sharpe-terminal/mcp-server@4.3.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
search_market_cap Market cap search ~64
Search crypto and supported TradFi assets by name or ticker. Returns matching assets with asset class, market cap, and nullable price, day return, FDV, ATH, and estimated ATH market cap fields.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | yes | Search query (2-100 characters). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| meta | object | yes | Which route answered, what the API said about the data's freshness, and whether the client cut the answer to fit the agent's context window. |
| pagination | object | – | Present when the answer is one page: pass `cursor` back to read the next one. |
No examples provided.
How do I install the Sharpe Terminal MCP server?
Sharpe Terminal runs locally as an npm package, launched with npx -y @sharpe-terminal/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @sharpe-terminal/mcp-server
claude mcp add ai-sharpe-mcp -- npx -y @sharpe-terminal/mcp-server
What is the Sharpe Terminal MCP server?
Sharpe Terminal is an MCP server listed in the public MCP registry as ai.sharpe/mcp. Live crypto derivatives data: funding rates, open interest, basis, arbitrage and listings. This page covers its npm package (@sharpe-terminal/mcp-server).
Is the Sharpe Terminal MCP server safe to use?
Sharpe Terminal scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Sharpe Terminal MCP server expose?
Sharpe Terminal exposes 45 tools: get_api_coverage, get_arbitrage_borrow_rates, get_arbitrage_cex_spot_transfer, get_arbitrage_cross_exchange, get_arbitrage_dated_futures_basis, and 40 more. Their descriptions and schemas cost roughly 12,771 tokens of context every time the server is loaded.
Is the Sharpe Terminal MCP server still maintained?
Sharpe Terminal is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Sharpe Terminal MCP server under?
Sharpe Terminal declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Sharpe Terminal MCP server?
VerifyMCP ran 15 checks on Sharpe Terminal, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Sharpe Terminal: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.