Home / MCP registry index / io.github.duckframework/duckframework-mcp
Duck Framework MCP
io.github.duckframework/duckframework-mcp in the official MCP registry.
Endpoint https://duckframework.com/mcp. Source: github.com/duckframework/duck.
The registry describes it as: Official Duck Framework MCP server for AI-assisted development and project scaffolding.
We read its 13 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
fetch_ai_guide get_ai_guides get_blueprint_locations get_blueprint_structure get_component_api get_project_structure lint_component_code list_doc_categories plan_feature reindex_docs scaffold_blueprint scaffold_project search_docs
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-duckframework-duckframework-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.