A
licenseNot graded
qualityD
maintenanceConverts any webpage into clean, LLM-ready Markdown, removing noise and supporting JavaScript rendering.
MIT
anybrowse
Server Details
Converts any URL to clean, LLM-ready Markdown using real Chrome browsers
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
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- kc23go/anybrowse
- GitHub Stars
- 5
- Server Listing
- Anybrowse
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
5 tool updates
- Added
batch_scrape - Changed
crawl1 field changed- added
Input schema / properties / contextAdded value: +{ + "description": "Optional: what you're trying to accomplish (e.g., 'finding competitors pricing', 'researching market trends'). Helps return more targeted results.", + "type": "string" +}
- Added
extract - Changed
scrape1 field changed- added
Input schema / properties / contextAdded value: +{ + "description": "Optional: what you're trying to accomplish (e.g., 'comparing job salaries', 'researching competitors', 'extracting product prices'). Helps anybrowse return more relevant content.", + "type": "string" +}
- Changed
search1 field changed- added
Input schema / properties / contextAdded value: +{ + "description": "Optional: what you're trying to accomplish. Helps with result relevance.", + "type": "string" +}
5 tool updates
- Removed
batch_scrape - Changed
crawl1 field changed- removed
Input schema / properties / contextRemoved value: -{ - "description": "Optional: what you're trying to accomplish (e.g., 'finding competitors pricing', 'researching market trends'). Helps return more targeted results.", - "type": "string" -}
- Removed
extract - Changed
scrape1 field changed- removed
Input schema / properties / contextRemoved value: -{ - "description": "Optional: what you're trying to accomplish (e.g., 'comparing job salaries', 'researching competitors', 'extracting product prices'). Helps anybrowse return more relevant content.", - "type": "string" -}
- Changed
search1 field changed- removed
Input schema / properties / contextRemoved value: -{ - "description": "Optional: what you're trying to accomplish. Helps with result relevance.", - "type": "string" -}
1 tool update
- Changed
extract3 fields changed- changed
Input schema / properties / context / descriptionPrevious value: -"Optional: what you're trying to accomplish"New value: +"Optional: what you're trying to accomplish (helps LLM extraction accuracy)" - changed
Input schema / properties / schema / additionalProperties / enumPrevious value: -[ - "string", - "number", - "boolean", - "array" -]New value: +[ + "string", + "number", + "boolean", + "array", + "object" +] - changed
Input schema / properties / schema / descriptionPrevious value: -"Field names mapped to types: string, number, boolean, array"New value: +"Field names mapped to type strings. Format: {\"fieldName\": \"string|number|boolean|array|object\"}. Example: {\"title\": \"string\", \"price\": \"number\", \"inStock\": \"boolean\", \"tags\": \"array\"}"
2 tool updates
- Added
batch_scrape - Added
extract
3 tool updates
- Changed
crawl1 field changed- added
Input schema / properties / contextAdded value: +{ + "description": "Optional: what you're trying to accomplish (e.g., 'finding competitors pricing', 'researching market trends'). Helps return more targeted results.", + "type": "string" +}
- Changed
scrape1 field changed- added
Input schema / properties / contextAdded value: +{ + "description": "Optional: what you're trying to accomplish (e.g., 'comparing job salaries', 'researching competitors', 'extracting product prices'). Helps anybrowse return more relevant content.", + "type": "string" +}
- Changed
search1 field changed- added
Input schema / properties / contextAdded value: +{ + "description": "Optional: what you're trying to accomplish. Helps with result relevance.", + "type": "string" +}
1 tool update
- Removed
screenshot
1 tool update
- Added
screenshot
3 tool updates
- First observed
crawl - First observed
scrape - First observed
search
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
Web scraping for AI agents. Converts URLs to clean, LLM-ready Markdown with anti-bot bypass.
Fetch any URL and get clean Markdown. Web scraping for AI agents.
Clean Markdown and AI-readability scoring for any URL. Built for AI agents.
11Screenshot any URL/HTML as PNG/JPEG/WebP, or read it as clean Markdown/text for LLMs.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceConverts URLs into clean, LLM-ready markdown, respecting robots.txt and never bypassing anti-bot measures or paywalls.MIT
- AlicenseAqualityBmaintenanceConverts any URL to clean, LLM-ready Markdown by removing ads, navigation, and other clutter, using Mozilla Readability and Turndown.153MIT
- AlicenseAqualityDmaintenanceConverts URLs and raw HTML to clean Markdown, enabling AI assistants to read web pages for summarization, analysis, or ingestion.2191MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.1/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: batch_scrape handles multiple URLs, crawl combines search and scraping, extract returns structured JSON, scrape converts a single URL to markdown, and search returns search results. There is no meaningful overlap that would confuse an agent.
Naming Consistency3/5
Most tools use single-word verbs (scrape, search, crawl, extract), but batch_scrape uses a prefix, creating a mixed convention. While readable, the naming is not uniformly patterned.
Tool Count5/5
With 5 tools, the set is well-scoped for a scraping/search service, covering single-page scraping, batch scraping, structured extraction, web search, and crawl without unnecessary bloat.
Completeness4/5
The tool surface covers the main workflows: search to find URLs, scrape to fetch content, batch_scrape for efficiency, and extract for structured data. A minor gap is the lack of pagination or status tracking, but these are not critical for typical use cases.