Data · Local MCP server
Lithium Vault MCP
Primary-source lithium & battery-metals mining data (AISC, reserves, filings) via x402.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.ciinkwia/lithium-vault-mcp- Version
- 0.4.0
- Status
- Active
- Category
- data
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-08-10
- Updated
- 2026-08-10
- Publisher
- ciinkwia (GitHub) · 3 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/ciinkwia) · how
- Repository
- github.com/ciinkwia/lithium-vault-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | lithium-vault-mcp | 0.4.0 | stdio |
How to connect Lithium Vault MCP
Lithium Vault MCP runs locally from a Node.js package published to the npm registry: lithium-vault-mcp version 0.4.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y lithium-vault-mcp@0.4.0. It reads these environment variables: CDP_API_KEY_ID (required, secret), CDP_API_KEY_SECRET (required, secret), CDP_WALLET_SECRET (required, secret), CDP_ACCOUNT_NAME, VAULT_BASE_URL and X402_MAX_PRICE; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"lithium-vault-mcp": {
"command": "npx",
"args": [
"-y",
"lithium-vault-mcp@0.4.0"
],
"env": {
"CDP_API_KEY_ID": "<secret>",
"CDP_API_KEY_SECRET": "<secret>",
"CDP_WALLET_SECRET": "<secret>",
"CDP_ACCOUNT_NAME": "<value>",
"VAULT_BASE_URL": "<value>",
"X402_MAX_PRICE": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from ciinkwia (GitHub)
| Server | Runs |
|---|---|
| Prediction Market Signal MCPPolymarket + Kalshi odds, movers, gaps, watch, and X sentiment for AI agents. Pay per call via x402. | Local · stdio |
| Twitter Signal MCPLive X/Twitter search, profiles, leads, pain points, bot checks, AI digests. Paid per call, x402. | Local · stdio |
More data servers
| Server | Runs |
|---|---|
| Lipe Court RecordSearch page-cited evidence from the public court record in Lipe v. Lupus Superior. | Remote · HTTPLive check: ✓ handshake |
| Listen to SadhuRead-only semantic search over Vedic scripture verses, commentaries, and recorded lectures. | Remote · HTTPLive check: ✓ handshake |
| listingsAPI MCPManage business listings, reviews, posts and local analytics across 50 plus sites. | Remote · HTTPLive check: sign-in required |
| Literature Review CouncilMulti-agent literature review: research, peer review, and synthesize grounded reports. | Local · stdio |
| Lithuanian Data Portal documentationSearch and read the Lithuanian Data Portal user guide and Data API docs, in Lithuanian and English. | Remote · HTTPLive check: ✓ handshake |
| Live UK Company SearchSearch current public UK company metadata from the official Companies House Public Data API.… | Local · stdio |
| LiveDataLink294 public-data tools across 60 domains; source freshness varies. Free tier. | Remote · HTTPLive check: ✓ handshake |
| LivingMeta - AI in ResearchRead-only MCP over the LivingMeta AI-in-Research corpus: 12,400 papers, gaps, priority agenda. | Remote · HTTPLive check: sign-in required |