MCP Spine

@Donnyb369

代码仓库

基本信息

分类

其他

许可证

MIT

传输方式

stdio

作者

Donnyb369

提交者

Donnyb369

关于 MCP Spine

Context Minifier & State Guard — Local-first MCP middleware proxy

#proxy #middleware #security #mcp #token-optimization#schema-minification#audit #rate-limiting #windows #python

MCP Spine 配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "spine": {
      "command": "python",
      "args": [
        "-m",
        "spine.cli",
        "serve",
        "--config",
        "/path/to/spine.toml"
      ],
      "cwd": "/path/to/mcp-spine"
    }
  }
}

MCP Spine 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表，不代表服务没有工具。请查阅项目文档了解支持的能力。

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is Mcp Spine?

Mcp Spine is a local-first proxy that sits between an MCP client (such as Claude Desktop) and your MCP servers. It adds security, routing, token control, and compliance — handling what goes in, what comes out, and what gets logged — all through a single configuration file.

How to use Mcp Spine?

Install with pip install mcp-spine (add [ml] for semantic routing). Run mcp-spine init for an interactive setup wizard, then start the proxy with mcp-spine serve --config spine.toml. Replace individual MCP server entries in your client configuration with a single Spine entry pointing to the proxy.

Key features of Mcp Spine

Security proxy with rate limiting, secret scrubbing, and path jails
Semantic router using local embeddings (no API calls)
Schema minifier achieving 61% token savings at default level
Human-in-the-loop confirmation for destructive tools
Prompt injection detection in tool responses
Multi-user audit trail with session tagging
Web dashboard for live monitoring and analytics

Use cases of Mcp Spine

Centralize security policies across multiple MCP servers
Reduce token consumption by minifying tool schemas and routing only relevant tools
Enforce daily token budgets per user or server
Audit all tool calls with session tracking for shared deployments
Prevent prompt injection and command injection in agent workflows

常见问题

How is Mcp Spine different from running MCP servers directly?

It acts as a middleware proxy that adds security, routing, token control, and audit logging between the client and servers — capabilities not available when connecting tools directly.

What are the runtime requirements?

Python 3.8+ is required. The base install uses only standard library dependencies; optional ML dependencies (`pip install mcp-spine[ml]`) enable semantic routing.

Where does audit data live?

All audit events, token budgets, and session data are stored in a local SQLite database (default `spine_audit.db`). No data leaves your machine.

What transport protocols are supported?

stdio (local subprocess servers), SSE (legacy remote servers), and Streamable HTTP (MCP 2025-03-26 spec).

Does semantic routing require external API calls?

No. It uses the local embedding model `all-MiniLM-L6-v2` with ChromaDB for tool indexing — all processing stays on your machine.

其他分类下的更多 MCP 服务器

FastMCP v2 🚀

jlowin

🚀 The fast, Pythonic way to build MCP servers and clients.

26.0K

Codelf

unbug

A search tool helps dev to solve the naming things problem.

14.2K

Reactive Resume

amruthpillai

A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!

39.5K