
Ietf Mcp
io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 30, 2026
Use this MCP server to IETF documents, RFCs, Internet-Drafts, and working groups. Tools include...
Overview
Read-only MCP server that lets an assistant search IETF RFCs and Internet-Drafts, look up documents, and find working groups and recent meetings via the…
- What you can do
- Search RFCs and Internet-Drafts by name or query
- Look up a specific document by name, such as rfc9110
- Find IETF working groups by name
- List recent public IETF meetings
- When to use it
- Useful when you need protocol research or standards context while working: checking an RFC's metadata, discovering drafts, or identifying the working group and recent meetings behind a specification. It is read-only, so it suits lookup rather than standards authoring.
- Requirements
- Runs as a local stdio process installed from the npm package ietf-mcp (Node.js). No API key or authentication is needed; it relies on the public IETF Datatracker API, so network access is required.
Installation
In SourceWeft
- Open Ietf Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
ietf-mcp
A focused MCP interface to the IETF Datatracker for protocol research, RFC lookup, Internet-Draft discovery, working-group context, and meeting history.
Tools
search_documents: search RFCs and Internet-Drafts by name or query.get_document: look up a document by name such asrfc9110.search_working_groups: find IETF working groups by name.list_recent_meetings: list recent public IETF meetings.
The server is read-only, keyless, and uses the public Datatracker API. It returns metadata and public records; it does not submit drafts, edit working-group records, or perform standards actions.
Run
Source: README.md at commit 8914740
Tools
0Version history
1- v1.0.0LatestSep 22, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.