internet-standards-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the hosted Streamable HTTP server when running with --http | 3000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| iana_lookupA | Looks up an entry in an IANA registry (HTTP status codes, fields, methods; media types; URI schemes; port numbers; TLS cipher suites; link relations; DNS record types) by exact value or name, else by text. Returns the entry and its defining RFC section. |
| rfc_infoA | For up to 20 RFCs (RFC 2616, BCP 14, STD 97 or a draft name): title, status, whether it is current, what obsoletes it and the current replacements at the end of that chain, what updates it, and links. Use before citing or implementing an RFC. |
| rfc_sectionA | Returns the exact text of one RFC section (by number like 15.5.5 or by title) with the verified errata that apply to it; with find, lists the sections containing a phrase; with neither, the table of contents. Warns when the RFC is obsolete. |
| search_rfcsA | Finds RFCs by topic words in titles, keywords and abstracts; current documents rank above the ones they replaced. Returns number, title, status, year and what obsoletes each. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clear, distinct purpose: IANA registry lookup vs. RFC discovery, metadata retrieval, and section text extraction. There is no meaningful overlap between any two tools.
All names use lowercase with underscores styles vary between object+verb (iana_lookup), object+noun (rfc_info, rfc_section), and verb+object (search_rfcs). The pattern is not perfectly uniform but remains predictable and readable.
At 4 tools, the server is compact but covers the core references for internet standards. Slightly thin, but each tool serves a necessary, non-redundant function.
The set covers IANA lookups, RFC searching, metadata validation, and section-level text with errata. Missing full RFC text retrieval or a registry listing, but the main workflows are covered without major dead ends.