stripfeed-mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STRIPFEED_API_KEY | Yes | Your StripFeed API key. Sign up at stripfeed.dev to obtain one. Keys typically start with sf_live_. |
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 | Convert any URL to clean, token-efficient Markdown. Strips ads, navigation, scripts, and noise. Returns clean content ready for LLM consumption. |
| batch_fetchB | Fetch multiple URLs in parallel and convert them all to clean Markdown. Process up to 10 URLs in a single call. |
| check_usageA | Check your current monthly API usage and plan limits. |
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 3 tools
fetch_url and batch_fetch both convert URLs to Markdown but differ in batching, which is clear from names and descriptions. check_usage is distinct for usage tracking. Minor ambiguity between fetch_url and batch_fetch could exist, but descriptions clarify.
All tools use a consistent verb_noun pattern (fetch_url, batch_fetch, check_usage). No mixed casing or inconsistent verb styles.
3 tools is well-scoped for a URL-to-Markdown conversion service dashboard. Each tool serves a clear purpose: single fetch, batch, and usage monitoring. No excessive or redundant tools.
The set covers core fetching (single and batch) and usage checking, but lacks obvious lifecycle operations like cancellation, status, or configuration of output options. For a simple converter, it may be adequate, but missing a way to customize output or manage preferences is a notable gap.