Injective MCP
Official Injective MCP for natural-language queries and trading, incl.
- Sato Score48
- ChainsInjective
Injective MCP is an open-source MCP server by Injective Labs on Injective, with no code activity tracked. Sato Score 48/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →
See how to install Injective MCP →No code activity tracked
Listed from injective.com on 2026-07-13. Install: not attempted. Evidence →
Next step
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpAsk Sato Hub what is on record about Injective MCP before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Overview
Injective Labs' MCP server lets AI assistants query and trade on Injective through natural language, covering perpetual futures, spot transfers, cross-chain bridging, and EVM transactions. It runs over stdio transport locally and is open source (github.com/InjectiveLabs/mcp-server). An agent builder plugs it in to give an agent direct market data and trade-execution access on Injective rather than integrating the chain's APIs from scratch.
Sato Score
48/100· MediumHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 20/35
- Code transparency
- 8/20
- Interface verifiability
- 0/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 11/15
- Independent verification
- 3/10
Evidence — listed vs checked · what the words mean
Listed from injective.com on 2026-07-13. Install: not attempted.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Injective | self-reported | docs.injective.network | as of 2026-10-15 |
| Verification status | Self-Reported — not independently reviewed | self-reported | injective.com | as of 2026-10-15 |
| Install works | documented by the project, not run by Sato Hubnot attempted: the run did not complete and the log named no cause we could attribute | self-reported | docs.injective.network | as of 2026-09-21 |
| Website answers | answered (HTTP 200) | observed | injective.com | 2026-10-15 |
| Daily check record | 90 of 90 daily checks since 2026-07-17 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-14 |
| Deploys as | npm (local stdio, git clone + build)confidence 0.80 | self-reported | docs.injective.network | as of 2026-07-14 |
| Works with | Claude Desktopconfidence 0.75 | self-reported | docs.injective.network | as of 2026-07-14 |
| Sato Score | 48/100 (Medium)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-15 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Install — not run by us — the run did not complete and the log named no cause we could attribute
Runtime: Node.js >=22 (build from source)
git clone https://github.com/InjectiveLabs/mcp-server injective-mcp-server
cd injective-mcp-server
npm install && npm run build
{"mcpServers": {"injective": {"command": "node", "args": ["/path/to/injective-mcp-server/dist/mcp/server.js"], "env": {"INJECTIVE_NETWORK": "mainnet"}}}}You supply: INJECTIVE_NETWORK=mainnet, Node.js v22+ on PATH
claude mcp add satohub-injective-mcp -- node dist/mcp/server.js
A local server: your client runs this command on your machine. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.
Read from the project’s own docs as of 2026-09-21. What a deploy spec is →
Observed record — 91 daily checks since 2026-07-17
- Succeeded
- 91
- Failed
- 0
- Their error
- 0
- Unattributed
- 0
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.
Last 30 days — to 2026-10-15, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Skills that target this — 1, with disclosures
injective-evm-developerskills.sh · injectivelabs
39 installsDevelop EVM smart contracts and dApps on Injective
Disclosures describe what a skill declares and does; they are not safety verdicts. All skills →
Details
- Chains
- Injective
- Agent types
- MCP Server, Trading
- Open source
- Yes
- Deploys as
- npm (local stdio, git clone + build)
- Works with
- Claude Desktop
- Last checked
- 2026-10-15
Marketplace Signals
No marketplace signals recorded for this resource yet.
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Where Injective MCP fits
Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets, What Are MCPs? The Standard Way to Give Agents Tools
Listing History
Recorded changes to Injective MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Sep 21, 2026Verified: deploy spec
- Jul 18, 2026Sato Hub began tracking this listing
- Jul 14, 2026Enriched: supported integrations
- Jul 14, 2026Auto-enriched: deployment options
- Jul 13, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
Coinbase AgentKit
ActiveCoinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.
Hyperliquid
ActiveOnchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.
Model Context Protocol (MCP)
ActiveAnthropic's open standard for connecting AI systems to external tools and data sources.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Injective MCP
- Is Injective MCP open source?
- Yes. Injective MCP is open source under the Unknown license. Checked as of 2026-10-15.
- Which chains does Injective MCP support?
- Injective MCP lists support for Injective as of 2026-10-15.
- Is Injective MCP still maintained?
- Sato Hub tracks no commit or release for Injective MCP; it cannot say whether it is maintained.
- How do I install or run Injective MCP?
- Node.js >=22 (build from source). Install: git clone https://github.com/InjectiveLabs/mcp-server injective-mcp-server && cd injective-mcp-server && npm install && npm run build. Entry: {"mcpServers": {"injective": {"command": "node", "args": ["/path/to/injective-mcp-server/dist/mcp/server.js"], "env": {"INJECTIVE_NETWORK": "mainnet"}}}}. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (node dist/mcp/server.js (stdio)).
- Is Injective MCP verified on Sato Hub?
- No independent verification is on record for Injective MCP; its verification status is "Self-Reported" and its Sato Score is 48 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Injective MCP — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/injective-mcpData last refreshed 2026-10-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.