Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.2s-io/mcp

NPM · @2SIO/MCP

575+ agent tools: data, AI gateway, storage/queues/watchers. x402 USDC, no keys, usage billing.

Available components

0 this week 62 Trust /100

Last scanned (23 hours ago)

Scores higher than 30% of npm servers

Trust breakdown (7 categories)

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 Security82
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 206 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to 2s-io/sdk). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 91 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: the captured schema was too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge it on a partial copy.Unverified
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage0
  • Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge them on a partial copy.Unverified
Tool Safety0
  • Tool safety not yet verified: the captured tool definitions were too large for us to store in full (the trim removes the very descriptions this category reads), or the server stopped listing its tools part-way.Unverified
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 3 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

What we tested

Checks we ran (11)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Stability
  • MCP protocol

Checks we could not complete (3)

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.

  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: the captured schema was too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge it on a partial copy.
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge them on a partial copy.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: the captured tool definitions were too large for us to store in full (the trim removes the very descriptions this category reads), or the server stopped listing its tools part-way.

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 →

Changelog

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.

  • 15 Nov 26 0
    • Dependency health: partial → 0.93 functional
  • 13 Nov 26 0
    • Dependency health: 0.93 → partial functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Nov 26 −2
    • Stability: pass → 0.83 functional
  • 1 Nov 26 0
    • Stability: 0.97 → pass security
  • 31 Oct 26 0
    • Stability: pass → 0.97 functional
Diagnostics

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/@2sio/mcp@1.82.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo 2s-io/sdk
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/2s-io/sdk/.github/workflows/publish-npm.yml@refs/heads/main
Rekor log index 2549506778
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:d1029263016fc09454e267ed23b73e13233ef417644b3f4dd610645ce8fa81f36f5008c7c8c0a2f8f99b19911d84f5d0437f06f1c942e062f789b1e9a

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 206 packages
Packages resolved 206
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 575 exposed · ~69,622 tokens partial

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 →

Tool Tokens
calendar.earnings ~141

No description provided.

NameTypeReqDescription
fromstring––
tickerstring––
tostring––

No output schema declared.

No examples provided.

calendar.holidays ~213

No description provided.

NameTypeReqDescription
countrystringyes–
langstring––
regionstring––
typesstring––
yearnumberyes–

No output schema declared.

No examples provided.

calendar.ipo ~122

No description provided.

NameTypeReqDescription
fromstring––
tostring––

No output schema declared.

No examples provided.

census.demographics ~155

No description provided.

NameTypeReqDescription
countystring––
statestringyes–
yearinteger––

No output schema declared.

No examples provided.

census.zipcode ~37

No description provided.

NameTypeReqDescription
zipstringyes–

No output schema declared.

No examples provided.

chem.compound ~83

No description provided.

NameTypeReqDescription
cidinteger––
inchikeystring––
namestring––
smilesstring––

No output schema declared.

No examples provided.

chinese.convert ~123

No description provided.

NameTypeReqDescription
fromstringyes–
textstringyes–
tostringyes–

No output schema declared.

No examples provided.

chinese.detect ~85

No description provided.

NameTypeReqDescription
textstringyes–

No output schema declared.

No examples provided.

chinese.pinyin ~133

No description provided.

NameTypeReqDescription
segmentedboolean––
textstringyes–
tonestring––

No output schema declared.

No examples provided.

class.industry-resolve ~74

No description provided.

NameTypeReqDescription
codestringyes–
systemstringyes–

No output schema declared.

No examples provided.

climate.station-history ~186

No description provided.

NameTypeReqDescription
dataTypesstring––
endDatestringyes–
startDatestringyes–
stationstringyes–

No output schema declared.

No examples provided.

climate.station-near ~62

No description provided.

NameTypeReqDescription
latnumberyes–
limitinteger––
lonnumberyes–
radius_kmnumber––

No output schema declared.

No examples provided.

clinical.study-detail ~143

No description provided.

NameTypeReqDescription
nctIdstringyes–

No output schema declared.

No examples provided.

clinical.trial-search ~115

No description provided.

NameTypeReqDescription
countrystring––
nctIdstring––
pageSizeinteger––
pageTokenstring––
phasestring––
querystring––
sponsorstring––
statusstring––

No output schema declared.

No examples provided.

code.repo-lookup ~75

No description provided.

NameTypeReqDescription
repostringyes–

No output schema declared.

No examples provided.

convert.currency ~167

No description provided.

NameTypeReqDescription
amountnumber––
datestring––
fromstringyes–
tostringyes–

No output schema declared.

No examples provided.

convert.unit ~142

No description provided.

NameTypeReqDescription
fromstringyes–
tostringyes–
valuenumberyes–

No output schema declared.

No examples provided.

countdown.gif ~90

No description provided.

NameTypeReqDescription
endDatestringyes–
fpsinteger––
heightinteger––
secondsinteger––
templatestring––
widthinteger––

No output schema declared.

No examples provided.

country.financials ~118

No description provided.

NameTypeReqDescription
codestring––

No output schema declared.

No examples provided.

country.lookup ~104

No description provided.

NameTypeReqDescription
alpha2string––
alpha3string––
fullTextboolean––
namestring––

No output schema declared.

No examples provided.

crypto.address-history ~193

No description provided.

NameTypeReqDescription
addressstringyes–
chainIdinteger––
endBlockinteger––
offsetinteger––
pageinteger––
sortstring––
startBlockinteger––

No output schema declared.

No examples provided.

crypto.address-safety ~129

No description provided.

NameTypeReqDescription
addressstringyes–
chainIdstringyes–

No output schema declared.

No examples provided.

crypto.address-screen ~118

No description provided.

NameTypeReqDescription
addressstringyes–

No output schema declared.

No examples provided.

crypto.address-validate ~64

No description provided.

NameTypeReqDescription
addressstringyes–
chainstringyes–

No output schema declared.

No examples provided.

crypto.balances ~126

No description provided.

NameTypeReqDescription
addressstringyes–
chainstring––
tokensstring––

No output schema declared.

No examples provided.

crypto.btc-address ~95

No description provided.

NameTypeReqDescription
addressstringyes–

No output schema declared.

No examples provided.

crypto.btc-fees ~77

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

crypto.btc-mempool ~84

No description provided.

NameTypeReqDescription
minBtcnumber––

No output schema declared.

No examples provided.

crypto.btc-tx ~81

No description provided.

NameTypeReqDescription
txidstringyes–

No output schema declared.

No examples provided.

crypto.btc-utxos ~93

No description provided.

NameTypeReqDescription
addressstringyes–
limitinteger––

No output schema declared.

No examples provided.

crypto.cex-klines ~143

No description provided.

NameTypeReqDescription
intervalstring––
limitinteger––
pairstringyes–

No output schema declared.

No examples provided.

crypto.cex-ticker ~92

No description provided.

NameTypeReqDescription
pairstringyes–

No output schema declared.

No examples provided.

crypto.chain-tvl-history ~130

No description provided.

NameTypeReqDescription
chainstringyes–
limitinteger––

No output schema declared.

No examples provided.

crypto.coin ~130

No description provided.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

crypto.coin-history ~122

No description provided.

NameTypeReqDescription
daysinteger––
idstringyes–
vsstring––

No output schema declared.

No examples provided.

crypto.contract ~151

No description provided.

NameTypeReqDescription
addressstringyes–
chainstringyes–
selectorstring––

No output schema declared.

No examples provided.

crypto.decode-calldata ~91

No description provided.

NameTypeReqDescription
datastringyes–

No output schema declared.

No examples provided.

crypto.defi ~179

No description provided.

NameTypeReqDescription
chainstring––
limitinteger––
protocolstring––

No output schema declared.

No examples provided.

crypto.defi-chains ~81

No description provided.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

crypto.defi-fees ~120

No description provided.

NameTypeReqDescription
kindstring––
limitinteger––
sortstring––

No output schema declared.

No examples provided.

crypto.defi-protocol-history ~144

No description provided.

NameTypeReqDescription
limitinteger––
slugstringyes–

No output schema declared.

No examples provided.

crypto.defi-yields ~169

No description provided.

NameTypeReqDescription
chainstring––
limitinteger––
minApynumber––
minTvlUsdnumber––
projectstring––
sortstring––
symbolstring––

No output schema declared.

No examples provided.

crypto.dex-networks ~87

No description provided.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

crypto.dex-ohlcv ~162

No description provided.

NameTypeReqDescription
addressstringyes–
aggregateinteger––
limitinteger––
networkstringyes–
timeframestring––

No output schema declared.

No examples provided.

crypto.dex-pools ~151

No description provided.

NameTypeReqDescription
kindstring––
limitinteger––
networkstringyes–

No output schema declared.

No examples provided.

crypto.dex-search ~125

No description provided.

NameTypeReqDescription
limitinteger––
networkstring––
querystringyes–

No output schema declared.

No examples provided.

crypto.dex-token-pools ~122

No description provided.

NameTypeReqDescription
addressstringyes–
limitinteger––
networkstringyes–

No output schema declared.

No examples provided.

crypto.ens-resolve ~93

No description provided.

NameTypeReqDescription
querystringyes–

No output schema declared.

No examples provided.

crypto.fear-greed ~82

No description provided.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

crypto.gas-oracle ~69

No description provided.

NameTypeReqDescription
chainstring––

No output schema declared.

No examples provided.

Install

How do I install the io.github.2s-io/mcp server?

io.github.2s-io/mcp runs locally as an npm package, launched with npx -y @2sio/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @2sio/mcp

# add to Claude Code
claude mcp add 2s-io-mcp -- npx -y @2sio/mcp
Common questions

What is the io.github.2s-io/mcp server?

io.github.2s-io/mcp is listed in the public MCP registry as io.github.2s-io/mcp. 575+ agent tools: data, AI gateway, storage/queues/watchers. x402 USDC, no keys, usage billing. This page covers its npm package (@2sio/mcp).

Is the io.github.2s-io/mcp server safe to use?

io.github.2s-io/mcp scores 62 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.

Is the io.github.2s-io/mcp server still maintained?

io.github.2s-io/mcp 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 io.github.2s-io/mcp server under?

io.github.2s-io/mcp 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 io.github.2s-io/mcp server?

VerifyMCP ran 11 checks on io.github.2s-io/mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 7 more. 3 items could not be completed, a gap on our side rather than a finding about io.github.2s-io/mcp: Schema quality, Tool coverage and Tool safety. 3 categories score 0 for that reason, because we only credit what we can confirm. 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.