baseline-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_BASE_URL | No | Base URL for the webstatus.dev API | https://api.webstatus.dev |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_web_feature_baseline_statusC | Get comprehensive baseline information for web platform features |
| get_baseline_summaryA | Get overview of the Baseline system and status categories |
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 2 tools
The two tools have clearly distinct purposes: one provides a system overview and status categories, the other gives detailed baseline information for web features. No overlap.
Both tools follow a consistent 'get_[specific]_[modifier]' pattern, making it easy for an agent to understand their actions.
With only two tools, the server is quite minimal but may be appropriate if the domain is limited to read-only access. However, it is borderline for a typical MCP server scope.
The tools cover a system overview and specific feature status, but lack any mutating operations or additional resource listing. For a server about baselines, missing create/update/delete is a notable gap.