MCP Demo E60dd8b7

MCP安全风控

提供方 patrickyee23

安全风控 stdio · 本地进程 OAuth 授权 社区 / 第三方
查看接入方式

支持stdio和HTTP/SSE传输的Python MCP服务器,具有可选的OAuth2认证功能。

一句话选型结论

按资料字段整理

MCP Demo E60dd8b7 属于安全风控类 MCP 服务器,stdio · 本地进程,OAuth 授权,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

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

工具与能力

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

能力标签

适用场景

Python服务器Python本地部署HTTP/SSE传输OAuth2认证模型协议

安装与配置

stdio · 本地进程 OAuth 授权
客户端在本机拉起子进程,数据不出本机
pip install -r requirements.txt

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

    连接成功后客户端会列出约 2 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

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

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

日志与审计

汇总日志、查异常行为。

合规检查

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

选择建议

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

值得选的地方

  • 资料标注 2 个工具,职责相对集中,接入后不容易误操作。
  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

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

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MCP Demo E60dd8b7当前 2 stdio · 本地进程 本地部署 有 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

服务器档案

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

详细介绍

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

MCP Server with HTTP Transport

A Python MCP (Model Context Protocol) server that supports both stdio and HTTP/SSE transports with optional OAuth2 authentication.

Features

  • Dual transport support: stdio and HTTP with Server-Sent Events (SSE)
  • Optional OAuth2 authentication with two modes:
  • Built-in OAuth: Server issues its own tokens (demo/development)
  • External OIDC: Validates tokens via introspection endpoint (production)
  • Two tools: list_profiles and get_titans
  • Demo data with Attack on Titan characters
  • JSON-formatted responses
  • Environment-based configuration

Installation```bash

pip install -r requirements.txt


## Quick Start

### Option 1: Without OAuth (Simple)```bash
python server.py

Configure in ChatGPT:```json
{
"name": "Demo MCP Server",
"url": "http://127.0.0.1:8000/sse"
}


### Option 2: With Built-in OAuth (Demo/Development)

1. Generate OAuth2 credentials:```bash
python generate_credentials.py
  1. Start the server:```bash
    python server.py

3. Configure in ChatGPT with OAuth2 settings (see Configuration section below)

### Option 3: With External OIDC Provider (Production)

1. Configure external OIDC provider (Keycloak, Auth0, Okta, etc.)

2. Create `.env` file:```bash
OAUTH_ENABLED=true
OAUTH_MODE=external
OIDC_INTROSPECTION_ENDPOINT=https://auth.example.com/oauth/introspect
OIDC_CLIENT_ID=mcp-server-client-id
OIDC_CLIENT_SECRET=mcp-server-client-secret
  1. Start the server:```bash
    python server.py

4. Configure ChatGPT to point to your external OIDC provider

## Usage

### HTTP/SSE Transport (default)

Run the server with HTTP transport:```bash
python server.py
# Or explicitly:
python server.py --transport sse --host 127.0.0.1 --port 8000

The server will be available at:
- SSE endpoint: http://127.0.0.1:8000/sse
- Messages endpoint: http://127.0.0.1:8000/messages/

Stdio Transport

Run the server with stdio transport:```bash
python server.py --transport stdio


## Configuration

### OAuth Modes

The server supports two OAuth modes:

| Mode | Description | Use Case |
|------|-------------|----------|
| `builtin` | Server issues its own tokens | Demo, development, small deployments |
| `external` | Validates tokens via introspection | Production, enterprise, SSO |

### Mode 1: Built-in OAuth (Default)

For demo and development purposes. The server handles the complete OAuth flow.```bash
# .env file
OAUTH_ENABLED=true
OAUTH_MODE=builtin
OAUTH_CLIENT_ID=chatgpt-mcp-xxxxxxxxxxxx
OAUTH_CLIENT_SECRET=your-secret-here
SERVER_HOST=127.0.0.1
SERVER_PORT=8000
USE_HTTPS=false

Generate credentials automatically:```bash
python generate_credentials.py


**ChatGPT Configuration:**```json
{
  "name": "Demo MCP Server",
  "url": "http://127.0.0.1:8000/sse",
  "description": "Demo server with built-in OAuth",
  "auth": {
    "type": "oauth2",
    "authorization_url": "http://127.0.0.1:8000/oauth/authorize",
    "token_url": "http://127.0.0.1:8000/oauth/token",
    "client_id": "chatgpt-mcp-xxxxxxxxxxxx",
    "client_secret": "your-secret-here",
    "scope": "read write"
  }
}

Mode 2: External OIDC Provider (Token Introspection)

For production deployments. The server validates tokens from your external OIDC provider using the token introspection endpoint.```bash

.env file

OAUTH_ENABLED=true
OAUTH_MODE=external

Token Introspection Configuration

OIDC_INTROSPECTION_ENDPOINT=https://auth.example.com/oauth/introspect
OIDC_CLIENT_ID=mcp-server-client-id
OIDC_CLIENT_SECRET=mcp-server-client-secret

Server Configuration

SERVER_HOST=127.0.0.1
SERVER_PORT=8000


**ChatGPT Configuration:**```json
{
  "name": "Demo MCP Server",
  "url": "http://127.0.0.1:8000/sse",
  "description": "MCP server with external OIDC",
  "auth": {
    "type": "oauth2",
    "authorization_url": "https://auth.example.com/oauth/authorize",
    "token_url": "https://auth.example.com/oauth/token",
    "client_id": "chatgpt-client-id",
    "client_secret": "chatgpt-client-secret",
    "scope": "openid profile read write"
  }
}

Note: OAuth URLs point to your external provider, not the MCP server!

Provider-Specific Examples

Keycloak```bash

OAUTH_MODE=external
OIDC_INTROSPECTION_ENDPOINT=https://keycloak.example.com/realms/myrealm/protocol/openid-connect/token/introspect
OIDC_CLIENT_ID=mcp-server
OIDC_CLIENT_SECRET=your-secret-here


#### Auth0```bash
OAUTH_MODE=external
OIDC_INTROSPECTION_ENDPOINT=https://yourtenant.auth0.com/oauth/introspect
OIDC_CLIENT_ID=mcp-server-client-id
OIDC_CLIENT_SECRET=your-secret-here

Okta```bash

OAUTH_MODE=external
OIDC_INTROSPECTION_ENDPOINT=https://yourorg.okta.com/oauth2/default/v1/introspect
OIDC_CLIENT_ID=mcp-server-client-id
OIDC_CLIENT_SECRET=your-secret-here


### For Claude Desktop (HTTP/SSE)

In `claude_desktop_config.json`:```json
{
  "mcpServers": {
    "demo-mcp-server": {
      "url": "http://127.0.0.1:8000/sse"
    }
  }
}

For Claude Desktop (Stdio)```json

{
"mcpServers": {
"demo-mcp-server": {
"command": "python",
"args": ["/path/to/server.py", "--transport", "stdio"]
}
}
}


## Available Tools

### list_profiles

Lists all available profiles on the server.

**Parameters:** None

**Returns:** JSON array of profile objects with `profile_id` and `name` fields

**Example response:**```json
[
  {
    "profile_id": "eren",
    "name": "Eren Yeager"
  },
  {
    "profile_id": "mikasa",
    "name": "Mikasa Ackerman"
  }
]

get_titans

Gets titans for a specific profile.

Parameters:
- profile_id (string, required): The profile ID to get titans for

Returns: JSON object with titans for the specified profile

Example success response:```json
{
"profile_id": "eren",
"titans": [
"founding",
"war hammer"
],
"status": "success"
}


**Example error response:**```json
{
  "profile_id": "unknown",
  "status": "error",
  "error": "Profile not found"
}

Demo Data

The server includes demo data with Attack on Titan characters:
- eren - Eren Yeager (founding and war hammer titans)
- mikasa - Mikasa Ackerman (attack titan)

Testing

Test Token Introspection

Use the included test script to validate your OIDC configuration:```bash

Test introspection endpoint

python test_oidc_token.py introspect --token "your-token-here" \
--introspection-url https://auth.example.com/oauth/introspect \
--client-id mcp-server --client-secret secret

Test token with MCP server

python test_oidc_token.py test --token "your-token-here" --server http://127.0.0.1:8000

Test OIDC discovery

python test_oidc_token.py discover --issuer https://auth.example.com


## Customization

Replace the demo data and logic in `server.py`:

1. **`DATA` dictionary** - Replace with your actual data source (database, file, API)
2. **`list_profiles()`** - Modify to return your profile format
3. **`get_titans(profile_id)`** - Modify to return your data format

## Troubleshooting

### Server not connecting
- Check server is running: `curl http://127.0.0.1:8000/sse`
- Verify URL is exactly `http://127.0.0.1:8000/sse`
- Check firewall allows port 8000

### Tools don't appear
- Check server logs for errors
- Tools should work even if not visible in UI
- Try asking directly: "list profiles" or "get titans for eren"

### OAuth/OIDC Issues

#### "Token introspection request timed out"
- Check introspection endpoint URL
- Verify network connectivity
- Check client credentials are correct

#### "Token is not active"
- Token may be expired
- Token may have been revoked
- Check token was issued by the correct provider

#### Authentication failing
- Verify `OIDC_CLIENT_ID` and `OIDC_CLIENT_SECRET` are correct
- Check the introspection endpoint supports basic auth
- Verify your MCP server client has introspection permissions

## OAuth2 Details

### Built-in OAuth Mode

**How it works:**
1. ChatGPT redirects user to `/oauth/authorize`
2. Server auto-approves (demo mode) and returns authorization code
3. ChatGPT exchanges code for access token at `/oauth/token`
4. ChatGPT includes `Bearer {token}` in all MCP requests
5. Server validates token against in-memory storage

**Security Notes:**
- ⚠️ Auto-approval is for demo only - implement proper login/consent in production
- ⚠️ Tokens stored in memory - use database for production
- ⚠️ Use HTTPS for production - set `USE_HTTPS=true` when behind HTTPS proxy/load balancer
- ✓ Client secret is stored in `.env` (not committed to git)

### External OIDC Mode (Token Introspection)

**How it works:**
1. ChatGPT redirects user to external OIDC provider's authorization endpoint
2. User logs in at OIDC provider (supports SSO, MFA, etc.)
3. OIDC provider returns authorization code to ChatGPT
4. ChatGPT exchanges code for access token at OIDC provider
5. ChatGPT includes `Bearer {token}` in all MCP requests to your server
6. Your server validates token via introspection endpoint

**Why Token Introspection:**
- ✅ Works with any token format (JWT or opaque)
- ✅ Real-time token status (can detect revoked tokens immediately)
- ✅ Simpler configuration (no JWKS, audience, or issuer validation)
- ✅ Supports enterprise SSO and MFA (via provider)
- ⚠️ Network call per validation (slightly higher latency than JWT)
- ⚠️ Requires introspection endpoint access

**Security Notes:**
- ✅ Stateless (scales horizontally)
- ✅ Centralized user management
- ✅ Real-time token revocation
- ✅ Works with any OIDC provider
- ⚠️ Use HTTPS for production

**To disable OAuth:**```bash
# In .env file
OAUTH_ENABLED=false

Or simply don't create a .env file.

Comparison: Built-in vs External OIDC

Feature Built-in OAuth External OIDC (Introspection)
Use Case Demo/Development Production/Enterprise
Token Issuer MCP Server External Provider
User Auth Auto-approve (demo) Full login via provider
Token Format Opaque Any (JWT or opaque)
SSO ❌ No ✅ Yes
MFA ❌ No ✅ Yes (via provider)
Token Revocation Manual Real-time
Scalability Limited (in-memory) Excellent (stateless)
Setup Complexity ⭐ Simple ⭐⭐ Moderate
Latency ~0.1ms ~50-100ms

Files

  • server.py - Main MCP server with OAuth support (both modes)
  • generate_credentials.py - OAuth2 credential generator (built-in mode)
  • test_oidc_token.py - OIDC token validation testing tool
  • config.py - Configuration defaults
  • requirements.txt - Python dependencies
  • .env.example - Example environment configuration (built-in mode)
  • .env.external_oidc.example - Example environment configuration (external OIDC)
  • README.md - This file

常见问题

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

在客户端按下面的安装命令接入:pip install -r requirements.txt。装完在客户端配置里引用同一个包或端点。

MCP Demo E60dd8b7 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

MCP Demo E60dd8b7 收费吗?

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

MCP Demo E60dd8b7 需要 API Key 吗?

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

MCP Demo E60dd8b7 能提供哪些能力?

资料显示约 2 个工具;能力标签包括 Python服务器、Python、OAuth认证。具体工具清单以官方文档为准。

MCP Demo E60dd8b7 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

MCP Demo E60dd8b7 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

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

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