@pipeworx/rfc-editor

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/rfc-editor’s. Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 6

RFC Editor MCP — fetch full RFC text + metadata directly from rfc-editor.org (complementary to ietf-datatracker which deals in metadata). Keyless.

Tools

• rfc_text(number) — full RFC plain text
• rfc_metadata(number) — RFC index entry metadata (title, authors, status, obsoletes/updates)
• errata(number?) — known errata (per-RFC or all)
• bcp(number) — Best Current Practice mapping (BCP → RFC list)
• std(number) — STD mapping (STD → RFC list)
• search(query, status?) — substring search in title/abstract via rfc-editor index

Data source

https://www.rfc-editor.org/rfc/rfc<N>.txt etc., plus the rfc-index.xml + errata feed.

Tools

• rfc_text — Full RFC plain text.
• rfc_metadata — RFC index entry metadata.
• errata — Known errata.
• bcp — BCP → RFC list.
• std — STD → RFC list.
• search — Substring search in title/abstract.