modelcontextprotocol / modelcontextprotocol/python-sdk
Add wildcard pattern support for `allowed_hosts` in transport security
@pcarleton 已經在處理了。
開始於 2026年3月5日。
- 主要語言
- Python
- 星號
- 24.3k
- 分支
- 4k
- 平均合併
- 1 天 1 小時
- 30 天內合併 PR
- 31
描述
Description
Problem
Currently, the allowed_hosts configuration in TransportSecuritySettings only supports exact string matching link. This is too restrictive for real-world scenarios where you need to allow multiple subdomains under the same parent domain.
For example, if you want to allow app.mysite.com, api.mysite.com, admin.mysite.com, etc., you currently need to list each subdomain explicitly:
allowed_hosts=["app.mysite.com", "api.mysite.com", "admin.mysite.com", ...]
This becomes impractical when you have many subdomains or dynamic subdomain generation.
Proposed Solution
Add wildcard pattern support similar to Starlette's TrustedHostMiddleware or Django's ALLOWED_HOSTS , allowing patterns like:
*.mysite.com- matches any subdomain ofmysite.com(e.g.,app.mysite.com,api.mysite.com) as well as the base domainmysite.comexample.com:*- matchesexample.comwith any port (already supported)
Example Usage
from mcp.server.transport_security import TransportSecuritySettings
settings = TransportSecuritySettings(
enable_dns_rebinding_protection=True,
allowed_hosts=["*.mysite.com", "localhost:*"],
)
I'd be happy to follow up and create a PR.
References
No response
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
評估
這個 Issue 還沒有評估資料。