A
licenseA
qualityD
maintenanceConverts URLs and raw HTML to clean Markdown, enabling AI assistants to read web pages for summarization, analysis, or ingestion.
2
19
1
MIT
Stringer CleanExtract
Server Details
Convert public HTML or a public URL into token-dense Markdown through one remote MCP tool.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Available Tools
1 toolclean_extractAInspect
Extract clean, token-dense markdown from a public URL or raw HTML string, with extraction_status and detailed extraction_quality metadata that identifies empty or probably partial output. The first 3 calls per source IP are free, total, with no header or signup needed; the allowance does not reset. Every later extraction costs USD 0.05 via x402.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url_or_html | Yes | A public HTTP(S) URL or a raw HTML string to convert into Markdown. | |
| max_output_bytes | No | Optional maximum UTF-8 byte length of the returned Markdown. |
TDQS
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden and does well: it discloses output quality metadata, indicates that empty or partial output may be flagged, and explicitly describes the free allowance and per-call cost. It does not detail error behavior or exact response structure, but the core behavioral traits are covered.
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?
Two sentences carry the entire message with zero filler. The primary purpose is front-loaded, followed by the most decision-relevant operational detail (pricing/free allowance). Every clause earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and no annotations, the description supplies the key context agents need: input type, output nature, quality metadata, and cost model. It could go slightly deeper on response shape or error handling, but for a 2-parameter extraction tool it is largely complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description echoes the meaning of the first parameter (public URL or raw HTML) but adds no new meaning beyond the schema. The optional max_output_bytes parameter is not mentioned, though its schema description already explains it.
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 names a specific verb ('Extract'), a concrete resource type ('public URL or raw HTML string'), and the exact expected output ('clean, token-dense markdown') plus return metadata. It fully clarifies what the tool does, even without sibling tools to differentiate from.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It clearly states when this tool is appropriate: converting public URLs or raw HTML to Markdown. It also gives practical usage context—first 3 calls free, later calls paid—which helps an agent decide whether to call it repeatedly. It does not mention alternatives, but there are no sibling tools to contrast against.
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. Dates show when Glama detected each change.
1 tool update
- Removed
diagnose_extraction
1 tool update
- Added
diagnose_extraction
1 tool update
- Changed
clean_extract1 field changed- added
Input schema / properties / max_output_bytesAdded value: +{ + "description": "Optional maximum UTF-8 byte length of the returned Markdown.", + "maximum": 1048576, + "minimum": 1, + "type": "integer" +}
1 tool update
- Changed
clean_extract3 fields changed- added
Input schema / additionalPropertiesAdded value: +false - changed
Input schema / properties / url_or_html / descriptionPrevious value: -"The public URL or raw HTML string to convert into markdown."New value: +"A public HTTP(S) URL or a raw HTML string to convert into Markdown." - added
Input schema / properties / url_or_html / minLengthAdded value: +1
1 tool update
- First observed
clean_extract
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Convert files, URLs, and documents to clean, AI-ready Markdown via MCP.
Fetch a URL and get clean Markdown with metadata. No API key required; rate-limited per IP.
Converts any URL to clean, LLM-ready Markdown using real Chrome browsers
Fetch any URL and get clean Markdown. Web scraping for AI agents.
Related MCP Servers
- FlicenseAqualityCmaintenanceEnables converting web pages to clean Markdown via MCP, compressing token usage by roughly 95% in under 150ms to support LLM context windows and RAG pipelines.2-
- AlicenseNot gradedqualityCmaintenanceConverts URLs into clean, LLM-ready markdown, respecting robots.txt and never bypassing anti-bot measures or paywalls.MIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI clients to extract live web content and convert it into structured Markdown for LLM ingestion, RAG pipelines, and agentic workflows.-
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.3/5.0
Disambiguation5/5
There is only one tool, so no agent could confuse it with another. The single operation has a clear and narrow boundary.
Naming Consistency5/5
The tool name 'clean_extract' follows a clear verb_noun pattern and accurately describes what the server does. With one tool, the naming is predictable and unambiguous.
Tool Count3/5
One tool is minimal and feels thin, even if the server's extraction purpose is narrow. It is not bloated, but it falls below the typical well-scoped 3-15 tool range.
Completeness5/5
The tool accepts both a public URL and raw HTML, returns extraction status and quality metadata, and addresses the full stated purpose of clean extraction. There are no obvious missing operations for this focused service.