# Reported issues for iana-registries-mcp-server Pod holds 12 of 12 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects. Back to [iana-registries-mcp-server](/mcp/iana-registries-mcp-server). ## Most discussed ### bug(upstream): plain-http redirect on iana.org followed, then failed as retryable ### Server version 0.1.1 ### mcp-ts-core version 0.13.10 ### Runtime Node.js ### Runtime version Node 26.5.0 ### Transport HTTP (Streamable HTTP) ### OS macOS 27.0 ### Description The protocols index links `address-literal-tags`, but its XML URL answers `301` to a plain-http URL on the same host (`http://www.iana.org/assignments/smtp/smtp.xml`, which serves the registry over http with `200`). The upstream client follows redirects automatically, so it has already made the plain-http… [Read the thread](https://github.com/cyanheads/iana-registries-mcp-server/issues/13) · 2026-10-01 · closed · 2 comments ### bug(format): fields after a quoted block render inside the blockquote ### Server version 0.1.0 ### mcp-ts-core version 0.13.10 ### Runtime Node.js ### Runtime version Node 26.5.0 ### Transport HTTP (Streamable HTTP) ### Description `format()` puts server-authored lines directly after a `quote()` block with no blank line. Under CommonMark's laziness rule (spec §5.1), a paragraph line that follows a `>` line continues the blockquote, so those fields render inside the quoted third-party text, blurring the boundary the quoting exists to mark. ### Steps to… [Read the thread](https://github.com/cyanheads/iana-registries-mcp-server/issues/4) · 2026-10-01 · closed · 2 comments ### bug(iana_lookup_pen): organization search for "cisco" misses PEN 9 (ciscoSystems) ### Server version 0.1.0 ### mcp-ts-core version 0.13.10 ### Runtime Node.js ### Runtime version Node 26.5.0 ### Transport HTTP (Streamable HTTP) ### Description `iana_lookup_pen` organization search does not find PEN 9, Cisco's enterprise number (the `1.3.6.1.4.1.9` arc), from "cisco" or "cisco systems". The registry writes the organization as the single camelCase token `ciscoSystems`, and the token normalizer does not split lower-to-upper case boundaries, so only the exact joined… [Read the thread](https://github.com/cyanheads/iana-registries-mcp-server/issues/3) · 2026-10-01 · closed · 2 comments ### bug(search): matches past the max limit are unreachable, and the notice still says raise limit ### Server version 0.1.0 ### mcp-ts-core version 0.13.10 ### Runtime Node.js ### Runtime version Node 26.5.0 ### Transport HTTP (Streamable HTTP) ### Description List modes have no offset or cursor, so matches past the maximum `limit` cannot be retrieved. At the maximum, the notice still tells the caller to raise `limit`. Affected: keyword/organization/description modes of `iana_lookup_port`, `iana_lookup_media_type`, `iana_lookup_pen` (confirmed past the cap), and… [Read the thread](https://github.com/cyanheads/iana-registries-mcp-server/issues/2) · 2026-10-01 · closed · 2 comments ### bug(iana_get_registry_records): record-less YANG and MIB registries fail as retryable or answer empty ### Server version 0.1.0 ### mcp-ts-core version 0.13.10 ### Runtime Node.js ### Runtime version Node 26.5.0 ### Transport HTTP (Streamable HTTP) ### Description Registries that `iana_search_registries` lists but that hold no `` elements are mishandled. The 26 "YANG Modules" registries (`iana-tls-cipher-suite-algs` is the second hit for "tls cipher") publish XML with only metadata: title, description, xrefs, no `` pointer. The read is treated as `upstream_unreadable`,… [Read the thread](https://github.com/cyanheads/iana-registries-mcp-server/issues/1) · 2026-10-01 · closed · 2 comments ### bug(iana_lookup_media_type): "No registration template available." page reported as a template read ### Server version 0.1.1 ### mcp-ts-core version 0.13.10 ### Runtime Node.js ### Runtime version Node 26.5.0 ### Transport HTTP (Streamable HTTP) ### OS macOS 27.0 ### Description For some registered types, IANA's template URL answers HTTP 200 with the 35-byte placeholder `No registration template available.` instead of a template. `iana_lookup_media_type` reads that as a template with no statements and returns `template: { fetched: true }`, the same shape as a real template that… [Read the thread](https://github.com/cyanheads/iana-registries-mcp-server/issues/12) · 2026-10-01 · closed · 1 comment ### feat(iana_lookup_media_type): say keyword search does not cover file extensions ### Use case "Which media type is a `.jpg` / `.mp3` / `.docx` file?" is a common media type question, and `iana_lookup_media_type` keyword mode cannot answer it: keywords match registered type names, and the registry carries no file extensions. Of 61 common extensions whose type is registered (registry of 2026-09-24), 22 miss with "Try fewer words." though they are one word (`mp3`, `docx`, `txt`), and 8 return `found: true` without the type the extension usually denotes (`jpg` returns only… [Read the thread](https://github.com/cyanheads/iana-registries-mcp-server/issues/11) · 2026-10-01 · closed · 1 comment ### feat(iana_get_rfc_status): accept tools.ietf.org, ietf.org/rfc, and draft archive URLs ### Use case URL and file-name forms common in documentation and source comments come back `kind: "unsupported"` from `iana_get_rfc_status`, though each names exactly one document, and the guidance ("neither an RFC number nor a draft name") does not say what the tool accepts: | input | names | |:--|:--| | `https://tools.ietf.org/html/rfc7231` | RFC 7231 | | `https://www.ietf.org/rfc/rfc2616.txt` | RFC 2616 | | `https://www.ietf.org/archive/id/draft-ietf-httpbis-semantics-19.html` |… [Read the thread](https://github.com/cyanheads/iana-registries-mcp-server/issues/10) · 2026-10-01 · closed · 1 comment ## Most recent ### feat(iana_get_registry_records): exact match on any column, consistent key, hex code-point forms ### Use case People usually hold a registry entry's mnemonic or its wire form, not the key column. `iana_get_registry_records` `value` matches only the key, so common lookups miss, and a row without the `value_field` column is keyed by its first field instead, which returns partial answers. Measured 2026-10-01: | registry / input | result | |:--|:--| | `ieee-802-numbers-1` value `86DD` | miss: key is `type_decimal`, `type_hex` holds `86DD` | | `dns-parameters-4` `AAAA`, `protocol-numbers`… [Read the thread](https://github.com/cyanheads/iana-registries-mcp-server/issues/9) · 2026-10-01 · closed · 1 comment ### bug(iana_get_registry_records): root notes and nested tables dropped on sub-registry reads ### Server version 0.1.1 ### mcp-ts-core version 0.13.10 ### Runtime Node.js ### Runtime version Node 26.5.0 ### Transport HTTP (Streamable HTTP) ### OS macOS 27.0 ### Description `iana_get_registry_records` drops context held by the tables around the one it reads: 1. A sub-registry read never returns the root's notes. `iana-ipv6-special-registry` records cite root footnotes (`"source": "False 1"`) that its default read, which picks the one sub-registry, never returns;… [Read the thread](https://github.com/cyanheads/iana-registries-mcp-server/issues/8) · 2026-10-01 · closed · 1 comment ### bug(iana_search_registries): main registries missed or ranked past the first page ### Server version 0.1.1 ### mcp-ts-core version 0.13.10 ### Runtime Node.js ### Runtime version Node 26.5.0 ### Transport HTTP (Streamable HTTP) ### OS macOS 27.0 ### Description `iana_search_registries` matches every query word as a whole token, with no singular/plural folding, and orders results as exact-id hits then index order. Common queries miss the main registry or bury it, and four registry/sub-registry pairs come back twice. The example in the tool description and the… [Read the thread](https://github.com/cyanheads/iana-registries-mcp-server/issues/7) · 2026-10-01 · closed · 1 comment ### bug(iana_get_rfc_status): series membership never returned; BCP/STD/FYI ids dead-end ### Server version 0.1.1 ### mcp-ts-core version 0.13.10 ### Runtime Node.js ### Runtime version Node 26.5.0 ### Transport HTTP (Streamable HTTP) ### OS macOS 27.0 ### Description `rfc.see_also` is described as "Related documents, e.g. its BCP or STD", but it relays the RFC Editor JSON `see_also`, which is always empty: `[]` on all 27 RFCs sampled (19 BCP, STD, or FYI members, 8 non-members), and no `see-also` on any of the 9,843 entries in the RFC Editor's `rfc-index.xml`… [Read the thread](https://github.com/cyanheads/iana-registries-mcp-server/issues/6) · 2026-10-01 · closed · 1 comment The remaining reports are on [the project's issue tracker](https://github.com/cyanheads/iana-registries-mcp-server/issues).