Log inSubmit server
Sdk logo

Sdk

by 2s-io

Accesses hundreds of data, validation, AI, and agent tools through MCP with per-call USDC payments and optional free trials.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Sdk

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "2s-io-sdk": {
      "command": "npx",
      "args": [
        "-y",
        "@2sio/mcp"
      ],
      "env": {
        "EVM_PRIVATE_KEY": "YOUR_VALUE_HERE",
        "TWOS_TRIAL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 575 tools correctly (1mo ago).

Overview

The 2s-io/sdk MCP server exposes the 2s.io API to MCP-compatible hosts, covering public data, research, validation, AI processing, crypto, and agent infrastructure. It can discover endpoints with natural-language search and group up to 50 eligible calls behind one atomic x402 payment. Run it locally with Node or connect to the hosted Streamable HTTP endpoint; paid calls use USDC on Base or Solana, while each endpoint offers one free trial call per hour. Reach for it when an agent needs access to many specialized APIs without managing separate provider credentials.

Use cases

  • Discover specialized data endpoints from natural-language tasks
  • Query public government and scientific datasets
  • Validate financial, product, and blockchain identifiers
  • Batch related API calls under one atomic payment

Key features

  • Natural-language endpoint discovery
  • Atomic batches of up to 50 calls
  • Per-call USDC payments via x402
  • Hourly free trial calls without a wallet
  • Hundreds of data and utility endpoints
  • Local stdio and hosted HTTP MCP access

Tools575

What Sdk lets your agent do. Expand a tool for its parameters.

Verified live~93.3k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

18/18 checks healthy over the last 77d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 6d ago via OSV.dev · @2sio/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars9Stargazers on the source repository.
npm downloads1.4kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed575Callable tools this server registers over MCP.
Directory activity8 viewsConfig copies, upvotes, and views on AllMCPs.

How Sdk works

What 2s-io/sdk MCP server does

The 2s-io/sdk MCP server connects MCP hosts to the 2s.io catalog of hundreds of API endpoints. Its coverage includes government and legal records, agriculture, labor, maritime data, music metadata, patents, crypto checks, financial identifiers, geocoding, weather, academic papers, internet diagnostics, and AI operations such as summarization, translation, extraction, screenshots, and image description.

The repository also contains client SDKs for TypeScript/Node, Python, LangChain, LlamaIndex, Go, and Rust. This listing focuses on the MCP server, which makes the catalog available to MCP-aware applications rather than requiring a separate integration for each data source.

How it works

An agent can call search.endpoints with a natural-language description of its task. The response ranks matching endpoints and includes identifiers, paths, HTTP methods, prices, and descriptions, helping the agent select a suitable operation before making a request.

batch.run accepts up to 50 ordinary catalog calls and settles them through one x402 payment. The total price is the exact sum of the individual calls. The batch is atomic: if a sub-call fails, the result reports the failures and the payment is not charged. Nested batches and certain bearer-only, deprecated, variable-priced, or metered-upstream endpoints are excluded.

For paid use, the client signs a single-use USDC authorization per call. A configurable price ceiling and an approval hook can be used to control signing.

Setup and configuration

Install and run the local MCP process with:

Terminal
npx -y @2sio/mcp

Claude Desktop can launch that command as a stdio server and pass EVM_PRIVATE_KEY in its environment. The key is used to authorize Base payments; the material does not describe a separate API key or account-registration flow. Trial mode can be enabled with --trial or TWOS_TRIAL=1, allowing one real free call per endpoint per hour without a wallet.

The hosted MCP endpoint is https://2s.io/mcp and uses Streamable HTTP. Hosted requests can supply X-EVM-Private-Key for Base payments. The README warns that this option sends the signing key through 2s.io infrastructure, whereas the local 2s-io/sdk MCP server keeps the key on the client machine.

Tools and capabilities

Representative tools include:

  • Discovering catalog endpoints with search.endpoints.
  • Running atomic multi-call requests with batch.run.
  • Querying soil, drought, USDA agriculture, BLS labor, FCC, Coast Guard, port, and MusicBrainz data.
  • Searching USPTO patents and retrieving application details and documents.
  • Validating crypto addresses, EVM transactions, IBANs, GTINs, ABA routing numbers, LEIs, and BICs.

The live catalog and OpenAPI description are available from 2s.io, so the listed tools should not be treated as an exhaustive inventory.

Limitations and notes

Calls beyond the free hourly trial require USDC and a compatible signing setup. The default payment limit is unlimited unless maxPriceUsd is configured, so applications should set a ceiling when autonomous spending must be constrained. Each authorization has a 60-second deadline and does not create a continuing allowance. The 2s-io/sdk MCP server is therefore best suited to agents that can handle wallet-based, per-request payments rather than environments restricted to conventional API-key authentication.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Sdk

Run `npx -y @2sio/mcp` for the local MCP server. Claude Desktop can launch this command as a stdio server.

Yes. The README provides a Claude Desktop configuration that runs `npx -y @2sio/mcp` and passes `EVM_PRIVATE_KEY`.

No API key, account, or signup is described. Paid calls require a wallet signing setup for USDC, while trial mode works without a key or wallet.

Paid calls use x402 and USDC on Base or Solana. Each endpoint has a per-call price, and batches cost the exact sum of their sub-calls.

Related MCP servers

All in Aggregators All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSdk AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/2s-io-sdk?style=directory)](https://allmcps.com/mcp/2s-io-sdk)
HTML Embed
<a href="https://allmcps.com/mcp/2s-io-sdk"><img src="https://allmcps.com/api/badge/2s-io-sdk?style=directory" alt="Sdk on AllMCPs" /></a>