MCP Router 27b899e3

MCP安全风控

提供方 AshrafMd-1

安全风控 未标注 OAuth 授权 社区 / 第三方 ClaudeCursor

MCP Gateway是一个自托管的多路复用网关,可将多个上游MCP服务器聚合为单一端点,为AI客户端提供统一的工具访问控制。

一句话选型结论

按资料字段整理

MCP Router 27b899e3 属于安全风控类 MCP 服务器,传输方式未标注,OAuth 授权,可直接接入 Claude、Cursor,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类安全风控 传输方式未标注 鉴权OAuth 授权 部署方式未标注
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

安全风控
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

多路复用TypeScript本地部署网关服务访问控制OAuth支持自托管

安装与配置

未标注 OAuth 授权
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
资产与漏洞排查

盘点资产、扫漏洞、看暴露面。

日志与审计

汇总日志、查异常行为。

合规检查

按规则检查配置与权限是否合规。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在安全风控场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MCP Router 27b899e3当前 未标注 未标注 未标注 无 2026-05-17
Cyber Strike AI 75 未标注 未标注 无 2026-05-17
mcp-for-beginners 未标注 stdio · 本地进程 本地部署 有 2026-04-13
casdoor 未标注 stdio · 本地进程 本地部署 有 2026-04-12
kubeshark 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Modelcontextprotocol C22988b0 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

安全风控
字段来自项目仓库与公开索引,中文说明由本站标注
提供方AshrafMd-1上游标注的维护方 AshrafMd-1
分类安全风控本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

8.5 KB
来自项目仓库与上游目录的原文,未做删改

MCP Gateway [alpha]

A self-hosted gateway that multiplexes multiple upstream MCP servers into a single endpoint. AI clients (Claude, Cursor, etc.) connect once and get access to whichever tools the admin has granted them.```
AI Client (Claude/Cursor)
│ Bearer token
▼
┌─────────────┐ allowlist policy
│ MCP Gateway │──────────────────────────────┐
└─────────────┘ │
│ │ │ │
▼ ▼ ▼ ▼
Linear Granola local CLI tool catalog
(OAuth) (OAuth) (STDIO) (per client)


## Features

### Connector types

| Type | Auth | Example |
|------|------|---------|
| HTTP - OAuth URL | OAuth 2.0 + PKCE, auto-discovery (RFC 9728), dynamic client registration | Figma, GitHub, Atlan |
| HTTP - JSON config | API key / custom headers | Any HTTP MCP server |
| STDIO | env vars / none | Local CLI tools, `npx` servers |

### Per-client access control
- Create named clients, assign a subset of connectors, then allowlist specific tools (glob patterns supported: `github.*`, `figma.get_*`)
- Issue multiple bearer tokens per client; revoke or rotate individually
- Tool names are exposed as `connector__tool` so there are no collisions across connectors

### OAuth support
- Auto-discovers authorization server via `/.well-known/oauth-protected-resource` → `/.well-known/oauth-authorization-server` chain (RFC 9728)
- Dynamic client registration when the provider supports it; falls back to manually configured `clientId`/`clientSecret`
- PKCE (`S256`) on every authorization request
- Transparent token refresh on `401` - single concurrent refresh per connector (lock prevents duplicate grant requests)
- `auth_failed` guard: once a refresh token is known expired, all further calls are rejected immediately with a structured error pointing to `/admin/connectors/:id/oauth/start`

### Storage & security
- PostgreSQL with auto-migration on startup (`AUTO_MIGRATE=true`)
- Connector credentials (OAuth tokens, API keys) encrypted at rest with AES-GCM (`ENCRYPTION_KEY`)
- Admin sessions stored server-side; short-lived by default (`ADMIN_SESSION_HOURS`)
- `sanitizeConfig` strips `token`, `secret`, and `password` fields before returning connector config to the browser

### Admin UI
- Vanilla JS single-page app at `/admin/`
- Connectors view: create / edit / delete, OAuth flow, health check, tool discovery
- Clients view: create / edit / delete, access policy (connector selection + tool allowlist), token management (issue / revoke / rotate)

### MCP protocol
- Protocol version `2025-06-18`
- Proxies `tools/list`, `tools/call`, `resources/list`, `resources/read`, `prompts/list`, `prompts/get`
- All downstream errors normalized to typed MCP error codes (`UPSTREAM_UNAUTHORIZED`, `UPSTREAM_TIMEOUT`, `UPSTREAM_UNAVAILABLE`, etc.)
- SSE and plain JSON response bodies both handled

## Tech stack

- Node.js 22 + TypeScript (ESM)
- Fastify 5
- PostgreSQL 16
- Vitest

## Environment

Copy `.env.example` to `.env` and fill in:

| Variable | Required | Default | Notes |
|----------|----------|---------|-------|
| `ADMIN_TOKEN` | yes | - | Password for the admin UI |
| `DATABASE_URL` | yes | - | `postgres://user:pass@host:5432/db` |
| `ENCRYPTION_KEY` | yes | - | 64-char hex or 32-byte base64 (AES-GCM key) |
| `HOST` | no | `0.0.0.0` | Bind address |
| `PORT` | no | `3000` | Listen port |
| `AUTO_MIGRATE` | no | `true` | Run DB migrations on startup |
| `ADMIN_SESSION_HOURS` | no | `24` | Admin session lifetime |

Generate a key:```bash
node -e "console.log(require('crypto').randomBytes(32).toString('hex'))"

Quick start with Docker```bash

cp .env.example .env

Edit .env - set ADMIN_TOKEN and ENCRYPTION_KEY at minimum

docker compose up --build


Endpoints:

| Path | Purpose |
|------|---------|
| `http://localhost:3000/admin/` | Admin UI |
| `http://localhost:3000/mcp` | MCP endpoint (for clients) |
| `http://localhost:3000/health` | Health check |

## Run locally```bash
npm install
npm run dev        # tsx watch - auto-restarts on change

Build and start:```bash
npm run build
npm start


## MCP client setup

After issuing a token in the admin UI, add this to your client config:```json
{
  "mcpServers": {
    "gateway": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "http://127.0.0.1:3000/mcp",
        "--header",
        "Authorization: Bearer <CLIENT_TOKEN>"
      ]
    }
  }
}

Admin walkthrough

  1. Open /admin/ and log in with ADMIN_TOKEN
  2. Connectors → Create connector
    - OAuth URL: paste the MCP server URL; click "Connect OAuth" to go through browser OAuth
    - JSON config (HTTP): paste URL + API key or headers
    - JSON config (STDIO): paste {"command": "npx", "args": ["-y", "some-mcp-server"]}
  3. Click Discover Tools to populate the tool catalog
  4. Clients → Create client
  5. Open the client → Access tab → select connectors and check the tools to allow
  6. Tokens tab → Issue token (shown once - copy it)
  7. Paste the token into your AI client config

API reference

Admin endpoints (session cookie required)

Method Path Description
POST /admin/login Login, sets mgw_admin_session cookie
POST /admin/logout Invalidate session
GET /admin/connectors List connectors
POST /admin/connectors Create connector
PUT /admin/connectors/:id Update connector
DELETE /admin/connectors/:id Delete connector (blocked if in use)
POST /admin/connectors/:id/discover Refresh tool catalog
GET /admin/connectors/:id/health Live health check
POST /admin/connectors/:id/oauth/start Begin OAuth flow
GET /admin/oauth/callback OAuth redirect callback
GET /admin/tool-catalog?connectorId= List tools for connector
GET /admin/clients List clients
POST /admin/clients Create client
PUT /admin/clients/:id Update client
DELETE /admin/clients/:id Delete client
GET /admin/clients/:id/policy Get access policy
PUT /admin/clients/:id/policy Update access policy
GET /admin/clients/:id/tokens List tokens
POST /admin/clients/:id/tokens Issue new token
DELETE /admin/clients/:id/tokens/:tokenId Revoke token
POST /admin/tokens/:id/rotate Rotate token

MCP endpoint

POST /mcp - Bearer token auth. Accepts JSON-RPC 2.0.

Supported methods: initialize, tools/list, tools/call, resources/list, resources/read, prompts/list, prompts/get

Testing```bash

npm test
```

Unit tests cover policy evaluation and error mapping.

Known issues & planned work

Critical

  • OAuth stability (Figma, GitHub, Atlan) - Authentication failures still observed for these providers. Investigation ongoing; likely scope or audience parameter mismatches.
  • Issue Token before initial save - Issuing a token immediately after creating a client (before the first save completes) can fail. Needs a guard in the UI to wait for the client record to be confirmed.

High

  • Unified tool filtering - The DB schema stores both allowedTools and deniedTools, but the policy evaluator only enforces allowlists. Goal: a single list where every tool is either Allowed or Hidden, removing the denylist concept entirely.
  • Raw config textarea for OAuth connectors - Advanced overrides (resource, audience, scope, clientId) are only accessible for JSON config connectors. OAuth URL connectors need the same raw config panel.
  • Tools list for all connector types - The tools list view is not shown for all connector types in the admin UI.

UI / UX

  • Access tags active state - The current "everything green" chip styling makes it hard to tell which tab is active. Needs better visual contrast.
  • Tool description tooltips - Tool tags should show the full description on hover.
  • Global loading states - API requests lack consistent loading indicators; users can interact with stale data during fetches.
  • API key not displayed on reopen - When a connector is saved with an API key, reopening it shows an empty field because credentials are redacted before being sent to the browser. The UI should indicate a key is stored and allow replacing it.
  • Enhanced error messages - Error display across the UI needs more actionable copy to help with troubleshooting.

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
MCP Router 27b899e3 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

MCP Router 27b899e3 怎么在 Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

MCP Router 27b899e3 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

MCP Router 27b899e3 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

MCP Router 27b899e3 支持哪些客户端?

资料标注支持 Claude、Cursor;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

MCP Router 27b899e3 能提供哪些能力?

资料显示能力标签包括 访问控制、TypeScript、Claude。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。