fetch-url-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Bind address for the HTTP server. Defaults to 0.0.0.0. | 0.0.0.0 |
| PORT | No | Listen port for the HTTP server. Defaults to 8080. | 8080 |
| VYBE_ORIGIN | No | Collect API origin. Defaults to https://www.vybe.finance. | https://www.vybe.finance |
| ALLOW_PRIVATE | No | Set to '1' to allow fetching localhost/private IPs. Should never be used in production. | |
| VYBE_USERNAME | No | Your Collect @username without '@'. Required only for Path C (SKU wrapper). | |
| VYBE_OFFERING_ID | No | Offering id from the desk, e.g. svc_…. Required only for Path C (SKU wrapper). |
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 |
|---|---|
| fetch_urlA | Fetch a public http(s) URL and return readable plain text (HTML stripped). Use for pages, docs, blog posts. |
| fetch_jsonA | Fetch a public http(s) URL that returns JSON and pretty-print it. Use for public APIs. |
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 are clearly distinguished by output type and use case: one returns readable plain text, the other pretty-printed JSON. The names themselves signal the difference, so there is minimal risk of selecting the wrong tool.
Both tool names follow the same verb_noun snake_case pattern: fetch_url and fetch_json. The naming is predictable, concise, and exactly matches each tool's function.
Two tools is slightly below the typical 3-15 range, but for the narrow purpose of fetching public URLs, the count is reasonable. Each tool earns its place, and adding more would likely inflate the surface unnecessarily.
The tool set covers the two most common URL-fetching needs: human-readable content and JSON APIs. It lacks support for binary content or raw HTML, but that appears beyond the server's stated scope, so the coverage is adequate with only minor gaps.