generate_checklist
Generate RFC implementation checklist in Markdown format.
LABSCO SUMMARY
Extracting the MUST, SHOULD and MAY set is the tool that changes how an RFC gets used at all.
get_requirements returns normative requirements structured and filterable by level, which turns a spec from prose into a list an implementation can be held against; generate_checklist writes that list out as Markdown for a specific role and section set, and validate_statement runs a claim back through it. The metadata comes from the IETF Datatracker rather than the document text alone, so category, stream and publication date carry the authoritative record — with includeAuthors flagged as costing extra calls, which is a setting to make deliberately rather than by default.
What it is
An RFC reader with 7 tools that return a document's structure and metadata, extract its normative requirements and definitions, map its references, generate an implementation checklist, and validate a statement against it.
What you get
- get_rfc_structure returns the section hierarchy with metadata enriched from the IETF Datatracker — category, stream, publication date and abstract — and includeAuthors to resolve author names at the cost of extra API calls.
- get_requirements extracts normative requirements in structured form, filterable by level across MUST, SHOULD and MAY and by section.
- get_definitions returns term definitions from an RFC, optionally for one term.
- get_rfc_dependencies returns the reference graph, normative and informative, with includeReferencedBy for the inbound direction.
- get_related_sections returns the sections related to a given one.
- generate_checklist produces an implementation checklist in Markdown for a chosen role, over chosen sections, optionally including subsections.
- validate_statement checks whether a statement complies with an RFC's requirements.
Requirements
Nothing — no account, no key. includeAuthors on get_rfc_structure costs extra Datatracker API calls.
Setup effort
One command — npx -y @shuji-bonji/rfcxml-mcp
USE CASES
01
Pulling the normative requirements out of a spec
Filtering by MUST, SHOULD or MAY and by section turns a long document into the obligations that apply to the part you are building.
02
Turning a spec into something an implementation can be checked against
The checklist is generated for a role and a section set, which keeps it to the obligations that side of the protocol actually carries.
03
Working out what else you have to read
Normative and informative references are distinguished, and the inbound direction shows which documents depend on this one.
04
Settling an argument about what a term means
Definitions come out as their own list rather than being hunted through the prose, and can be narrowed to one term.
05
Checking whether a design decision actually complies
The statement goes in as written and comes back checked against the document's requirements, rather than against a recollection of them.
7 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_definitions
Get term definitions from RFC.
get_related_sections
Get sections related to the specified section.
get_requirements
Extract normative requirements (MUST/SHOULD/MAY) from RFC in structured format.
get_rfc_dependencies
Get RFC reference relationships (normative/informative).
get_rfc_structure
Get RFC section hierarchy and metadata. Metadata is enriched from the IETF Datatracker API (category, stream, publication date, abstract). Pass includeAuthors=true to also resolve author names (incurs extra API calls).
validate_statement
Validate if a statement complies with RFC requirements.
BEFORE YOU INSTALL
What to know first
Tools you get
7 tools when we connected. The README lists the same seven, and all of them ship in the current release.
Requires
npx on PATH
Where it runs
Both documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 7 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @shuji-bonji/rfcxml-mcpMCP Clients
Claude Desktop, Claude Code
JSON
{
"mcpServers": {
"rfcxml": {
"command": "npx",
"args": [
"-y",
"@shuji-bonji/rfcxml-mcp"
]
}
}
}
