Inistate MCP server
online · 100% uptimeio.github.Inistate/inistate-mcp·v1.3.5·1 starsMCP server for the Inistate platform: module discovery, entry management, and activity submission.
not scanned yet
1 stars50 downloads/wk
Reviews
Write oneNobody has reviewed Inistate MCP yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Inistate MCP tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Inistate MCP compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 99/100
- higher than 99% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 476 ms
- faster than 31% of 30,031 servers
- GitHub stars
- 1
- more than 65% of 28,688 servers
- Downloads a week
- 50
- more than 42% of 12,191 servers with a package
Release history: 5 versions in the registry since 2026-06-25, latest 2026-10-22, typically one every 6 days.
Install Inistate MCP in Claude Code, Cursor or VS Code
claude mcp add --transport http inistate-mcp https://mcp.inistate.com/mcp
What the publisher says
From the Inistate MCP repository's README, as published. We do not edit it. Read it on GitHub
Inistate MCP Server
MCP server for the Inistate platform — module discovery, entry management, and activity submission.
Setup
Environment Variables
Install from npm (recommended)
No clone or build needed — npx will fetch and run the published package on demand:
npx -y inistate-mcpOr install globally:
npm install -g inistate-mcp
inistate-mcpInteractive setup (recommended)
Run the binary in a terminal with no MCP client attached and it walks you through entering your API token and picks the right config file for your client:
npx -y inistate-mcp
# or, explicitly:
npx -y inistate-mcp setupSupported clients: Claude Desktop, Claude Code (global or project-local .mcp.json), Cursor, Windsurf, Codex CLI, VS Code (user profile or workspace .vscode/mcp.json), Cline, Gemini CLI (global or workspace). Pick "Print config only" to get a JSON block to paste anywhere else.
The wizard only runs when stdin is a TTY (i.e., you launched it yourself). When an MCP client spawns the binary via piped stdio, it skips the wizard and runs as a normal MCP server — set INISTATEMCPNO_SETUP=1 if you need to force server mode from a terminal.
Claude Desktop Configuration
Add to your claudedesktopconfig.json:
{
"mcpServers": {
"inistate": {
"command": "npx",
"args": ["-y", "inistate-mcp"],
"env": {
"INISTATE_API_TOKEN": "your-token-here"
}
}
}
}Claude Code Configuration
claude mcp add inistate -e INISTATE_API_TOKEN=your-token-here -- npx -y inistate-mcpInstall from source
git clone https://github.com/Inistate/inistate-mcp.git
cd inistate-mcp
npm install
npm run buildThen point your MCP client at node /absolute/path/to/inistate-mcp/build/index.js.
Tools
Tools marked (configure) are only exposed in configure mode — see Modes. Tools the active backend cannot serve (e.g. scaffold_module on the hosted Platform) stay registered but return a structured capability message instead of failing silently.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Inistate MCP: common questions
- Is Inistate MCP server safe?
- Yes, by our scan: it is graded A (99/100). Read the Inistate MCP safety report
- How do I install Inistate MCP?
- It runs remotely at mcp.inistate.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Inistate MCP need an API key?
- Yes. The registry entry asks for
INISTATE_API_TOKEN. - Is Inistate MCP maintained?
- The last commit was 39 days ago (2026-09-26). The latest release is v1.3.5.
- Is Inistate MCP up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Inistate MCP compare with other MCP servers?
- safety score 99/100 (higher than 99% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 476 ms (faster than 31% of 30,031 servers). Full comparison.