Developer · Remote MCP server
Statey
An agent-native database over MCP: shared, validated, structured records in every AI chat.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.statey/statey- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-07-09
- Updated
- 2026-07-09
- Publisher
- ai.statey
- Namespace
- Namespace verified by the MCP Registry via the domain statey.ai · how
- Website
- statey.ai
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.statey.ai/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Statey
Statey is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.statey.ai/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. 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 |
|---|---|
| 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 |
| Statecore MCPAuditable memory for coding agents: evidence chains, supersession history, keyless embedded SQLite. | 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 |
| 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 |
| Statping MCPService rollup, ports, DNS propagation and TLS chains - no API key. | Local · stdio |
| Statuscake MCPUptime, TCP port, SSL chain and DNS propagation checks - no API key. | Local · stdio |