A
licenseNot graded
qualityC
maintenanceEnables clean, LLM-ready markdown extraction from any URL with automatic anti-bot bypass.
3
MIT
CleanText
Server Details
Extract clean article text or Markdown from any public web page; ads and boilerplate stripped.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
A3.7/5.0
Scored across 1 tool
Disambiguation5/5
There is only one tool, so there is no possibility of misselection or overlap. An agent cannot confuse `extract` with anything else on this server.
Naming Consistency4/5
The single name `extract` is a clear, lowercase verb that reads well and matches the server's action-oriented purpose. A one-tool surface gives no pattern to verify, so it cannot earn the top score, but nothing is inconsistent.
Tool Count3/5
The server's scope is narrow (strip boilerplate from a page), so one tool is defensible, but a single tool still feels thin for a whole server. Practical extras like batch extraction or output-format selection are absent.
Completeness3/5
Core capability (fetch + clean article text/Markdown) is covered, but the surface has notable gaps: no batch/multi-URL extraction, no choice of output length or format parameters, and no way to retrieve page metadata or diagnose failed extractions.
Available Tools
1 toolextractExtract page textAInspect
Fetch a public web page and return its main article text or Markdown (nav, ads and boilerplate stripped).
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Absolute http(s) URL of the page | |
| format | No | markdown |
TDQS
A3.6/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden. It discloses public-page scope, boilerplate stripping, and text/Markdown output, but does not cover error behavior, rate limits, dynamic pages, paywalls, or authentication boundaries.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence states the fetch, the return value, and the stripping behavior. Every phrase is relevant and nothing is padded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema and no annotations, so the description must explain return behavior and constraints. It does so at a high level for text/Markdown and boilerplate stripping, but omits the json format and failure/edge cases, leaving gaps for an agent to infer.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 50%, so the description should compensate for the undocumented format parameter. It mentions text or Markdown but omits the schema's json option and does not clarify what json returns, leaving the parameter only partially explained.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action and resource: fetch a public web page and return its main article text or Markdown. It also clarifies the transformation via boilerplate stripping, so an agent can tell exactly what the tool does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The 'public web page' and 'main article text' wording implies use for public article extraction, but there is no explicit when-not guidance or alternative tool to compare against. The public-only constraint is a useful prerequisite but falls short of full usage routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
extract
Related MCP Connectors
Turn any web page URL or HTML into clean Markdown or plain text for an LLM to read.
Convert any webpage to clean LLM-ready markdown, extraction-first, with article and news modes.
Read any public web page as clean Markdown for LLMs. Respects robots.txt. Free tier; x402 paid API.
Link-preview metadata and clean page-to-Markdown for any public URL. No install.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceConverts any webpage into clean, LLM-ready Markdown, removing noise and supporting JavaScript rendering.MIT
- AlicenseAqualityDmaintenanceConverts URLs and raw HTML to clean Markdown, enabling AI assistants to read web pages for summarization, analysis, or ingestion.25 npm1MIT
- FlicenseNot gradedqualityDmaintenanceFetches webpages and returns clean, structured Markdown with metadata (title, author, publish date, description, domain, word count).1-
Try in Browser
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd
Glama MCP Gateway
Add one secure layer between your agents and this server.