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 还没有评估数据。