A
license-
qualityB
maintenanceEnables scraping and fetching websites with protection handling like Cloudflare and captchas, via an MCP interface.
23
1
Apache 2.0
cloudflare-solver
by com.jojapi
Server Details
Cloudflare Solver: Scraping API designed to bypass Cloudflare protection.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
B3.4/5.0
Tool DescriptionsA
Average 3.8/5 across 1 of 1 tools scored.
Server CoherenceC
Disambiguation2/5
With only one tool there is nothing to disambiguate, so ambiguity is trivial. However, the tool's name 'post_get_page_source' confuses its own purpose by mixing POST and GET semantics, making it unclear what the tool actually does without reading the description.
Naming Consistency2/5
A single tool name cannot establish a consistent pattern across tools, but the name itself is internally inconsistent, combining 'post' and 'get' prefixes which suggest conflicting conventions. The snake_case styling is fine, but the contradictory verb choices lower the score.
Tool Count3/5
A single tool feels thin for a server named 'cloudflare-solver', since solving Cloudflare challenges typically involves more than just fetching page source. However, one tool can be acceptable for a narrowly defined purpose, placing it right at the borderline.
Completeness2/5
The server only fetches page source, which is a minimal subset of what a Cloudflare-solving tool should do. Missing crucial capabilities like handling cookies, solving interactive challenges, setting headers, or retrying, making the server likely to hit dead ends on real-world tasks.
Available Tools
1 toolpost_get_page_sourceGet page sourceAInspect
Fetches and returns page source of provided url. Billing per call: 1 Credits.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No |
Tool Definition Quality
A3.8/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses the primary behavior (fetching and returning page source) and mentions billing. However, it does not mention potential side effects, error handling, rate limits, or whether it is read-only. Given no annotations, more transparency could be provided.
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?
The description is extremely concise and well-structured, containing only essential information in two short sentences. No wasted words.
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?
For a simple tool with one parameter and no output schema, the description adequately states what it returns ('page source') and the billing cost. It could be more complete by mentioning error cases or encoding, but it is sufficient for basic understanding.
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?
The schema provides the parameter 'url' with type and example. The description adds minimal meaning by restating 'of provided url,' which is already implied by the parameter name. Baseline is 3 due to full schema coverage, and no significant additional semantics are added.
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 clearly states the tool's function: 'Fetches and returns page source of provided url.' This is a specific verb and resource, leaving no ambiguity about 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 description implies usage (when you need the page source of a URL) but does not explicitly state when to use it over alternatives or provide any exclusions. Since there are no sibling tools, this is acceptable but not fully explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
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
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 Servers
- Alicense-qualityBmaintenanceOpen-source browser automation API with anti-detection for AI agents, web scraping, and automation, providing undetectable Chrome via MCP and REST API with Cloudflare bypass.9MIT
sessemi-mcpofficial
AlicenseAqualityDmaintenanceEnables AI agents to scrape websites protected by Cloudflare, DataDome, and Akamai, bypassing anti-bot measures to retrieve page content.2MIT- AlicenseAqualityAmaintenanceEnables web scraping, structured data extraction, and screenshot capture with automatic anti-bot bypass, supporting JavaScript rendering, proxy rotation, and tiered pricing.251871MIT