skim
Description
Read any public web page as clean, agent-ready Markdown — typically ~4x smaller than the raw HTML, so your agent burns fewer tokens per read. Skim strips nav, ads, and boilerplate and keeps the article body with title, byline, and publish date. Also does structured JSON extraction and curated intelligence signal feeds.
What our measurements say
skim is a remote MCP server published at skim402.com. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 543 ms, a delay an agent will notice. It offers a narrow, focused set of 3 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tool names explicitly indicate their primary function (read, extract, signals).
- Descriptions clearly define use cases and differentiate between tools.
Weaknesses
- Parameter requirements (e.g., JSON Schema for skim_extract) lack explicit zorunluluk/opsiyonel clarification.
- No explicit error handling documentation for edge cases (e.g., invalid URLs, schema mismatches).
skim_extract— Parameter expectations (preset/JSON Schema) are mentioned but not formally defined in inputSchema.skim_signals— Cost details in description may distract from core functionality without clear error handling for failed polls.
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — era changed from 'auth-gated' to 'legacy' · indicates system transition to legacy mode
- 2026-09-11T09:28:19.138Z — complianceScore improved from null to 100 · shows successful compliance verification
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test not run this round
- Cold-start: cold 158ms → warm 160ms (penalty 0ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 0.1.0
- Supported versions: — → 2025-11-25
- Era changed: Auth-gated → Legacy
- Added to watch — era: Auth-gated
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/hello-jf1i-skim)<a href="https://mcpmetrics.io/servers/hello-jf1i-skim"><img src="https://mcpmetrics.io/badge/hello-jf1i/skim/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see