Developer · Local MCP server
Statecore MCP
Auditable memory for coding agents: evidence chains, supersession history, keyless embedded SQLite.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.yul761/statecore-mcp- Version
- 0.1.2
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-08-15
- Updated
- 2026-08-15
- Publisher
- yul761 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/yul761) · how
- Listed under
- SQLite MCP servers
- Repository
- github.com/yul761/StateCore
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | statecore-mcp | 0.1.2 | stdio |
How to connect Statecore MCP
Statecore MCP runs locally from a Node.js package published to the npm registry: statecore-mcp version 0.1.2. 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 statecore-mcp@0.1.2. It reads these environment variables: STATECORE_SCOPE, FEATURE_LLM, MODEL_API_KEY (secret), MODEL_BASE_URL and MODEL_NAME; 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": {
"statecore-mcp": {
"command": "npx",
"args": [
"-y",
"statecore-mcp@0.1.2"
],
"env": {
"STATECORE_SCOPE": "<value>",
"FEATURE_LLM": "<value>",
"MODEL_API_KEY": "<secret>",
"MODEL_BASE_URL": "<value>",
"MODEL_NAME": "<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 developer servers
| Server | Runs |
|---|---|
| Stata MCPLet LLM help you achieve your regression analysis with Stata. | Local · stdio |
| State of Web VitalsCore Web Vitals metrics by CMS, CDN, and framework - free remote MCP, no auth. | Remote · HTTPLive check: ✓ handshake |
| state-traceBounded working memory for coding agents - typed nodes, current-vs-stale state, MCP-mountable. | Local · stdio |
| StatecliState replay and self-debugging for AI agents. Track, replay, undo, checkpoint. | Local · stdio |
| Statewrightgate MCPA paid remote MCP for Statewright, built to return verdicts, receipts, usage logs, and audit-ready J. | Remote · HTTPLive check: ✗ no handshake |
| StateyAn agent-native database over MCP: shared, validated, structured records in every AI chat. | Remote · HTTPLive check: sign-in required |
| StaticbotDeploy websites, migrate app backends, and run continuous sync with explicit approval gates. | Local · stdio |
| statlyte - live LLM pricingLive LLM pricing, context windows and model ids, read from each vendor's own page every 3 hours. | Local · stdio |