Duck Framework MCP
REMOTE · DUCKFRAMEWORK.COM
Official Duck Framework MCP server for AI-assisted development and project scaffolding.
Available components
Last scanned (2 hours ago)
Scores higher than 53% of remote servers
Unreachable for 1 day in a row. Last reached 4 Nov 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security14
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.40 → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- HSTS header: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 13 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Stability: unverified → 0.30 ▲ functional
- 31 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.23 → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://duckframework.com/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of duckframework.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| duckframework.com. | present | 5307 | 13 | Verified |
| duckframework.com. | Verified address RRset verified with the apex keys |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://duckframework.com/mcp | Unreachable | ||
| http (plaintext) | http://duckframework.com/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fetch_ai_guide ~62
Fetch an official Duck Framework AI guide. Use this after get_ai_guides() to retrieve the full guide content for AI-assisted Duck Framework development. Always read the relevant guide before generating code instead of relying on memory.
| Name | Type | Req | Description |
|---|---|---|---|
| guide | string | yes | – |
No output schema declared.
No examples provided.
get_ai_guides ~40
List available Duck Framework AI guides. Use this to discover available guides before fetching one with fetch_ai_guide(). Returns guide identifiers and their descriptions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_blueprint_locations ~36
Explain where Duck Framework blueprints can be located. Describes the supported blueprint layouts and when each organization approach is appropriate.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_blueprint_structure ~53
Return the standard internal structure of a Duck Framework blueprint. Use this before generating a new blueprint or adding files to an existing one to understand where components, pages, templates, automations, and views belong.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_component_api ~80
Look up a built-in Duck Framework component API. Returns the confirmed import path, container type, and supported keyword arguments for a component without requiring the full HTML components guide to be loaded. Use this before using any component that has not already been confirmed. Returns close-name suggestions when the component does not exist.
| Name | Type | Req | Description |
|---|---|---|---|
| component_name | string | yes | – |
No output schema declared.
No examples provided.
get_project_structure ~34
Return the standard Duck Framework project directory structure. Use this before creating or modifying projects to understand where files and directories belong.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lint_component_code ~96
Check Duck Framework component or page code for common mistakes. Detects known patterns such as incorrect component imports, invalid page imports, incorrect Heading usage, leading-underscore method names, and separator comments. This is a pattern check for known issues, not a complete correctness validator. An empty result only means no known issues were detected. Run this on generated component code before presenting it as final.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
No output schema declared.
No examples provided.
list_doc_categories ~39
List all Duck Framework documentation categories and their pages. Use this when browsing available documentation without a specific search query.
| Name | Type | Req | Description |
|---|---|---|---|
| version | string | – | – |
No output schema declared.
No examples provided.
plan_feature ~62
Analyze a Duck Framework feature request and create an implementation plan. Returns relevant documentation to read and a suggested order of operations before writing code. Use this before implementing non-trivial Duck Framework features.
| Name | Type | Req | Description |
|---|---|---|---|
| request | string | yes | – |
| version | string | – | – |
No output schema declared.
No examples provided.
reindex_docs ~71
Rebuild the Duck Framework documentation index. Crawls the live documentation sitemap for a given version and merges the result in: curated tags/summary/category are preserved, new pages are added, and pages no longer in the sitemap are removed. Requires the admin scope.
| Name | Type | Req | Description |
|---|---|---|---|
| version | string | – | – |
No output schema declared.
No examples provided.
scaffold_blueprint ~111
Scaffold a new Duck Framework blueprint. Generates a blueprint structure containing blueprint.py, views.py, and optional UI, template, and static directories following the documented Duck blueprint conventions. Returns generated file contents and the settings configuration needed to register the blueprint. This tool does not write files.
| Name | Type | Req | Description |
|---|---|---|---|
| blueprint_name | string | yes | – |
| enable_static_dir | string | – | – |
| enable_template_dir | string | – | – |
| prepend_name_to_urls | string | – | – |
| urlpatterns | string | – | – |
No output schema declared.
No examples provided.
scaffold_project ~89
Scaffold a new Duck Framework project. Returns the required CLI commands and generated file contents for supported features with confirmed APIs. Unsupported features return documentation guidance instead of generated code to avoid guessing framework APIs. This tool does not write files. It only returns generated content for the calling client to add to the user's project directory.
| Name | Type | Req | Description |
|---|---|---|---|
| features | string | – | – |
| project_name | string | yes | – |
No output schema declared.
No examples provided.
search_docs ~75
Fuzzy-search the Duck Framework documentation. Use this whenever the correct documentation page for a feature is unknown. Returns ranked matches containing title, URL, category, summary, and relevance score.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| query | string | yes | – |
| top_k | string | – | – |
| version | string | – | – |
No output schema declared.
No examples provided.
How do I install the Duck Framework MCP server?
Duck Framework MCP is a hosted endpoint at https://duckframework.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · duckframework.com
claude mcp add --transport http duckframework-duckframework-mcp 'https://duckframework.com/mcp'
What is the Duck Framework MCP server?
Duck Framework MCP is listed in the public MCP registry as io.github.duckframework/duckframework-mcp. Official Duck Framework MCP server for AI-assisted development and project scaffolding. This page covers its hosted endpoint (https://duckframework.com/mcp).
Is the Duck Framework MCP server safe to use?
Duck Framework MCP scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Duck Framework MCP server expose?
Duck Framework MCP exposes 13 tools: fetch_ai_guide, get_ai_guides, get_blueprint_locations, get_blueprint_structure, get_component_api, and 8 more. Their descriptions and schemas cost roughly 848 tokens of context every time the server is loaded.
Does the Duck Framework MCP server require authentication?
Its publisher declares no required credentials for Duck Framework MCP. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Duck Framework MCP server still maintained?
Duck Framework MCP is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.