awf-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | Optional GitHub token to raise the unauthenticated GitHub API rate limit (60 requests per hour per IP without it). |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_pageA | Fetch a public web page and return clean content plus metadata. Escalation: site adapter API -> HTTP with realistic headers -> client/UA rotation -> AMP/RSS alternates -> headless browser (if installed). Every rung is listed in fetch_attempts. On failure ok=false and blocked_reason explains why (e.g. cloudflare_challenge, captcha, verification_wall, login_required, paywall, rate_limited, not_found, soft_404, js_required). Args: url: page URL (http/https). format: which content field(s) to return. use_browser: auto (only when cheaper rungs fail), never, or always. adapter: auto, none, wechat, github, x. max_chars: truncate content to this many characters (0 = no limit). min_chars: extracted length that counts as success. |
| extract_from_htmlA | Extract main content + metadata from HTML you already have (no network). Useful when the user pasted HTML, or another tool (a browser) already loaded the page. Runs the same block detection and multi-strategy extraction as fetch_page. |
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 distinct input requirements and use cases: fetch_page requires a URL and performs network retrieval plus extraction, while extract_from_html accepts existing HTML and performs extraction only. The descriptions explicitly guide the agent on when to use each, leaving little ambiguity.
Both names use snake_case and begin with a clear verb, but the pattern is not identical: fetch_page is verb_noun, while extract_from_html is verb_from_noun. This minor structural deviation is still readable and consistent overall.
Two tools is minimal for a server whose purpose is web fetching and extraction. While both tools are substantial and earn their place, the surface feels thin compared to typical multi-operation MCP servers.
The server covers the core operations of fetching a page and extracting content from provided HTML, with fetch_page offering escalation and error reporting. Minor gaps exist, such as batch fetching or a dedicated metadata-only tool, but agents can work around them.