All public server reports

Endpoint report / Metadata + smoke test

Cloudflare Docs MCP

A dated endpoint inspection. Metadata and any separately recorded tool call have their own evidence, scope and limitations.

Developer documentationRunner 1.1.0

What this establishes

The anonymous endpoint advertised 2 tools and passed four bounded metadata checks. A separate, fixed read-only smoke scenario is recorded below. Actual ChatGPT and Claude workflows were not tested.

The smoke result applies only to the displayed call and literal content assertions. It does not establish overall answer correctness or reliability.

Connection and metadata
Metadata checks passed
Observed tool catalog
Complete: 2 tools
Read-only smoke test
Passed · 1 call attempted
ChatGPT / Claude
Not tested / Not tested
Overall score
Not assigned

Read-only smoke test / Passed

Find Cloudflare's public documentation for a Workers fetch handler.

This is one direct, fixed-input tool test. It does not exercise an AI model or a ChatGPT or Claude session. Calls attempted may include a call that returned an error or timed out.

The response passed the registered content assertions.

Smoke tool calls attempted
1
Tool
search_cloudflare_documentation
Scenario / version
cloudflare-workers-docs / 1
Observed at
2026-10-15T07:18:20.633Z
Runner
1.0.0
Protocol
2025-11-25
Elapsed time
9480 ms
Run ID
6c468a1e-fff4-45b9-831d-50aadd46d313
Result SHA-256
ccef0c8d1c0e37a98dfda62fe18cbd49c22dc8c59db2449c3c2252aef039e043

Exact public inputs

{
  "query": "Cloudflare Workers fetch handler"
}

Fixture assertions

  • fetch: Passed
  • workers: Passed
Recorded response excerpt
<result>
<url>https://developers.cloudflare.com/workers/languages/python/basics/</url>
<title>Basics</title>
<text>
---
title: The Basics
description: Learn the basics of Python Workers
image: https://developers.cloudflare.com/dev-products-preview.png
---

> Documentation Index  
> Fetch the complete documentation index at: https://developers.cloudflare.com/workers/llms.txt  
> Use this file to discover all available pages before exploring further. 

[Skip to content](#%5Ftop) 

# The Basics

## Fetch Handler

As mentioned in the [introduction to Python Workers](/workers/languages/python/), a Python Worker can be as simple as four lines of code:

Python

```
from workers import WorkerEntrypoint, Response
class Default(WorkerEntrypoint):    async def fetch(self, request):        return Response("Hello World!")
```

Similar to other Workers, the main entry point for a Python worker is the [fetch handler](/workers/runtime-apis/handlers/fetch) which handles incoming requests sent to the Worker.

In a Python Worker, this handler is placed in a `Default` class that extends the `WorkerEntrypoint` class (which you can import from the `workers` SDK module).

## The `Request` Interface

The 
  • One fixed public read-only request from a direct MCP client. No model selection, ChatGPT/Claude host, OAuth, private account or write behavior was tested.
  • Content assertions check the listed literal terms and absence of a tool error; they do not establish complete factual correctness, relevance or production reliability.
  • Observed call duration is one sample and includes network conditions. It is not a latency benchmark or a comparison between services.
  • Only the first tools/list page is inspected for this selected tool. No notification stream, redirect, credentials or caller-supplied scenario is allowed.
  • Response SHA-256 covers the UTF-8 JSON serialization of the SDK-parsed tool result. Only a bounded public text excerpt is retained; it is untrusted server content.

Recorded checks

These checks cover the metadata inspection. They are separate from the tool-call result above, when present.

protocol-negotiation

Negotiated protocol 2025-11-25; this does not establish host compatibility.

Passed

initialized-notification

The initialization notification received HTTP 202 with an empty body.

Passed

tool-catalog

Observed the complete advertised catalog: 2 tools across 1 pages.

Passed

tool-metadata-shape

SDK metadata shape checked for 2 observed tools. This is not complete JSON Schema validation or behavior verification.

Passed

oauth-login

OAuth discovery, login, token refresh and authenticated access are outside this anonymous inspection.

Not tested

Metadata request evidence

request-1 / initialize

2026-10-15T07:11:36.570Z

HTTP 200 · 369 ms · 224 B

response-received

request-2 / notifications/initialized

2026-10-15T07:11:36.939Z

HTTP 202 · 15 ms · 0 B

notification-accepted

request-3 / tools/list

2026-10-15T07:11:36.954Z

HTTP 200 · 18 ms · 1860 B

response-received

Observed tool catalog

Names were advertised through tools/list. Any tool execution is recorded separately in the smoke test section.

Complete: 2 tools
  • migrate_pages_to_workers_guide
  • search_cloudflare_documentation

Endpoint and provenance

Endpoint
https://docs.mcp.cloudflare.com/mcp
Official source
https://developers.cloudflare.com/agents/model-context-protocol/mcp-servers-for-cloudflare/
Profile
Anonymous endpoint profile
Requested protocol
2025-11-25
Reported protocol
2025-11-25
Protocol
2025-11-25
Observed at
2026-10-15T07:11:36.978Z
Run ID
3227f663-546c-40b3-85eb-b02c0f19351f
Catalog SHA-256
73a71bc7e7c992186b518bdd19debbd387ffb80cc13508d0b489c76e1000cab7
Fingerprint scope
complete-catalog

SHA-256 of all observed tool objects, recursively sorted object keys and sorted canonical tool strings; schema array order is preserved. Raw descriptions, schemas and headers are not persisted.

Inspection bounds
requestTimeoutMs
5,000
runTimeoutMs
30,000
responseBytes
1,048,576
requests
7
pages
5
tools
200
Read the full methodology (English Markdown)

What this report does not establish

These observations do not establish general task success, security, OAuth behavior or ChatGPT and Claude compatibility. Read the limits of each recorded test.

  • Metadata-only anonymous inspection. No tools/call, OAuth flow, API model calls, host UI or publication review was executed. No global quality or safety score is produced.
  • Annotations are server declarations, not verified behavior. Metadata success does not establish task success, security, usefulness or ChatGPT/Claude compatibility.
  • Only active exact HTTPS endpoints in the reviewed source registry are accepted. Redirects, supplied credentials, arbitrary endpoints and OAuth URL fetching are disabled. DNS/TLS use the local runtime: this is not a hardened multi-tenant SSRF sandbox and must not be exposed as a public scanner.
  • Session identifiers are used only in memory. Request/response headers, raw error messages, raw descriptions and schemas are excluded from artifacts. Tool names and aggregate metadata remain untrusted server input.
  • Only the recorded protocol versions and bounded catalog prefix are supported. Reaching a bound or lacking access means unknown, not a failed server or a passing full audit.

What should your MCP do better?

Share a public endpoint or repository, the tasks that matter, and the clients your users use. We will discuss a pilot scope, access and price.

Discuss a benchmark

Opens your email app. Send public links only; arrange sandbox access separately.

Was this helpful?

Anonymous feedback helps us improve pages and translations.