1. Conduid
  2. Developer Tools
  3. Example MCP Stateful
MCP server · Developer Tools

Example MCP Stateful

stateful MCP server with Redis sessions, event sourcing, and horizontal scaling

54Fair

Scored 4 months ago · breakdown

About Example MCP Stateful

Example MCP Stateful is an MCP server published by yigitkonur in the Developer Tools category: stateful MCP server with Redis sessions, event sourcing, and horizontal scaling. It has been installed 0 times through Conduid.

The repository has 1 stars and 0 forks, with the last commit 6 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.

Install

Install
npx example-mcp-stateful

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

Ask AI about Example MCP Stateful

Powered by Claude · Grounded in docs

I know everything about Example MCP Stateful. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

example-mcp-stateful

learning-first boilerplate for stateful MCP servers over Streamable HTTP with TypeScript SDK v2.

part of a series: stdio · stateless · stateful (you are here) · sse

what it does

  • runs a stateful MCP server where sessions persist across requests with in-memory storage
  • implements the full Streamable HTTP lifecycle: POST /mcp (JSON-RPC), GET /mcp (SSE stream), DELETE /mcp (session close)
  • demonstrates SSE resumability via an in-memory event store with Last-Event-Id replay
  • registers example tools (add_note, list_notes, simulate_work), resources (session://overview, session://notes/{index}), and a prompt (study-notes)
  • includes a scaffold CLI to generate new projects from templates
  • vendors MCP TypeScript SDK v2 pre-release tarballs for reproducible installs

quick start

npm install
npm run dev

server starts at http://127.0.0.1:1453. endpoints:

  • POST /mcp -- JSON-RPC requests
  • GET /mcp -- SSE stream
  • DELETE /mcp -- close session
  • GET /health -- health check
  • GET /sessions -- list active sessions

Docker alternative:

docker compose up --build -d

scaffold cli

generate a new project from the included templates:

npm run create -- init my-mcp-app

options: --force, --dir <path>, --sdk vendored|registry. see scaffold CLI docs for details.

documentation

doc description
getting started install, run, verify endpoints
architecture module layout, session lifecycle, resumability
scaffold cli generate new projects from templates
sdk v2 notes v2 packages, vendoring, migration
validation smoke tests, primitive checks, release checklist

sdk v2 context

this project targets MCP TypeScript SDK v2 pre-release (2.0.0-alpha.0). the v2 SDK splits the monolithic @modelcontextprotocol/sdk package into server, node, client, and core. this repo uses @modelcontextprotocol/server for McpServer and @modelcontextprotocol/node for NodeStreamableHTTPServerTransport. vendored tarballs under vendor/mcp-sdk-v2/ ensure reproducible installs until v2 reaches stable release.

license

MIT

README mirrored from the source repository 4 months ago. The original is authoritative.

Questions

About Example MCP Stateful

How do I install Example MCP Stateful?

Run npx example-mcp-stateful, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is Example MCP Stateful safe to use with an AI agent?

Its trust score is 54 out of 100 (fair). It passes 0 of 1 static security checks; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Example MCP Stateful still maintained?

The last commit was 6 months ago, with 0 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.