py-har-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| load_harA | 从文件路径或 HTTP URL 加载 HAR 文件，并保存为默认分析数据集。 |
| list_urls_methodsA | 列出 HAR 中访问过的所有 URL 与 HTTP 方法组合。 |
| get_request_idsA | 根据指定 URL 与 HTTP 方法，返回匹配的请求 ID 列表。 |
| get_request_detailsA | 根据请求 ID 获取完整请求详情，并自动脱敏认证相关请求头。 |
| get_domain_statsA | 按域名汇总请求统计信息，包括请求方法和状态码分布。 |
| get_status_code_statsB | 按 HTTP 状态码汇总请求统计信息。 |
| search_harA | 在 HAR 中搜索请求头、响应头、请求体和响应体内容。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clear, distinct purpose: loading data, listing URL/method combos, filtering request IDs, fetching request details, aggregating by domain or status code, and searching content. No two tools overlap in function.
All tool names follow a consistent verb_noun pattern: load_har, list_urls_methods, get_request_ids, get_request_details, get_domain_stats, get_status_code_stats, search_har. The verbs are uniform and descriptive.
With 7 tools, the set is well-scoped for HAR analysis. Each tool covers a distinct aspect of the workflow, and the count is neither sparse nor bloated.
The surface covers the main HAR analysis workflow: load, browse, filter, inspect, search, and statistics. A minor gap is the absence of a direct 'get all requests' tool, but this can be worked around by combining list_urls_methods with get_request_ids.