← Back to search
com.cloudflare.mcp/mcp

com.cloudflare.mcp/mcp

Cloudflare MCP servers

Status
Healthy
Score
74.9
Transport
streamable-http
Tools
2

Production readiness

Verdict
Needs remediation
Current validation evidence shows operational or discovery gaps that should be fixed first.
Critical alerts
0
Production verdicts degrade quickly when critical alerts are active.

Evidence confidence

Confidence score
65.0
Based on 20 recent validations, 26 captured checks, and validation age of 605.4 hours.
Live checks captured
26
More direct checks increase trust in the current verdict.
Validation age
605.4h
Lower age means fresher evidence.

Recommended for

Claude Desktop
Claude Desktop is marked compatible with score 100.
Smithery
Smithery is marked compatible with score 100.
Generic Streamable HTTP
Generic Streamable HTTP is marked compatible with score 100.

Client readiness verdicts

Ready for ChatGPT custom connector
Partial
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.
Confidence: medium (65.0)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initializeOK
  • tools_listOK
  • transport_compliance_probeWarning
  • step_up_auth_probeMissing
  • connector_replay_probeOK — Frozen tool snapshots must survive refresh.
  • request_association_probeMissing — Roots, sampling, and elicitation should stay request-scoped.
Ready for Claude remote MCP
Ready
No major blockers detected.
Confidence: medium (65.0)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initializeOK
  • tools_listOK
  • transport_compliance_probeWarning
Unsafe for write actions
Yes
High-risk write, exec, or destructive tools need stronger auth and confirmation semantics.
Confidence: medium (65.0)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history
Disagreements: none
  • action_safety_probeError
Snapshot churn risk
Low
No material tool-surface churn detected in the latest comparison.
Confidence: medium (65.0)
Evidence provenance
Winner: history
Supporting sources: history, live_validation
Disagreements: none
  • tool_snapshot_probeOK
  • connector_replay_probeOK

Why not ready by client

ChatGPT custom connector
Partial
Remediation checklist
  • No explicit blockers recorded.
Claude remote MCP
Ready
Remediation checklist
  • No explicit blockers recorded.
Write-safe publishing
Blocked
Remediation checklist
  • No explicit blockers recorded.

Verdict traces

Production verdict
Needs remediation
Current validation evidence shows operational or discovery gaps that should be fixed first.
Confidence: medium (65.0)
Winning source: live_validation
Triggering alerts
  • validation_stale • medium • Validation evidence is stale
Client verdict trace table
VerdictStatusChecksWinning sourceConflicts
openai_connectors Partial initialize, tools_list, transport_compliance_probe, step_up_auth_probe, connector_replay_probe, request_association_probe live_validation none
claude_desktop Ready initialize, tools_list, transport_compliance_probe live_validation none
unsafe_for_write_actions Yes action_safety_probe live_validation none
snapshot_churn_risk Low tool_snapshot_probe, connector_replay_probe history none

Publishability policy profiles

ChatGPT custom connector publishability
Caution
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.
  • Search Fetch Only: No
  • Write Actions Present: Yes
  • Oauth Configured: No
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No
Claude remote MCP publishability
Ready
Transport, discovery, and remote-MCP assumptions are satisfied.
  • Search Fetch Only: No
  • Write Actions Present: Yes
  • Oauth Configured: No
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No

Compatibility fixtures

ChatGPT custom connector fixture
Degraded
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.
  • remote_http_endpoint: Passes
  • oauth_discovery: Degraded
  • frozen_tool_snapshot_refresh: Passes
  • request_association: Passes
Anthropic remote MCP fixture
Passes
Remote MCP transport and discovery assumptions are satisfied.
  • remote_transport: Passes
  • tool_discovery: Passes
  • auth_connect: Passes
  • safe_write_review: Degraded

Authenticated validation sessions

Latest profile
remote_mcp
Authenticated session used
Public score isolation
Preview endpoint
/v1/verify
CI preview endpoint
/v1/ci/preview

Public server reputation

Validation success 7d
n/a
Validation success 30d
1.0
Mean time to recover
n/a
Breaking diffs 30d
0
Registry drift frequency 30d
0
Snapshot changes 30d
0

Incident & change feed

TimestampEventDetails
Apr 09, 2026 12:28:45 AM UTC Latest validation: healthy Score 74.9 with status healthy.

Capabilities

Use-case taxonomy
database search productivity web

Security posture

Tools analyzed
2
High-risk tools
1
Destructive tools
0
Exec tools
1
Egress tools
0
Secret tools
0
Bulk-access tools
0
Risk distribution
medium:1, high:1

Tool capability & risk inventory

ToolCapabilitiesRiskFindingsNotes
search_cloudflare_documentation read write exec network admin High command execution freeform input surface admin mutation No explicit safeguard hints detected.
migrate_pages_to_workers_guide read admin Medium none No explicit safeguard hints detected.

Write-action governance

Governance status
Error
Safe to publish
Auth boundary
public_or_unclear
Blast radius
Medium
High-risk tools
1
Confirmation signals
none
Safeguard count
0

Status detail: 1 high-risk tool(s), 1 exec-capable tool(s) are exposed without a clear auth boundary; no safeguards or confirmation signals detected.

ToolRiskFlagsSafeguards
search_cloudflare_documentation High command execution freeform input surface admin mutation no

Action-controls diff

Snapshot changed
no
Disabled-by-default candidates
none
Manual review candidates
none
New actions
ActionRiskFlags
No newly added actions.
Changed actions
ActionChange typesRisk
No materially changed actions.

Why this score?

Access & Protocol
32/44
Connectivity, auth, and transport expectations for common clients.
Interface Quality
37.12/56
How well the tool/resource interface communicates and behaves under automation.
Security Posture
27.25/36
How safely the exposed tool surface handles destructive actions, egress, execution, secrets, and risky inputs.
Reliability & Trust
24/24
Operational stability, consistency, and trustworthiness over time.
Discovery & Governance
21.5/28
How well the server is documented, listed, and governed in public registries.
Adoption & Market
5/8
Adoption clues and public evidence that the server is intended for external use.

Algorithmic score breakdown

Auth Operability
2/4
Measures whether auth discovery and protected access behave predictably for clients.
Error Contract Quality
2.1/4
Grades machine-readable error structure, status alignment, and remediation hints.
Rate-Limit Semantics
2/4
Checks whether quota/throttle responses are deterministic and automation-friendly.
Schema Completeness
2/4
Completeness of tool descriptions, parameter docs, examples, and schema shape.
Backward Compatibility
4/4
Stability score across tool schema/name drift relative to prior validations.
SLO Health
4/4
Availability, latency, and burst-failure profile across recent validation history.
Security Hygiene
2.5/4
HTTPS posture, endpoint hygiene, and response-surface hardening checks.
Task Success
4/4
Can an agent reliably initialize, enumerate tools, and execute core MCP flows?
Trust Confidence
4/4
Confidence-adjusted reliability score that penalizes low evidence volume.
Abuse/Noise Resilience
4/4
How well the server preserves core behavior in the presence of noisy traffic patterns.
Prompt Contract
2/4
Quality of prompt metadata, argument shape, and prompt discoverability for clients.
Resource Contract
2/4
How completely resources and resource templates describe URIs, types, and usage shape.
Discovery Metadata
2/4
Homepage, docs, icon, repository, support, and license coverage for directory consumers.
Registry Consistency
2/4
Agreement between stored registry metadata, live server-card data, and current validation output.
Installability
4/4
How cleanly a real client can connect, initialize, enumerate tools, and proceed through auth.
Session Semantics
4/4
Determinism and state behavior across repeated MCP calls, including sticky-session surprises.
Tool Surface Design
3/4
Naming clarity, schema ergonomics, and parameter complexity across the tool surface.
Result Shape Stability
3/4
Stability of declared output schemas across validations, with penalties for drift or missing shapes.
OAuth Interop
3/4
Depth and client compatibility of OAuth/OIDC metadata beyond the minimal protected-resource check.
Recovery Semantics
0/4
Whether failures include actionable machine-readable next steps such as retry or upgrade guidance.
Maintenance Signal
4/4
Versioning, update recency, and historical validation cadence that indicate active stewardship.
Adoption Signal
2/4
Directory presence and distribution clues that suggest the server is intended for external use.
Freshness Confidence
4/4
Confidence that recent validations are current enough and dense enough to trust operationally.
Transport Fidelity
4/4
Whether declared transport metadata matches the observed endpoint behavior and response formats.
Spec Recency
2/4
How close the server’s claimed MCP protocol version is to the latest known public revision.
Session Resume
3/4
Whether Streamable HTTP session identifiers and resumed requests behave cleanly for real clients.
Step-Up Auth
3/4
Whether OAuth metadata and WWW-Authenticate challenges support granular, incremental consent instead of broad upfront scopes.
Transport Compliance
2/4
Checks session headers, protocol-version enforcement, session teardown, and expired-session behavior.
Utility Coverage
3/4
Signals support for completions, pagination, and task-oriented utility surfaces that larger clients increasingly expect.
Advanced Capability Coverage
3/4
Coverage of newer MCP surfaces like roots, sampling, elicitation, structured output, and related metadata.
Connector Publishability
3/4
How ready the server looks for client catalogs and managed connector programs.
Tool Snapshot Churn
4/4
Stability of the tool surface across recent validations, including add/remove and output-shape drift.
Connector Replay
4/4
Whether a previously published frozen connector snapshot would remain backward compatible after the latest tool refresh.
Request Association
3/4
Whether roots, sampling, and elicitation appear tied to active client requests instead of arriving unsolicited on idle sessions.
Interactive Flow Safety
4/4
Whether prompts and docs steer users toward safe auth flows instead of pasting secrets directly.
Action Safety
2/4
Risk-weighted view of destructive, exec, egress, and confirmation semantics across the tool surface.
Official Registry Presence
4/4
Whether the server appears directly or indirectly in the official MCP registry.
Provenance Divergence
4/4
How closely official registry metadata, the live server card, and public repo/package signals agree with each other.
Safety Transparency
3/4
Clarity of docs, auth disclosure, support links, and other trust signals visible to integrators.
Tool Capability Clarity
3/4
How clearly the tool surface communicates whether each action reads, writes, deletes, executes, or exports data.
Destructive Operation Safety
3/4
Penalizes delete/revoke/destroy style tools unless auth and safeguards reduce blast radius.
Egress / SSRF Resilience
3/4
Assesses arbitrary URL fetch, crawl, webhook, and remote-request exposure on the tool surface.
Execution / Sandbox Safety
3.8/4
Evaluates shell, code, script, and command-execution exposure and whether that surface appears contained.
Data Exfiltration Resilience
3/4
Assesses export, dump, backup, and bulk-read behavior against the surrounding auth and safeguard signals.
Least Privilege Scope
2/4
Rewards scoped auth metadata and penalizes broad or missing scopes around privileged tools.
Secret Handling Hygiene
3/4
Assesses secret-bearing tools, token leakage risk, and whether the public surface avoids obvious secret exposure.
Supply Chain Signal
2.5/4
Public metadata signal for repository, changelog, license, versioning, and recency that supports supply-chain trust.
Input Sanitization Safety
3/4
Penalizes risky freeform string inputs when schemas do not constrain URLs, code, paths, queries, or templates.
Tool Namespace Clarity
4/4
Measures naming uniqueness and ambiguity across the tool namespace to reduce collision and confusion risk.

Compatibility profiles

OpenAI Connectors
77.8
partial
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.
Connector URL: https://docs.mcp.cloudflare.com/mcp
# No OAuth metadata detected.
# Server: com.cloudflare.mcp/mcp
Claude Desktop
100.0
compatible
No major blockers detected.
{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://docs.mcp.cloudflare.com/mcp"]
    }
  }
}
Smithery
100.0
compatible
No major blockers detected.
smithery mcp add "https://docs.mcp.cloudflare.com/mcp"
Generic Streamable HTTP
100.0
compatible
No major blockers detected.
curl -sS https://docs.mcp.cloudflare.com/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Actionable remediation

SeverityRemediationWhy it mattersRecommended action
High Add confirmation and dry-run semantics for risky actions High-risk write, delete, exec, or egress tools should communicate safeguards clearly. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
High Align session and protocol behavior with Streamable HTTP expectations Clients increasingly rely on MCP-Protocol-Version, session teardown, and expired-session semantics. Align MCP-Protocol-Version, MCP-Session-Id, DELETE teardown, and expired-session handling with the transport spec.
Playbook
  • Return `Mcp-Session-Id` and `Mcp-Protocol-Version` headers consistently on streamable HTTP responses.
  • Honor `DELETE` session teardown and return `404` when a deleted session is reused.
  • Reject invalid protocol-version headers with `400 Bad Request`.
High Associate roots, sampling, and elicitation with active client requests Modern MCP guidance expects roots, sampling, and elicitation traffic to be tied to an active client request instead of arriving unsolicited on idle sessions. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
High Expose /.well-known/oauth-protected-resource Without a protected-resource document, OAuth clients cannot discover auth requirements reliably. Serve /.well-known/oauth-protected-resource and point it at your authorization server metadata.
Playbook
  • Serve `/.well-known/oauth-protected-resource` from the same host as the MCP endpoint.
  • Point it at the authorization server metadata URL.
  • Confirm clients receive consistent auth hints before tool execution.
High Publish OAuth authorization-server metadata Clients need authorization-server metadata to discover issuer, endpoints, and DCR support. Publish /.well-known/oauth-authorization-server from your issuer and include registration_endpoint when supported.
Playbook
  • Publish `/.well-known/oauth-authorization-server` from the issuer.
  • Add `registration_endpoint` if DCR is supported.
  • Verify issuer, authorization, token, and jwks metadata are all reachable.
High Publish a complete server card Missing or incomplete server-card metadata weakens discovery, documentation, and trust signals. Serve /.well-known/mcp/server-card.json and include tools, prompts/resources, homepage, and support links.
Playbook
  • Publish `/.well-known/mcp/server-card.json`.
  • Include homepage, repository, support, tools, prompts/resources, and auth metadata.
  • Revalidate the server after publishing the card.
Medium Adopt a current MCP protocol revision Older protocol revisions reduce compatibility with newer clients and registry programs. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Close connector-publishing gaps Connector catalogs care about protocol recency, session behavior, auth clarity, and tool-surface stability. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Document minimal scopes and return cleaner auth challenges Modern clients expect granular scopes and step-up auth signals such as WWW-Authenticate scope hints. Return granular scopes and WWW-Authenticate challenge hints instead of forcing overly broad auth upfront.
Playbook
  • Advertise the narrowest viable scopes in OAuth metadata.
  • Return `WWW-Authenticate` challenges with scope or insufficient-scope hints when additional consent is needed.
  • Revalidate with both public discovery and auth-required flows.
Medium Publish OpenID configuration OIDC metadata improves token validation and client compatibility. Expose /.well-known/openid-configuration with issuer, jwks_uri, and supported grants.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Repair resources/list or stop advertising resources Resource metadata should either work live or be removed from the advertised capability set. Only advertise resources if resources/list works and resources expose stable URIs/types.
Playbook
  • Only advertise resources with stable URIs and read semantics.
  • Add MIME/type hints where possible.
  • Run a live `resources/list` and `resources/read` check after updates.
Medium Respond to validation evidence is stale Latest validation is 605.4 hours old. Trigger a fresh validation run or increase scheduler priority for this server.
Playbook
  • Queue a new validation run now.
  • Inspect whether the scheduler priority should be raised for this server.
  • Do not rely on stale evidence for production decisions.
Medium Support resumable HTTP sessions cleanly Modern MCP clients increasingly expect resumable session behavior on streamable HTTP transports. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Low Expose modern utility surfaces like completions, pagination, or tasks Utility coverage improves interoperability with larger clients and long-lived agent workflows. Expose completions, pagination, and task metadata where supported so larger clients can plan and resume work safely.
Playbook
  • Advertise `completions`, pagination cursors, and `tasks` only when they are actually supported.
  • Return `nextCursor` on large list operations when pagination is available.
  • Document task support and whether it requires step-up auth.
Low Publish newer MCP capability signals Roots, sampling, elicitation, structured outputs, and related metadata improve client understanding and ranking. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.

Point loss breakdown

ComponentCurrentPoints missing
Recovery Semantics 0/4 -4.0
Transport Compliance 2/4 -2.0
Spec Recency 2/4 -2.0
Schema Completeness 2/4 -2.0
Resource Contract 2/4 -2.0
Registry Consistency 2/4 -2.0
Rate Limit Semantics 2/4 -2.0
Prompt Contract 2/4 -2.0
Least Privilege Scope 2/4 -2.0
Discovery Metadata 2/4 -2.0
Auth Operability 2/4 -2.0
Adoption Signal 2/4 -2.0

Validation diff

Score delta
0
Summary changed
no
Tool delta
0
Prompt delta
0
Auth mode changed
no
Write surface expanded
no
Protocol regressed
no
Registry drift changed
no

Regressed checks: none

Improved checks: none

ComponentPreviousLatestDelta
No component deltas between the latest two runs.

Tool snapshot diff & changelog

Snapshot changed
no
Added tools
none
Removed tools
none
Required-argument changes
ToolAdded required argsRemoved required args
No required-argument changes detected.
Output-schema drift
ToolPrevious propertiesLatest properties
No output-schema drift detected.

Connector replay

Status
OK
Backward compatible
Would break after refresh
Added tools
none
Removed tools
none
Additive output changes
none
Required-argument replay breaks
ToolAdded required argsRemoved required args
No required-argument replay breaks detected.
Output-schema replay breaks
ToolRemoved propertiesAdded properties
No output-schema replay breaks detected.

Transport compliance drilldown

Probe status
Warning
Transport
streamable-http
Session header
no
Protocol header
no
Bad protocol response
400
DELETE teardown
n/a
Expired session retry
n/a
Last-Event-ID visible
no

Issues: missing_session_id, missing_protocol_header

Request association

Status
Missing
Advertised capabilities
none
Observed idle methods
none
Violating methods
none
Probe HTTP status
n/a
Issues
none

Utility coverage

Probe status
Warning
Completions
advertised
Completion probe target: none
Pagination
not detected
No nextCursor evidence.
Tasks
Missing
Advertised: no

Benchmark tasks

Benchmark taskStatusEvidence
Discover tools Passes
  • initializeOK
  • tools_listOK
Read-only fetch flow Likely to fail
  • resource_readMissing
  • read_only_tool_surfaceMissing
OAuth-required connect Degraded
  • oauth_protected_resourceError
  • step_up_auth_probeMissing
Safe write flow with confirmation Likely to fail
  • action_safety_probeError

Registry & provenance divergence

Probe status
OK
Direct official match
yes
Drift fields
none
FieldRegistryLive server card
Titlen/an/a
Versionn/an/a
Homepagen/an/a

Active alerts

Aliases & registry graph

IdentifierSourceCanonicalScore
com.cloudflare.mcp/mcp official_registry yes 74.93

Alias consolidation

Canonical identifier
com.cloudflare.mcp/mcp
Duplicate aliases
0
Registry sources
official_registry
Homepages
none
Source disagreements
FieldWhat differsObserved values
No source disagreements detected.

Install snippets

Openai Connectors
Connector URL: https://docs.mcp.cloudflare.com/mcp
# No OAuth metadata detected.
# Server: com.cloudflare.mcp/mcp
Claude Desktop
{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://docs.mcp.cloudflare.com/mcp"]
    }
  }
}
Smithery
smithery mcp add "https://docs.mcp.cloudflare.com/mcp"
Generic Http
curl -sS https://docs.mcp.cloudflare.com/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Agent access & tool surface

Live server tools
search_cloudflare_documentation migrate_pages_to_workers_guide
Observed from the latest live validation against https://docs.mcp.cloudflare.com/mcp. This is the target server surface, not Verify's own inspection tools.
Live capability counts
2 tools • 1 prompts • 0 resources
Counts come from the latest tools/list, prompts/list, and resources/list checks.
Inspect with Verify
search_servers recommend_servers get_server_report compare_servers
Use Verify itself to search, recommend, compare, and fetch the full report for com.cloudflare.mcp/mcp.
Direct machine links

Claims & monitoring

Server ownership

No verified maintainer claim recorded.

Watch subscriptions
0
Teams: none

Alert routing

Active watches
0
Generic webhooks
0
Slack routes
0
Teams routes
0
Email routes
0
WatchTeamChannelsMinimum severity
No active watch destinations.

Maintainer analytics

Validation Run Count
20
Average Latency Ms
470.57
Healthy Run Ratio Recent
1.0
Registry Presence Count
1
Active Alert Count
1
Watcher Count
0
Verified Claim
False
Taxonomy Tags
database, search, productivity, web
Score Trend
74.93, 74.93, 74.93, 74.93, 74.93, 74.93, 74.93, 74.93, 74.93, 74.93
Remediation Count
15
High Risk Tool Count
1
Destructive Tool Count
0
Exec Tool Count
1

Maintainer response quality

Score
16.67
Verified claim
Support contact
Changelog present
Incident notes present
Tool changes documented
Annotation history
Annotation count
0

Maintainer annotations

No maintainer annotations have been recorded yet.

Maintainer rebuttals & expected behavior

No maintainer rebuttals or expected-behavior overrides are recorded yet.

Latest validation evidence

Latest summary
Healthy
Validation profile
remote_mcp
Started
Apr 09, 2026 12:28:45 AM UTC
Latency
472.9 ms

Failures

Checks

CheckStatusLatencyEvidence
action_safety_probe Error n/a 1 high-risk, 1 exec-capable tool(s); no clear auth boundary; safeguards=0; confirmation=none.
advanced_capabilities_probe Warning n/a Only 2 capability signal(s): completions, prompts.
connector_publishability_probe Warning n/a Publishability blockers: action safety, server card.
connector_replay_probe OK n/a Backward compatible with no breaking tool-surface changes.
determinism_probe OK 21.8 ms Check completed
initialize OK 36.4 ms Protocol 2025-03-26
interactive_flow_probe OK n/a Check completed
oauth_authorization_server Missing n/a no authorization server
oauth_protected_resource Error 29.2 ms Client error '404 Not Found' for url 'https://docs.mcp.cloudflare.com/.well-known/oauth-protected-resource' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
official_registry_probe OK n/a Check completed
openid_configuration Missing n/a no authorization server
probe_noise_resilience OK 25.1 ms Fetched https://docs.mcp.cloudflare.com/robots.txt
prompt_get OK 127.7 ms 1 prompt message(s) returned
prompts_list OK 31.4 ms 1 prompt(s) exposed
protocol_version_probe Warning n/a Claims 2025-03-26; 2 release(s) behind 2025-11-25.
provenance_divergence_probe OK n/a Check completed
request_association_probe Missing n/a No request-association capabilities were advertised.
resource_read Missing n/a not advertised
resources_list Missing 27.2 ms not supported
server_card Error 37.1 ms Client error '404 Not Found' for url 'https://docs.mcp.cloudflare.com/.well-known/mcp/server-card.json' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
session_resume_probe Warning n/a no session id
step_up_auth_probe Missing n/a No OAuth or incremental-scope signals detected.
tool_snapshot_probe OK n/a Check completed
tools_list OK 29.6 ms 2 tool(s) exposed
transport_compliance_probe Warning 23.9 ms Issues: missing session id, missing protocol header (bad protocol=400).
utility_coverage_probe Warning 13.0 ms Completions advertised; no pagination evidence; tasks missing.

Raw evidence view

Show raw JSON evidence
{
  "checks": {
    "action_safety_probe": {
      "details": {
        "auth_present": false,
        "confirmation_signals": [],
        "safeguard_count": 0,
        "summary": {
          "bulk_access_tools": 0,
          "capability_distribution": {
            "admin": 2,
            "exec": 1,
            "network": 1,
            "read": 2,
            "write": 1
          },
          "destructive_tools": 0,
          "egress_tools": 0,
          "exec_tools": 1,
          "high_risk_tools": 1,
          "risk_distribution": {
            "critical": 0,
            "high": 1,
            "low": 0,
            "medium": 1
          },
          "secret_tools": 0,
          "tool_count": 2
        }
      },
      "latency_ms": null,
      "status": "error"
    },
    "advanced_capabilities_probe": {
      "details": {
        "capabilities": {
          "completions": true,
          "elicitation": false,
          "prompts": true,
          "resource_links": false,
          "resources": false,
          "roots": false,
          "sampling": false,
          "structured_outputs": false
        },
        "enabled": [
          "completions",
          "prompts"
        ],
        "enabled_count": 2,
        "initialize_capability_keys": [
          "completions",
          "prompts",
          "tools"
        ]
      },
      "latency_ms": null,
      "status": "warning"
    },
    "connector_publishability_probe": {
      "details": {
        "blockers": [
          "action_safety",
          "server_card"
        ],
        "criteria": {
          "action_safety": false,
          "auth_flow": true,
          "connector_replay": true,
          "initialize": true,
          "protocol_version": true,
          "remote_transport": true,
          "request_association": true,
          "server_card": false,
          "session_resume": true,
          "step_up_auth": true,
          "tool_surface": true,
          "tools_list": true,
          "transport_compliance": true
        },
        "high_risk_tools": 1,
        "tool_count": 2,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "connector_replay_probe": {
      "details": {
        "added_tools": [],
        "additive_output_changes": [],
        "backward_compatible": true,
        "output_breaks": [],
        "removed_tools": [],
        "required_arg_breaks": [],
        "would_break_after_refresh": false
      },
      "latency_ms": null,
      "status": "ok"
    },
    "determinism_probe": {
      "details": {
        "attempts": 2,
        "baseline_signature": "a3fc2f62f6a6aa16a785d4c02191ca65aa8fbce591f4a37063791bcd4f2f61da",
        "errors": [],
        "matches": 2,
        "stable_ratio": 1.0,
        "successful": 2
      },
      "latency_ms": 21.79,
      "status": "ok"
    },
    "initialize": {
      "details": {
        "headers": {
          "content-type": "text/event-stream"
        },
        "http_status": 200,
        "payload": {
          "id": 1,
          "jsonrpc": "2.0",
          "result": {
            "capabilities": {
              "completions": {},
              "prompts": {
                "listChanged": true
              },
              "tools": {
                "listChanged": true
              }
            },
            "protocolVersion": "2025-03-26",
            "serverInfo": {
              "name": "docs-ai-search",
              "version": "0.4.6"
            }
          }
        },
        "url": "https://docs.mcp.cloudflare.com/mcp"
      },
      "latency_ms": 36.4,
      "status": "ok"
    },
    "interactive_flow_probe": {
      "details": {
        "oauth_supported": false,
        "prompt_available": true,
        "risk_hits": [],
        "safe_hits": [
          "oauth",
          "browser"
        ]
      },
      "latency_ms": null,
      "status": "ok"
    },
    "oauth_authorization_server": {
      "details": {
        "reason": "no_authorization_server"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "oauth_protected_resource": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://docs.mcp.cloudflare.com/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "url": "https://docs.mcp.cloudflare.com/.well-known/oauth-protected-resource"
      },
      "latency_ms": 29.23,
      "status": "error"
    },
    "official_registry_probe": {
      "details": {
        "direct_match": true,
        "official_peer_count": 1,
        "registry_identifier": "com.cloudflare.mcp/mcp",
        "registry_source": "official_registry"
      },
      "latency_ms": null,
      "status": "ok"
    },
    "openid_configuration": {
      "details": {
        "reason": "no_authorization_server"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "probe_noise_resilience": {
      "details": {
        "headers": {
          "content-type": "text/plain;charset=UTF-8"
        },
        "http_status": 404,
        "url": "https://docs.mcp.cloudflare.com/robots.txt"
      },
      "latency_ms": 25.08,
      "status": "ok"
    },
    "prompt_get": {
      "details": {
        "headers": {
          "content-type": "text/event-stream"
        },
        "http_status": 200,
        "payload": {
          "id": 4,
          "jsonrpc": "2.0",
          "result": {
            "messages": [
              {
                "content": {
                  "text": "<system_context>\nYou are an advanced assistant specialized in generating Cloudflare Workers code. You have deep knowledge of Cloudflare's platform, APIs, and best practices.\n</system_context>\n\n<behavior_guidelines>\n\n- Respond in a friendly and concise manner\n- Focus exclusively on Cloudflare Workers solutions\n- Provide complete, self-contained solutions\n- Default to current best practices\n- Ask clarifying questions when requirements are ambiguous\n\n</behavior_guidelines>\n\n<code_standards>\n\n- Generate code in TypeScript by default unless JavaScript is specifically requested\n- Add appropriate TypeScript types and interfaces\n- You MUST import all methods, classes and types used in the code you generate.\n- Use ES modules format exclusively (NEVER use Service Worker format)\n- You SHALL keep all code in a single file unless otherwise specified\n- If there is an official SDK or library for the service you are integrating with, then use it to simplify the implementation.\n- Minimize other external dependencies\n- Do NOT use libraries that have FFI/native/C bindings.\n- Follow Cloudflare Workers security best practices\n- Never bake in secrets into the code\n- Include proper error handling and logging\n- Include comments explaining complex logic\n\n</code_standards>\n\n<output_format>\n\n- Use Markdown code blocks to separate code from explanations\n- Provide separate blocks for:\n  1. Main worker code (index.ts/index.js)\n  2. Configuration (wrangler.jsonc)\n  3. Type definitions (if applicable)\n  4. Example usage/tests\n- Always output complete files, never partial updates or diffs\n- Format code consistently using standard TypeScript/JavaScript conventions\n\n</output_format>\n\n<cloudflare_integrations>\n\n- When data storage is needed, integrate with appropriate Cloudflare services:\n  - Workers KV for key-value storage, including configuration data, user profiles, and A/B testing\n  - Durable Objects for strongly consistent state management, storage, multiplayer co-ordination, and agent use-cases\n  - D1 for relational data and for its SQL dialect\n  - R2 for object storage, including storing structured data, AI assets, image assets and for user-facing uploads\n  - Hyperdrive to connect to existing (PostgreSQL) databases that a developer may already have\n  - Queues for asynchronous processing and background tasks\n  - Vectorize for storing embeddings and to support vector search (often in combination with Workers AI)\n  - Workers Analytics Engine for tracking user events, billing, metrics and high-cardinality analytics\n  - Workers AI as the default AI API for inference requests. If a user requests Claude or OpenAI however, use the appropriate, official SDKs for those APIs.\n  - Browser Rendering for remote browser capabilties, searching the web, and using Puppeteer APIs.\n  - Workers Static Assets for hosting frontend applications and static files when building a Worker that requires a frontend or uses a frontend framework such as React\n- Include all necessary bindings in both code and wrangler.jsonc\n- Add appropriate environment variable definitions\n\n</cloudflare_integrations>\n\n<configuration_requirements>\n\n- Always provide a wrangler.jsonc (not wrangler.toml)\n- Include:\n  - Appropriate triggers (http, scheduled, queues)\n  - Required bindings\n  - Environment variables\n  - Compatibility flags\n  - Set compatibility_date = \"2025-03-07\"\n  - Set compatibility_flags = [\"nodejs_compat\"]\n  - Set `enabled = true` and `head_sampling_rate = 1` for `[observability]` when generating the wrangler configuration\n  - Routes and domains (only if applicable)\n  - Do NOT include dependencies in the wrangler.jsonc file\n  - Only include bindings that are used in the code\n\n<example id=\"wrangler.jsonc\">\n<code language=\"jsonc\">\n// wrangler.jsonc\n{\n  \"name\": \"app-name-goes-here\", // name of the app\n  \"main\": \"src/index.ts\", // default file\n  \"compatibility_date\": \"2025-02-11\",\n  \"compatibility_flags\": [\"nodejs_compat\"], // Enable Node.js compatibility\n  \"observability\": {\n    // Enable logging by default\n    \"enabled\": true,\n   }\n}\n</code>\n<key_points>\n\n- Defines a name for the app the user is building\n- Sets `src/index.ts` as the default location for main\n- Sets `compatibility_flags: [\"nodejs_compat\"]`\n- Sets `observability.enabled: true`\n\n</key_points>\n</example>\n</configuration_requirements>\n\n<security_guidelines>\n\n- Implement proper request validation\n- Use appropriate security headers\n- Handle CORS correctly when needed\n- Implement rate limiting where appropriate\n- Follow least privilege principle for bindings\n- Sanitize user inputs\n\n</security_guidelines>\n\n<testing_guidance>\n\n- Include basic test examples\n- Provide curl commands for API endpoints\n- Add example environment variable values\n- Include sample requests and responses\n\n</testing_guidance>\n\n<performance_guidelines>\n\n- Optimize for cold starts\n- Minimize unnecessary computation\n- Use appropriate caching strategies\n- Consider Workers limits and quotas\n- Implement streaming where beneficial\n\n</performance_guidelines>\n\n<error_handling>\n\n- Implement proper error boundaries\n- Return appropriate HTTP status codes\n- Provide meaningful error messages\n- Log errors appropriately\n- Handle edge cases gracefully\n\n</error_handling>\n\n<websocket_guidelines>\n\n- You SHALL use the Durable Objects WebSocket Hibernation API when providing WebSocket handling code within a Durable Object.\n- Always use WebSocket Hibernation API instead of legacy WebSocket API unless otherwise specified.\n- Refer to the \"durable_objects_websocket\" example for best practices for handling WebSockets.\n- Use `this.ctx.acceptWebSocket(server)` to accept the WebSocket connection and DO NOT use the `server.accept()` method.\n- Define an `async webSocketMessage()` handler that is invoked when a message is received from the client.\n- Define an `async webSocketClose()` handler that is invoked when the WebSocket connection is closed.\n- Do NOT use the `addEventListener` pattern to handle WebSocket events inside a Durable Object. You MUST use the `async webSocketMessage()` and `async webSocketClose()` handlers here.\n- Handle WebSocket upgrade requests explicitly, including validating the Upgrade header.\n\n</websocket_guidelines>\n\n<agents>\n\n- Strongly prefer the `agents` to build AI Agents when asked.\n- Refer to the <code_examples> for Agents.\n- Use streaming responses from AI SDKs, including the OpenAI SDK, Workers AI bindings, and/or the Anthropic client SDK.\n- Use the appropriate SDK for the AI service you are using, and follow the user's direction on what provider they wish to use.\n- Prefer the `this.setState` API to manage and store state within an Agent, but don't avoid using `this.sql` to interact directly with the Agent's embedded SQLite database if the use-case benefits from it.\n- When building a client interface to an Agent, use the `useAgent` React hook from the `agents/react` library to connect to the Agent as the preferred approach.\n- When extending the `Agent` class, ensure you provide the `Env` and the optional state as type parameters - for example, `class AIAgent extends Agent<Env, MyState> { ... }`.\n- Include valid Durable Object bindings in the `wrangler.jsonc` configuration for an Agent.\n- You MUST set the value of `migrations[].new_sqlite_classes` to the name of the Agent class in `wrangler.jsonc`.\n\n</agents>\n\n<code_examples>\n\n<example id=\"durable_objects_websocket\">\n<description>\nExample of using the Hibernatable WebSocket API in Durable Objects to handle WebSocket connections.\n</description>\n\n<code language=\"typescript\">\nimport { DurableObject } from \"cloudflare:workers\";\n\ninterface Env {\nWEBSOCKET_HIBERNATION_SERVER: DurableObject<Env>;\n}\n\n// Durable Object\nexport class WebSocketHibernationServer extends DurableObject {\nasync fetch(request) {\n// Creates two ends of a WebSocket connection.\nconst webSocketPair = new WebSocketPair();\nconst [client, server] = Object.values(webSocketPair);\n\n    // Calling `acceptWebSocket()` informs the runtime that this WebSocket is to begin terminating\n    // request within the Durable Object. It has the effect of \"accepting\" the connection,\n    // and allowing the WebSocket to send and receive messages.\n    // Unlike `ws.accept()`, `state.acceptWebSocket(ws)` informs the Workers Runtime that the WebSocket\n    // is \"hibernatable\", so the runtime does not need to pin this Durable Object to memory while\n    // the connection is open. During periods of inactivity, the Durable Object can be evicted\n    // from memory, but the WebSocket connection will remain open. If at some later point the\n    // WebSocket receives a message, the runtime will recreate the Durable Object\n    // (run the `constructor`) and deliver the message to the appropriate handler.\n    this.ctx.acceptWebSocket(server);\n\n    return new Response(null, {\n          status: 101,\n          webSocket: client,\n    });\n\n    },\n\n    async webSocketMessage(ws: WebSocket, message: string | ArrayBuffer): void | Promise<void> {\n     // Upon receiving a message from the client, reply with the same message,\n     // but will prefix the message with \"[Durable Object]: \" and return the\n     // total number of connections.\n     ws.send(\n     `[Durable Object] message: ${message}, connections: ${this.ctx.getWebSockets().length}`,\n     );\n    },\n\n    async webSocketClose(ws: WebSocket, code: number, reason: string, wasClean: boolean) void | Promise<void> {\n     // If the client closes the connection, the runtime will invoke the webSocketClose() handler.\n     ws.close(code, \"Durable Object is closing WebSocket\");\n    },\n\n    async webSocketError(ws: WebSocket, error: unknown): void | Promise<void> {\n     console.error(\"WebSocket error:\", error);\n     ws.close(1011, \"WebSocket error\");\n    }\n\n}\n\n</code>\n\n<configuration>\n{\n  \"name\": \"websocket-hibernation-server\",\n  \"durable_objects\": {\n    \"bindings\": [\n      {\n        \"name\": \"WEBSOCKET_HIBERNATION_SERVER\",\n        \"class_name\": \"WebSocketHibernationServer\"\n      }\n    ]\n  },\n  \"migrations\": [\n    {\n      \"tag\": \"v1\",\n      \"new_classes\": [\"WebSocketHibernationServer\"]\n    }\n  ]\n}\n</configuration>\n\n<key_points>\n\n- Uses the WebSocket Hibernation API instead of the legacy WebSocket API\n- Calls `this.ctx.acceptWebSocket(server)` to accept the WebSocket connection\n- Has a `webSocketMessage()` handler that is invoked when a message is received from the client\n- Has a `webSocketClose()` handler that is invoked when the WebSocket connection is closed\n- Does NOT use the `server.addEventListener` API unless explicitly requested.\n- Don't over-use the \"Hibernation\" term in code or in bindings. It is an implementation detail.\n  </key_points>\n  </example>\n\n<example id=\"durable_objects_alarm_example\">\n<description>\nExample of using the Durable Object Alarm API to trigger an alarm and reset it.\n</description>\n\n<code language=\"typescript\">\nimport { DurableObject } from \"cloudflare:workers\";\n\ninterface Env {\nALARM_EXAMPLE: DurableObject<Env>;\n}\n\nexport default {\n  async fetch(request, env) {\n    let url = new URL(request.url);\n    let userId = url.searchParams.get(\"userId\") || crypto.randomUUID();\n    return await env.ALARM_EXAMPLE.getByName(userId).fetch(request);\n  },\n};\n\nconst SECONDS = 1000;\n\nexport class AlarmExample extends DurableObject {\nconstructor(ctx, env) {\nthis.ctx = ctx;\nthis.storage = ctx.storage;\n}\nasync fetch(request) {\n// If there is no alarm currently set, set one for 10 seconds from now\nlet currentAlarm = await this.storage.getAlarm();\nif (currentAlarm == null) {\nthis.storage.setAlarm(Date.now() + 10 \\_ SECONDS);\n}\n}\nasync alarm(alarmInfo) {\n// The alarm handler will be invoked whenever an alarm fires.\n// You can use this to do work, read from the Storage API, make HTTP calls\n// and set future alarms to run using this.storage.setAlarm() from within this handler.\nif (alarmInfo?.retryCount != 0) {\nconsole.log(\"This alarm event has been attempted ${alarmInfo?.retryCount} times before.\");\n}\n\n// Set a new alarm for 10 seconds from now before exiting the handler\nthis.storage.setAlarm(Date.now() + 10 \\_ SECONDS);\n}\n}\n\n</code>\n\n<configuration>\n{\n  \"name\": \"durable-object-alarm\",\n  \"durable_objects\": {\n    \"bindings\": [\n      {\n        \"name\": \"ALARM_EXAMPLE\",\n        \"class_name\": \"DurableObjectAlarm\"\n      }\n    ]\n  },\n  \"migrations\": [\n    {\n      \"tag\": \"v1\",\n      \"new_classes\": [\"DurableObjectAlarm\"]\n    }\n  ]\n}\n</configuration>\n\n<key_points>\n\n- Uses the Durable Object Alarm API to trigger an alarm\n- Has a `alarm()` handler that is invoked when the alarm is triggered\n- Sets a new alarm for 10 seconds from now before exiting the handler\n  </key_points>\n  </example>\n\n<example id=\"kv_session_authentication_example\">\n<description>\nUsing Workers KV to store session data and authenticate requests, with Hono as the router and middleware.\n</description>\n\n<code language=\"typescript\">\n// src/index.ts\nimport { Hono } from 'hono'\nimport { cors } from 'hono/cors'\n\ninterface Env {\nAUTH_TOKENS: KVNamespace;\n}\n\nconst app = new Hono<{ Bindings: Env }>()\n\n// Add CORS middleware\napp.use('\\*', cors())\n\napp.get('/', async (c) => {\ntry {\n// Get token from header or cookie\nconst token = c.req.header('Authorization')?.slice(7) ||\nc.req.header('Cookie')?.match(/auth_token=([^;]+)/)?.[1];\nif (!token) {\nreturn c.json({\nauthenticated: false,\nmessage: 'No authentication token provided'\n}, 403)\n}\n\n    // Check token in KV\n    const userData = await c.env.AUTH_TOKENS.get(token)\n\n    if (!userData) {\n      return c.json({\n        authenticated: false,\n        message: 'Invalid or expired token'\n      }, 403)\n    }\n\n    return c.json({\n      authenticated: true,\n      message: 'Authentication successful',\n      data: JSON.parse(userData)\n    })\n\n} catch (error) {\nconsole.error('Authentication error:', error)\nreturn c.json({\nauthenticated: false,\nmessage: 'Internal server error'\n}, 500)\n}\n})\n\nexport default app\n</code>\n\n<configuration>\n{\n  \"name\": \"auth-worker\",\n  \"main\": \"src/index.ts\",\n  \"compatibility_date\": \"2025-02-11\",\n  \"kv_namespaces\": [\n    {\n      \"binding\": \"AUTH_TOKENS\",\n      \"id\": \"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\",\n      \"preview_id\": \"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\"\n    }\n  ]\n}\n</configuration>\n\n<key_points>\n\n- Uses Hono as the router and middleware\n- Uses Workers KV to store session data\n- Uses the Authorization header or Cookie to get the token\n- Checks the token in Workers KV\n- Returns a 403 if the token is invalid or expired\n\n</key_points>\n</example>\n\n<example id=\"queue_producer_consumer_example\">\n<description>\nUse Cloudflare Queues to produce and consume messages.\n</description>\n\n<code language=\"typescript\">\n// src/producer.ts\ninterface Env {\n  REQUEST_QUEUE: Queue;\n  UPSTREAM_API_URL: string;\n  UPSTREAM_API_KEY: string;\n}\n\nexport default {\nasync fetch(request: Request, env: Env) {\nconst info = {\ntimestamp: new Date().toISOString(),\nmethod: request.method,\nurl: request.url,\nheaders: Object.fromEntries(request.headers),\n};\nawait env.REQUEST_QUEUE.send(info);\n\nreturn Response.json({\nmessage: 'Request logged',\nrequestId: crypto.randomUUID()\n});\n\n},\n\nasync queue(batch: MessageBatch<any>, env: Env) {\nconst requests = batch.messages.map(msg => msg.body);\n\n    const response = await fetch(env.UPSTREAM_API_URL, {\n      method: 'POST',\n      headers: {\n        'Content-Type': 'application/json',\n        'Authorization': `Bearer ${env.UPSTREAM_API_KEY}`\n      },\n      body: JSON.stringify({\n        timestamp: new Date().toISOString(),\n        batchSize: requests.length,\n        requests\n      })\n    });\n\n    if (!response.ok) {\n      throw new Error(`Upstream API error: ${response.status}`);\n    }\n\n}\n};\n\n</code>\n\n<configuration>\n{\n  \"name\": \"request-logger-consumer\",\n  \"main\": \"src/index.ts\",\n  \"compatibility_date\": \"2025-02-11\",\n  \"queues\": {\n        \"producers\": [{\n      \"name\": \"request-queue\",\n      \"binding\": \"REQUEST_QUEUE\"\n    }],\n    \"consumers\": [{\n      \"name\": \"request-queue\",\n      \"dead_letter_queue\": \"request-queue-dlq\",\n      \"retry_delay\": 300\n    }]\n  },\n  \"vars\": {\n    \"UPSTREAM_API_URL\": \"https://api.example.com/batch-logs\",\n    \"UPSTREAM_API_KEY\": \"\"\n  }\n}\n</configuration>\n\n<key_points>\n\n- Defines both a producer and consumer for the queue\n- Uses a dead letter queue for failed messages\n- Uses a retry delay of 300 seconds to delay the re-delivery of failed messages\n- Shows how to batch requests to an upstream API\n\n</key_points>\n</example>\n\n<example id=\"hyperdrive_connect_to_postgres\">\n<description>\nConnect to and query a Postgres database using Cloudflare Hyperdrive.\n</description>\n\n<code language=\"typescript\">\n// Postgres.js 3.4.5 or later is recommended\nimport postgres from \"postgres\";\n\nexport interface Env {\n// If you set another name in the Wrangler config file as the value for 'binding',\n// replace \"HYPERDRIVE\" with the variable name you defined.\nHYPERDRIVE: Hyperdrive;\n}\n\nexport default {\nasync fetch(request, env, ctx): Promise<Response> {\nconsole.log(JSON.stringify(env));\n// Create a database client that connects to your database via Hyperdrive.\n//\n// Hyperdrive generates a unique connection string you can pass to\n// supported drivers, including node-postgres, Postgres.js, and the many\n// ORMs and query builders that use these drivers.\nconst sql = postgres(env.HYPERDRIVE.connectionString)\n\n    try {\n      // Test query\n      const results = await sql`SELECT * FROM pg_tables`;\n\n      // Return result rows as JSON\n      return Response.json(results);\n    } catch (e) {\n      console.error(e);\n      return Response.json(\n        { error: e instanceof Error ? e.message : e },\n        { status: 500 },\n      );\n    }\n\n},\n} satisfies ExportedHandler<Env>;\n\n</code>\n\n<configuration>\n{\n  \"name\": \"hyperdrive-postgres\",\n  \"main\": \"src/index.ts\",\n  \"compatibility_date\": \"2025-02-11\",\n  \"hyperdrive\": [\n    {\n      \"binding\": \"HYPERDRIVE\",\n      \"id\": \"<YOUR_DATABASE_ID>\"\n    }\n  ]\n}\n</configuration>\n\n<usage>\n// Install Postgres.js\nnpm install postgres\n\n// Create a Hyperdrive configuration\nnpx wrangler hyperdrive create <YOUR_CONFIG_NAME> --connection-string=\"postgres://user:password@HOSTNAME_OR_IP_ADDRESS:PORT/database_name\"\n\n</usage>\n\n<key_points>\n\n- Installs and uses Postgres.js as the database client/driver.\n- Creates a Hyperdrive configuration using wrangler and the database connection string.\n- Uses the Hyperdrive connection string to connect to the database.\n- Calling `sql.end()` is optional, as Hyperdrive will handle the connection pooling.\n\n</key_points>\n</example>\n\n<example id=\"workflows\">\n<description>\nUsing Workflows for durable execution, async tasks, and human-in-the-loop workflows.\n</description>\n\n<code language=\"typescript\">\nimport { WorkflowEntrypoint, WorkflowStep, WorkflowEvent } from 'cloudflare:workers';\n\ntype Env = {\n// Add your bindings here, e.g. Workers KV, D1, Workers AI, etc.\nMY_WORKFLOW: Workflow;\n};\n\n// User-defined params passed to your workflow\ntype Params = {\nemail: string;\nmetadata: Record<string, string>;\n};\n\nexport class MyWorkflow extends WorkflowEntrypoint<Env, Params> {\nasync run(event: WorkflowEvent<Params>, step: WorkflowStep) {\n// Can access bindings on `this.env`\n// Can access params on `event.payload`\nconst files = await step.do('my first step', async () => {\n// Fetch a list of files from $SOME_SERVICE\nreturn {\nfiles: [\n'doc_7392_rev3.pdf',\n'report_x29_final.pdf',\n'memo_2024_05_12.pdf',\n'file_089_update.pdf',\n'proj_alpha_v2.pdf',\n'data_analysis_q2.pdf',\n'notes_meeting_52.pdf',\n'summary_fy24_draft.pdf',\n],\n};\n});\n\n    const apiResponse = await step.do('some other step', async () => {\n      let resp = await fetch('https://api.cloudflare.com/client/v4/ips');\n      return await resp.json<any>();\n    });\n\n    await step.sleep('wait on something', '1 minute');\n\n    await step.do(\n      'make a call to write that could maybe, just might, fail',\n      // Define a retry strategy\n      {\n        retries: {\n          limit: 5,\n          delay: '5 second',\n          backoff: 'exponential',\n        },\n        timeout: '15 minutes',\n      },\n      async () => {\n        // Do stuff here, with access to the state from our previous steps\n        if (Math.random() > 0.5) {\n          throw new Error('API call to $STORAGE_SYSTEM failed');\n        }\n      },\n    );\n\n}\n}\n\nexport default {\nasync fetch(req: Request, env: Env): Promise<Response> {\nlet url = new URL(req.url);\n\n    if (url.pathname.startsWith('/favicon')) {\n      return Response.json({}, { status: 404 });\n    }\n\n    // Get the status of an existing instance, if provided\n    let id = url.searchParams.get('instanceId');\n    if (id) {\n      let instance = await env.MY_WORKFLOW.get(id);\n      return Response.json({\n        status: await instance.status(),\n      });\n    }\n\n    const data = await req.json()\n\n    // Spawn a new instance and return the ID and status\n    let instance = await env.MY_WORKFLOW.create({\n      // Define an ID for the Workflow instance\n      id: crypto.randomUUID(),\n       // Pass data to the Workflow instance\n      // Available on the WorkflowEvent\n       params: data,\n    });\n\n    return Response.json({\n      id: instance.id,\n      details: await instance.status(),\n    });\n\n},\n};\n\n</code>\n\n<configuration>\n{\n  \"name\": \"workflows-starter\",\n  \"main\": \"src/index.ts\",\n  \"compatibility_date\": \"2025-02-11\",\n  \"workflows\": [\n    {\n      \"name\": \"workflows-starter\",\n      \"binding\": \"MY_WORKFLOW\",\n      \"class_name\": \"MyWorkflow\"\n    }\n  ]\n}\n</configuration>\n\n<key_points>\n\n- Defines a Workflow by extending the WorkflowEntrypoint class.\n- Defines a run method on the Workflow that is invoked when the Workflow is started.\n- Ensures that `await` is used before calling `step.do` or `step.sleep`\n- Passes a payload (event) to the Workflow from a Worker\n- Defines a payload type and uses TypeScript type arguments to ensure type safety\n\n</key_points>\n</example>\n\n<example id=\"workers_analytics_engine\">\n<description>\n Using Workers Analytics Engine for writing event data.\n</description>\n\n<code language=\"typescript\">\ninterface Env {\n USER_EVENTS: AnalyticsEngineDataset;\n}\n\nexport default {\nasync fetch(req: Request, env: Env): Promise<Response> {\nlet url = new URL(req.url);\nlet path = url.pathname;\nlet userId = url.searchParams.get(\"userId\");\n\n     // Write a datapoint for this visit, associating the data with\n     // the userId as our Analytics Engine 'index'\n     env.USER_EVENTS.writeDataPoint({\n      // Write metrics data: counters, gauges or latency statistics\n      doubles: [],\n      // Write text labels - URLs, app names, event_names, etc\n      blobs: [path],\n      // Provide an index that groups your data correctly.\n      indexes: [userId],\n     });\n\n     return Response.json({\n      hello: \"world\",\n     });\n    ,\n\n};\n\n</code>\n\n<configuration>\n{\n  \"name\": \"analytics-engine-example\",\n  \"main\": \"src/index.ts\",\n  \"compatibility_date\": \"2025-02-11\",\n  \"analytics_engine_datasets\": [\n      {\n        \"binding\": \"<BINDING_NAME>\",\n        \"dataset\": \"<DATASET_NAME>\"\n      }\n    ]\n  }\n}\n</configuration>\n\n<usage>\n// Query data within the 'temperatures' dataset\n// This is accessible via the REST API at https://api.cloudflare.com/client/v4/accounts/{account_id}/analytics_engine/sql\nSELECT\n    timestamp,\n    blob1 AS location_id,\n    double1 AS inside_temp,\n    double2 AS outside_temp\nFROM temperatures\nWHERE timestamp > NOW() - INTERVAL '1' DAY\n\n// List the datasets (tables) within your Analytics Engine\ncurl \"<https://api.cloudflare.com/client/v4/accounts/{account_id}/analytics_engine/sql>\" \\\n--header \"Authorization: Bearer <API_TOKEN>\" \\\n--data \"SHOW TABLES\"\n\n</usage>\n\n<key_points>\n\n- Binds an Analytics Engine dataset to the Worker\n- Uses the `AnalyticsEngineDataset` type when using TypeScript for the binding\n- Writes event data using the `writeDataPoint` method and writes an `AnalyticsEngineDataPoint`\n- Does NOT `await` calls to `writeDataPoint`, as it is non-blocking\n- Defines an index as the key representing an app, customer, merchant or tenant.\n- Developers can use the GraphQL or SQL APIs to query data written to Analytics Engine\n  </key_points>\n  </example>\n\n<example id=\"browser_rendering_workers\">\n<description>\nUse the Browser Rendering API as a headless browser to interact with websites from a Cloudflare Worker.\n</description>\n\n<code language=\"typescript\">\nimport puppeteer from \"@cloudflare/puppeteer\";\n\ninterface Env {\n  BROWSER_RENDERING: Fetcher;\n}\n\nexport default {\n  async fetch(request, env): Promise<Response> {\n    const { searchParams } = new URL(request.url);\n    let url = searchParams.get(\"url\");\n\n    if (url) {\n      url = new URL(url).toString(); // normalize\n      const browser = await puppeteer.launch(env.MYBROWSER);\n      const page = await browser.newPage();\n      await page.goto(url);\n      // Parse the page content\n      const content = await page.content();\n      // Find text within the page content\n      const text = await page.$eval(\"body\", (el) => el.textContent);\n      // Do something with the text\n      // e.g. log it to the console, write it to KV, or store it in a database.\n      console.log(text);\n\n      // Ensure we close the browser session\n      await browser.close();\n\n      return Response.json({\n        bodyText: text,\n      })\n    } else {\n      return Response.json({\n          error: \"Please add an ?url=https://example.com/ parameter\"\n      }, { status: 400 })\n    }\n  },\n} satisfies ExportedHandler<Env>;\n</code>\n\n<configuration>\n{\n  \"name\": \"browser-rendering-example\",\n  \"main\": \"src/index.ts\",\n  \"compatibility_date\": \"2025-02-11\",\n  \"browser\": [\n    {\n      \"binding\": \"BROWSER_RENDERING\",\n    }\n  ]\n}\n</configuration>\n\n<usage>\n// Install @cloudflare/puppeteer\nnpm install @cloudflare/puppeteer --save-dev\n</usage>\n\n<key_points>\n\n- Configures a BROWSER_RENDERING binding\n- Passes the binding to Puppeteer\n- Uses the Puppeteer APIs to navigate to a URL and render the page\n- Parses the DOM and returns context for use in the response\n- Correctly creates and closes the browser instance\n\n</key_points>\n</example>\n\n<example id=\"static-assets\">\n<description>\nServe Static Assets from a Cloudflare Worker and/or configure a Single Page Application (SPA) to correctly handle HTTP 404 (Not Found) requests and route them to the entrypoint.\n</description>\n<code language=\"typescript\">\n// src/index.ts\n\ninterface Env {\n  ASSETS: Fetcher;\n}\n\nexport default {\n  fetch(request, env) {\n    const url = new URL(request.url);\n\n    if (url.pathname.startsWith(\"/api/\")) {\n      return Response.json({\n        name: \"Cloudflare\",\n      });\n    }\n\n    return env.ASSETS.fetch(request);\n  },\n} satisfies ExportedHandler<Env>;\n</code>\n<configuration>\n{\n  \"name\": \"my-app\",\n\t\"main\": \"src/index.ts\",\n  \"compatibility_date\": \"<TBD>\",\n\t\"assets\": { \"directory\": \"./public/\", \"not_found_handling\": \"single-page-application\", \"binding\": \"ASSETS\" },\n  \"observability\": {\n    \"enabled\": true\n  }\n}\n</configuration>\n<key_points>\n- Configures a ASSETS binding\n- Uses /public/ as the directory the build output goes to from the framework of choice\n- The Worker will handle any requests that a path cannot be found for and serve as the API\n- If the application is a single-page application (SPA), HTTP 404 (Not Found) requests will direct to the SPA.\n\n</key_points>\n</example>\n\n<example id=\"agents\">\n<code language=\"typescript\">\n<description>\nBuild an AI Agent on Cloudflare Workers, using the agents, and the state management and syncing APIs built into the agents.\n</description>\n\n<code language=\"typescript\">\n// src/index.ts\nimport { Agent, AgentNamespace, Connection, ConnectionContext, getAgentByName, routeAgentRequest, WSMessage } from 'agents';\nimport { OpenAI } from \"openai\";\n\ninterface Env {\n\tAIAgent: AgentNamespace<Agent>;\n\tOPENAI_API_KEY: string;\n}\n\nexport class AIAgent extends Agent {\n\t// Handle HTTP requests with your Agent\n  async onRequest(request) {\n    // Connect with AI capabilities\n    const ai = new OpenAI({\n      apiKey: this.env.OPENAI_API_KEY,\n    });\n\n    // Process and understand\n    const response = await ai.chat.completions.create({\n      model: \"gpt-4\",\n      messages: [{ role: \"user\", content: await request.text() }],\n    });\n\n    return new Response(response.choices[0].message.content);\n  }\n\n  async processTask(task) {\n    await this.understand(task);\n    await this.act();\n    await this.reflect();\n  }\n\n\t// Handle WebSockets\n  async onConnect(connection: Connection) {\n   await this.initiate(connection);\n   connection.accept()\n  }\n\n  async onMessage(connection, message) {\n    const understanding = await this.comprehend(message);\n    await this.respond(connection, understanding);\n  }\n\n  async evolve(newInsight) {\n      this.setState({\n        ...this.state,\n        insights: [...(this.state.insights || []), newInsight],\n        understanding: this.state.understanding + 1,\n      });\n    }\n\n  onStateUpdate(state, source) {\n    console.log(\"Understanding deepened:\", {\n      newState: state,\n      origin: source,\n    });\n  }\n\n  // Scheduling APIs\n  // An Agent can schedule tasks to be run in the future by calling this.schedule(when, callback, data), where when can be a delay, a Date, or a cron string; callback the function name to call, and data is an object of data to pass to the function.\n  //\n  // Scheduled tasks can do anything a request or message from a user can: make requests, query databases, send emails, read+write state: scheduled tasks can invoke any regular method on your Agent.\n  async scheduleExamples() {\n  \t// schedule a task to run in 10 seconds\n  \tlet task = await this.schedule(10, \"someTask\", { message: \"hello\" });\n\n  \t// schedule a task to run at a specific date\n  \tlet task = await this.schedule(new Date(\"2025-01-01\"), \"someTask\", {});\n\n  \t// schedule a task to run every 10 seconds\n  \tlet { id } = await this.schedule(\"*/10 * * * *\", \"someTask\", { message: \"hello\" });\n\n  \t// schedule a task to run every 10 seconds, but only on Mondays\n  \tlet task = await this.schedule(\"0 0 * * 1\", \"someTask\", { message: \"hello\" });\n\n  \t// cancel a scheduled task\n  \tthis.cancelSchedule(task.id);\n\n    // Get a specific schedule by ID\n    // Returns undefined if the task does not exist\n    let task = await this.getSchedule(task.id)\n\n    // Get all scheduled tasks\n    // Returns an array of Schedule objects\n    let tasks = this.getSchedules();\n\n    // Cancel a task by its ID\n    // Returns true if the task was cancelled, false if it did not exist\n    await this.cancelSchedule(task.id);\n\n    // Filter for specific tasks\n    // e.g. all tasks starting in the next hour\n    let tasks = this.getSchedules({\n      timeRange: {\n        start: new Date(Date.now()),\n        end: new Date(Date.now() + 60 * 60 * 1000),\n      }\n    });\n  }\n\n  async someTask(data) {\n    await this.callReasoningModel(data.message);\n  }\n\n  // Use the this.sql API within the Agent to access the underlying SQLite database\n \tasync callReasoningModel(prompt: Prompt) {\n  \tinterface Prompt {\n   \t\tuserId: string;\n   \t\tuser: string;\n   \t\tsystem: string;\n   \t\tmetadata: Record<string, string>;\n\t\t}\n\n\t\tinterface History {\n\t\t\ttimestamp: Date;\n\t\t\tentry: string;\n\t\t}\n\n\t\tlet result = this.sql<History>`SELECT * FROM history WHERE user = ${prompt.userId} ORDER BY timestamp DESC LIMIT 1000`;\n\t\tlet context = [];\n\t\tfor await (const row of result) {\n\t\t\tcontext.push(row.entry);\n\t\t}\n\n\t\tconst client = new OpenAI({\n\t\t\tapiKey: this.env.OPENAI_API_KEY,\n\t\t});\n\n\t\t// Combine user history with the current prompt\n\t\tconst systemPrompt = prompt.system || 'You are a helpful assistant.';\n\t\tconst userPrompt = `${prompt.user}\\n\\nUser history:\\n${context.join('\\n')}`;\n\n\t\ttry {\n\t\t\tconst completion = await client.chat.completions.create({\n\t\t\t\tmodel: this.env.MODEL || 'o3-mini',\n\t\t\t\tmessages: [\n\t\t\t\t\t{ role: 'system', content: systemPrompt },\n\t\t\t\t\t{ role: 'user', content: userPrompt },\n\t\t\t\t],\n\t\t\t\ttemperature: 0.7,\n\t\t\t\tmax_tokens: 1000,\n\t\t\t});\n\n\t\t\t// Store the response in history\n\t\t\tthis\n\t\t\t\t.sql`INSERT INTO history (timestamp, user, entry) VALUES (${new Date()}, ${prompt.userId}, ${completion.choices[0].message.content})`;\n\n\t\t\treturn completion.choices[0].message.content;\n\t\t} catch (error) {\n\t\t\tconsole.error('Error calling reasoning model:', error);\n\t\t\tthrow error;\n\t\t}\n\t}\n\n\t// Use the SQL API with a type parameter\n\tasync queryUser(userId: string) {\n\t\ttype User = {\n\t\t\tid: string;\n\t\t\tname: string;\n\t\t\temail: string;\n\t\t};\n\t\t// Supply the type paramter to the query when calling this.sql\n\t\t// This assumes the results returns one or more User rows with \"id\", \"name\", and \"email\" columns\n\t\t// You do not need to specify an array type (`User[]` or `Array<User>`) as `this.sql` will always return an array of the specified type.\n\t\tconst user = await this.sql<User>`SELECT * FROM users WHERE id = ${userId}`;\n\t\treturn user\n\t}\n\n\t// Run and orchestrate Workflows from Agents\n  async runWorkflow(data) {\n     let instance = await env.MY_WORKFLOW.create({\n       id: data.id,\n       params: data,\n     })\n\n     // Schedule another task that checks the Workflow status every 5 minutes...\n     await this.schedule(\"*/5 * * * *\", \"checkWorkflowStatus\", { id: instance.id });\n   }\n}\n\nexport default {\n\tasync fetch(request, env, ctx): Promise<Response> {\n\t\t// Routed addressing\n\t\t// Automatically routes HTTP requests and/or WebSocket connections to /agents/:agent/:name\n\t\t// Best for: connecting React apps directly to Agents using useAgent from @cloudflare/agents/react\n\t\treturn (await routeAgentRequest(request, env)) || Response.json({ msg: 'no agent here' }, { status: 404 });\n\n\t\t// Named addressing\n\t\t// Best for: convenience method for creating or retrieving an agent by name/ID.\n\t\tlet namedAgent = getAgentByName<Env, AIAgent>(env.AIAgent, 'agent-456');\n\t\t// Pass the incoming request straight to your Agent\n\t\tlet namedResp = (await namedAgent).fetch(request);\n\t\treturn namedResp;\n\n\t\t// Durable Objects-style addressing\n\t\t// Best for: controlling ID generation, associating IDs with your existing systems,\n\t\t// and customizing when/how an Agent is created or invoked\n\t\tconst id = env.AIAgent.newUniqueId();\n\t\tconst agent = env.AIAgent.get(id);\n\t\t// Pass the incoming request straight to your Agent\n\t\tlet resp = await agent.fetch(request);\n\n\t\t// return Response.json({ hello: 'visit https://developers.cloudflare.com/agents for more' });\n\t},\n} satisfies ExportedHandler<Env>;\n</code>\n\n<code>\n// client.js\nimport { AgentClient } from \"agents/client\";\n\nconst connection = new AgentClient({\n  agent: \"dialogue-agent\",\n  name: \"insight-seeker\",\n});\n\nconnection.addEventListener(\"message\", (event) => {\n  console.log(\"Received:\", event.data);\n});\n\nconnection.send(\n  JSON.stringify({\n    type: \"inquiry\",\n    content: \"What patterns do you see?\",\n  })\n);\n</code>\n\n<code>\n// app.tsx\n// React client hook for the agents\nimport { useAgent } from \"agents/react\";\nimport { useState } from \"react\";\n\n// useAgent client API\nfunction AgentInterface() {\n  const connection = useAgent({\n    agent: \"dialogue-agent\",\n    name: \"insight-seeker\",\n    onMessage: (message) => {\n      console.log(\"Understanding received:\", message.data);\n    },\n    onOpen: () => console.log(\"Connection established\"),\n    onClose: () => console.log(\"Connection closed\"),\n  });\n\n  const inquire = () => {\n    connection.send(\n      JSON.stringify({\n        type: \"inquiry\",\n        content: \"What insights have you gathered?\",\n      })\n    );\n  };\n\n  return (\n    <div className=\"agent-interface\">\n      <button onClick={inquire}>Seek Understanding</button>\n    </div>\n  );\n}\n\n// State synchronization\nfunction StateInterface() {\n  const [state, setState] = useState({ counter: 0 });\n\n  const agent = useAgent({\n    agent: \"thinking-agent\",\n    onStateUpdate: (newState) => setState(newState),\n  });\n\n  const increment = () => {\n    agent.setState({ counter: state.counter + 1 });\n  };\n\n  return (\n    <div>\n      <div>Count: {state.counter}</div>\n      <button onClick={increment}>Increment</button>\n    </div>\n  );\n}\n</code>\n\n<configuration>\n\t{\n  \"durable_objects\": {\n    \"bindings\": [\n      {\n        \"binding\": \"AIAgent\",\n        \"class_name\": \"AIAgent\"\n      }\n    ]\n  },\n  \"migrations\": [\n    {\n      \"tag\": \"v1\",\n      // Mandatory for the Agent to store state\n      \"new_sqlite_classes\": [\"AIAgent\"]\n    }\n  ]\n}\n</configuration>\n<key_points>\n\n- Imports the `Agent` class from the `agents` package\n- Extends the `Agent` class and implements the methods exposed by the `Agent`, including `onRequest` for HTTP requests, or `onConnect` and `onMessage` for WebSockets.\n- Uses the `this.schedule` scheduling API to schedule future tasks.\n- Uses the `this.setState` API within the Agent for syncing state, and uses type parameters to ensure the state is typed.\n- Uses the `this.sql` as a lower-level query API.\n- For frontend applications, uses the optional `useAgent` hook to connect to the Agent via WebSockets\n\n</key_points>\n</example>\n\n<example id=\"workers-ai-structured-outputs-json\">\n<description>\nWorkers AI supports structured JSON outputs with JSON mode, which supports the `response_format` API provided by the OpenAI SDK.\n</description>\n<code language=\"typescript\">\nimport { OpenAI } from \"openai\";\n\ninterface Env {\n\tOPENAI_API_KEY: string;\n}\n\n// Define your JSON schema for a calendar event\nconst CalendarEventSchema = {\n  type: 'object',\n  properties: {\n    name: { type: 'string' },\n    date: { type: 'string' },\n    participants: { type: 'array', items: { type: 'string' } },\n  },\n  required: ['name', 'date', 'participants']\n};\n\nexport default {\n\tasync fetch(request: Request, env: Env) {\n\t\tconst client = new OpenAI({\n\t\t\tapiKey: env.OPENAI_API_KEY,\n\t\t\t// Optional: use AI Gateway to bring logs, evals & caching to your AI requests\n\t\t\t// https://developers.cloudflare.com/ai-gateway/usage/providers/openai/\n\t\t\t// baseUrl: \"https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/openai\"\n\t\t});\n\n\t\tconst response = await client.chat.completions.create({\n\t    model: 'gpt-4o-2024-08-06',\n\t    messages: [\n\t      { role: 'system', content: 'Extract the event information.' },\n\t      { role: 'user', content: 'Alice and Bob are going to a science fair on Friday.' },\n\t    ],\n\t\t\t// Use the `response_format` option to request a structured JSON output\n\t    response_format: {\n\t\t\t\t// Set json_schema and provide ra schema, or json_object and parse it yourself\n\t      type: 'json_schema',\n\t      schema: CalendarEventSchema, // provide a schema\n\t    },\n\t  });\n\n\t\t// This will be of type CalendarEventSchema\n\t\tconst event = response.choices[0].message.parsed;\n\n\t\treturn Response.json({\n\t\t\t\"calendar_event\": event,\n\t\t})\n\t}\n}\n</code>\n<configuration>\n{\n  \"name\": \"my-app\",\n\t\"main\": \"src/index.ts\",\n  \"compatibility_date\": \"$CURRENT_DATE\",\n  \"observability\": {\n    \"enabled\": true\n  }\n}\n</configuration>\n<key_points>\n\n- Defines a JSON Schema compatible object that represents the structured format requested from the model\n- Sets `response_format` to `json_schema` and provides a schema to parse the response\n- This could also be `json_object`, which can be parsed after the fact.\n- Optionally uses AI Gateway to cache, log and instrument requests and responses between a client and the AI provider/API.\n\n</key_points>\n</example>\n\n</code_examples>\n\n<api_patterns>\n\n<pattern id=\"websocket_coordination\">\n<description>\nFan-in/fan-out for WebSockets. Uses the Hibernatable WebSockets API within Durable Objects. Does NOT use the legacy addEventListener API.\n</description>\n<implementation>\nexport class WebSocketHibernationServer extends DurableObject {\n  async fetch(request: Request, env: Env, ctx: ExecutionContext) {\n    // Creates two ends of a WebSocket connection.\n    const webSocketPair = new WebSocketPair();\n    const [client, server] = Object.values(webSocketPair);\n\n    // Call this to accept the WebSocket connection.\n    // Do NOT call server.accept() (this is the legacy approach and is not preferred)\n    this.ctx.acceptWebSocket(server);\n\n    return new Response(null, {\n          status: 101,\n          webSocket: client,\n    });\n},\n\nasync webSocketMessage(ws: WebSocket, message: string | ArrayBuffer): void | Promise<void> {\n  // Invoked on each WebSocket message.\n  ws.send(message)\n},\n\nasync webSocketClose(ws: WebSocket, code: number, reason: string, wasClean: boolean) void | Promise<void> {\n  // Invoked when a client closes the connection.\n  ws.close(code, \"<message>\");\n},\n\nasync webSocketError(ws: WebSocket, error: unknown): void | Promise<void> {\n  // Handle WebSocket errors\n}\n}\n</implementation>\n</pattern>\n</api_patterns>\n\n<user_prompt>\n{user_prompt}\n</user_prompt>\n",
                  "type": "text"
                },
                "role": "user"
              }
            ]
          }
        },
        "prompt_name": "workers-prompt-full",
        "url": "https://docs.mcp.cloudflare.com/mcp"
      },
      "latency_ms": 127.66,
      "status": "ok"
    },
    "prompts_list": {
      "details": {
        "headers": {
          "content-type": "text/event-stream"
        },
        "http_status": 200,
        "payload": {
          "id": 3,
          "jsonrpc": "2.0",
          "result": {
            "prompts": [
              {
                "description": "Detailed prompt for generating Cloudflare Workers code (and other developer platform products) from https://developers.cloudflare.com/workers/prompt.txt",
                "name": "workers-prompt-full"
              }
            ]
          }
        },
        "url": "https://docs.mcp.cloudflare.com/mcp"
      },
      "latency_ms": 31.37,
      "status": "ok"
    },
    "protocol_version_probe": {
      "details": {
        "claimed_version": "2025-03-26",
        "lag_days": 244,
        "latest_known_version": "2025-11-25",
        "releases_behind": 2,
        "validator_protocol_version": "2025-03-26"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "provenance_divergence_probe": {
      "details": {
        "direct_official_match": true,
        "drift_fields": [],
        "metadata_document_count": 1,
        "registry_homepage": null,
        "registry_repository": null,
        "registry_title": null,
        "registry_version": null,
        "server_card_homepage": null,
        "server_card_repository": null,
        "server_card_title": null,
        "server_card_version": null
      },
      "latency_ms": null,
      "status": "ok"
    },
    "request_association_probe": {
      "details": {
        "reason": "no_request_association_capabilities_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resource_read": {
      "details": {
        "reason": "not_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resources_list": {
      "details": {
        "headers": {
          "content-type": "text/event-stream"
        },
        "http_status": 200,
        "payload": {
          "error": {
            "code": -32601,
            "message": "Method not found"
          },
          "id": 5,
          "jsonrpc": "2.0"
        },
        "reason": "not_supported",
        "url": "https://docs.mcp.cloudflare.com/mcp"
      },
      "latency_ms": 27.24,
      "status": "missing"
    },
    "server_card": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://docs.mcp.cloudflare.com/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "url": "https://docs.mcp.cloudflare.com/.well-known/mcp/server-card.json"
      },
      "latency_ms": 37.12,
      "status": "error"
    },
    "session_resume_probe": {
      "details": {
        "protocol_version": "2025-03-26",
        "reason": "no_session_id",
        "resume_expected": true,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "step_up_auth_probe": {
      "details": {
        "auth_required_checks": [],
        "broad_scopes": [],
        "challenge_headers": [],
        "minimal_scope_documented": false,
        "oauth_present": false,
        "scope_specificity_ratio": 0.0,
        "step_up_signals": [],
        "supported_scopes": []
      },
      "latency_ms": null,
      "status": "missing"
    },
    "tool_snapshot_probe": {
      "details": {
        "added": [],
        "changed_outputs": [],
        "current_tool_count": 2,
        "previous_tool_count": 2,
        "removed": [],
        "similarity": 1.0
      },
      "latency_ms": null,
      "status": "ok"
    },
    "tools_list": {
      "details": {
        "headers": {
          "content-type": "text/event-stream"
        },
        "http_status": 200,
        "payload": {
          "id": 2,
          "jsonrpc": "2.0",
          "result": {
            "tools": [
              {
                "annotations": {
                  "annotations": {
                    "readOnlyHint": true
                  },
                  "title": "Search Cloudflare docs"
                },
                "description": "Search the Cloudflare documentation.\n\n\t\tThis tool should be used to answer any question about Cloudflare products or features, including:\n\t\t- Workers, Pages, R2, Images, Stream, D1, Durable Objects, KV, Workflows, Hyperdrive, Queues\n\t\t- AI Search, Workers AI, Vectorize, AI Gateway, Browser Rendering\n\t\t- Zero Trust, Access, Tunnel, Gateway, Browser Isolation, WARP, DDOS, Magic Transit, Magic WAN\n\t\t- CDN, Cache, DNS, Zaraz, Argo, Rulesets, Terraform, Account and Billing\n\n\t\tResults are returned as semantically similar chunks to the query.\n\t\t",
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "query": {
                      "type": "string"
                    }
                  },
                  "required": [
                    "query"
                  ],
                  "type": "object"
                },
                "name": "search_cloudflare_documentation"
              },
              {
                "annotations": {
                  "annotations": {
                    "readOnlyHint": true
                  },
                  "title": "Get Pages migration guide"
                },
                "description": "ALWAYS read this guide before migrating Pages projects to Workers.",
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {},
                  "type": "object"
                },
                "name": "migrate_pages_to_workers_guide"
              }
            ]
          }
        },
        "url": "https://docs.mcp.cloudflare.com/mcp"
      },
      "latency_ms": 29.58,
      "status": "ok"
    },
    "transport_compliance_probe": {
      "details": {
        "bad_protocol_error": null,
        "bad_protocol_headers": {
          "content-type": "application/json"
        },
        "bad_protocol_payload": {
          "error": {
            "code": -32000,
            "message": "Bad Request: Unsupported MCP-Protocol-Version: 1999-99-99. Supported versions: 2025-03-26, 2025-06-18"
          },
          "id": null,
          "jsonrpc": "2.0"
        },
        "bad_protocol_status_code": 400,
        "delete_error": null,
        "delete_status_code": null,
        "expired_session_error": null,
        "expired_session_status_code": null,
        "issues": [
          "missing_session_id",
          "missing_protocol_header"
        ],
        "last_event_id_visible": false,
        "protocol_header_present": false,
        "requested_protocol_version": "2025-03-26",
        "session_id_present": false,
        "transport": "streamable-http"
      },
      "latency_ms": 23.91,
      "status": "warning"
    },
    "utility_coverage_probe": {
      "details": {
        "completions": {
          "advertised": true,
          "live_probe": "not_executed",
          "sample_target": null
        },
        "initialize_capability_keys": [
          "completions",
          "prompts",
          "tools"
        ],
        "pagination": {
          "metadata_signal": false,
          "next_cursor_methods": [],
          "supported": false
        },
        "tasks": {
          "advertised": false,
          "http_status": 200,
          "probe_status": "missing"
        }
      },
      "latency_ms": 12.98,
      "status": "warning"
    }
  },
  "failures": {
    "oauth_authorization_server": {
      "reason": "no_authorization_server"
    },
    "oauth_protected_resource": {
      "error": "Client error '404 Not Found' for url 'https://docs.mcp.cloudflare.com/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "url": "https://docs.mcp.cloudflare.com/.well-known/oauth-protected-resource"
    },
    "openid_configuration": {
      "reason": "no_authorization_server"
    },
    "server_card": {
      "error": "Client error '404 Not Found' for url 'https://docs.mcp.cloudflare.com/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "url": "https://docs.mcp.cloudflare.com/.well-known/mcp/server-card.json"
    }
  },
  "remote_url": "https://docs.mcp.cloudflare.com/mcp",
  "server_card_payload": null,
  "server_identifier": "com.cloudflare.mcp/mcp"
}

Known versions

Validation history

7 day score delta
+0.0
30 day score delta
+0.0
Recent healthy ratio
100%
Freshness
605.4h
TimestampStatusScoreLatencyTools
Apr 09, 2026 12:28:45 AM UTC Healthy 74.9 472.9 ms 2
Apr 08, 2026 12:26:33 AM UTC Healthy 74.9 505.6 ms 2
Apr 07, 2026 12:25:42 AM UTC Healthy 74.9 511.9 ms 2
Apr 06, 2026 12:24:46 AM UTC Healthy 74.9 471.9 ms 2
Apr 05, 2026 12:22:43 AM UTC Healthy 74.9 437.2 ms 2
Apr 04, 2026 12:21:34 AM UTC Healthy 74.9 426.8 ms 2
Apr 03, 2026 12:20:13 AM UTC Healthy 74.9 397.4 ms 2
Apr 02, 2026 12:10:22 AM UTC Healthy 74.9 544.3 ms 2

Validation timeline

ValidatedSummaryScoreProtocolAuth modeToolsHigh-risk toolsChanges
Apr 09, 2026 12:28:45 AM UTC Healthy 74.9 2025-03-26 public 2 1 none
Apr 08, 2026 12:26:33 AM UTC Healthy 74.9 2025-03-26 public 2 1 none
Apr 07, 2026 12:25:42 AM UTC Healthy 74.9 2025-03-26 public 2 1 none
Apr 06, 2026 12:24:46 AM UTC Healthy 74.9 2025-03-26 public 2 1 none
Apr 05, 2026 12:22:43 AM UTC Healthy 74.9 2025-03-26 public 2 1 none
Apr 04, 2026 12:21:34 AM UTC Healthy 74.9 2025-03-26 public 2 1 none
Apr 03, 2026 12:20:13 AM UTC Healthy 74.9 2025-03-26 public 2 1 none
Apr 02, 2026 12:10:22 AM UTC Healthy 74.9 2025-03-26 public 2 1 none
Mar 31, 2026 11:32:51 PM UTC Healthy 74.9 2025-03-26 public 2 1 none
Mar 30, 2026 11:25:10 PM UTC Healthy 74.9 2025-03-26 public 2 1 none
Mar 29, 2026 11:17:25 PM UTC Healthy 74.9 2025-03-26 public 2 1 none
Mar 28, 2026 09:58:35 PM UTC Healthy 74.9 2025-03-26 public 2 1 none

Recent validation runs

StartedStatusSummaryLatencyChecks
Apr 09, 2026 12:28:45 AM UTC Completed Healthy 472.9 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
Apr 08, 2026 12:26:32 AM UTC Completed Healthy 505.6 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
Apr 07, 2026 12:25:42 AM UTC Completed Healthy 511.9 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
Apr 06, 2026 12:24:46 AM UTC Completed Healthy 471.9 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
Apr 05, 2026 12:22:42 AM UTC Completed Healthy 437.2 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
Apr 04, 2026 12:21:33 AM UTC Completed Healthy 426.8 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
Apr 03, 2026 12:20:12 AM UTC Completed Healthy 397.4 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
Apr 02, 2026 12:10:22 AM UTC Completed Healthy 544.3 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
Mar 31, 2026 11:32:50 PM UTC Completed Healthy 480.2 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
Mar 30, 2026 11:25:10 PM UTC Completed Healthy 351.3 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe