io.github.cyanheads/iana-registries-mcp-server

Est-ce que io.github.cyanheads/iana-registries-mcp-server est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.cyanheads/iana-registries-mcp-server » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 10 outils

• iana_get_registry_records≈ 3326 tokens

  Read records from any IANA XML registry by id, e.g. registry "tls-parameters" with subregistry "tls-parameters-4" (TLS Cipher Suites), "protocol-numbers", "http-methods", or "cbor-tags"; an iana.org/assignments URL also works. Filter with `value` (exact match on the key column, or on the column `field` names; digits compare by number with a cell of digits ("0443" finds "443") and one 0x token with a one-token 0x cell ("0x5" finds "0x05"), each also matching its own kind of range row ("105-199", "0x11-0xff"); other 0x forms compare their digits as written, in any comma, space, or brace spelling) and `contains` (words in any field; records with a field equal to the words come first). When a registry has several sub-registries and none is given, the response lists them instead of records; a table that nests tables lists them too. Field names are the registry's XML element names (e.g. "rec" is the Recommended column). Large registries page through `cursor`. Find ids with iana_search_registries.

  Paramètres, retour & exemple (7)

  Paramètres

  • field · string · optionnel
    Column for value to match instead of the key column, case-insensitive, one of the names in columns: e.g. "type" for a DNS RR type mnemonic, or "name" for every row of a service name. Ignored without value.
  • limit · integer · optionnel
    Requested maximum results, 1–1,000,000; values above 100 are clamped to 100 and disclosed as requested_limit and effective_limit. Default 25.
  • value · string · optionnel
    Exact match on the key column named by value_field (value, else number, else the first column), or on field when set; case and whitespace are ignored. A value of digits compares exactly with a cell of digits, so "0443" finds "443", and also matches decimal range rows without precision loss, including 64-bit endpoints; it never matches a 0x cell. One 0x token compares by number with a one-token 0x cell, so "0x5" finds "0x05", and also matches range rows such as "0x11-0xff". Any other pair of 0x forms compares the digits as written: "0x1301", "{0x13,0x01}", and "0x13 0x01" all find "0x13,0x01", while "0x13" never finds "0x00,0x13".
  • cursor · string · optionnel
    next_cursor from the previous page; reuse it only with the same registry, subregistry, value, field, and contains.
  • contains · string · optionnel
    Words matched as whole tokens against every field and reference id, e.g. "chacha20". Records with a field equal to the words come first.
  • registry · string · requis
    Registry id, e.g. "tls-parameters", or its https://www.iana.org/assignments/<id> URL (a #fragment selects the sub-registry when subregistry is unset).
  • subregistry · string · optionnel
    Sub-registry id, case-insensitive, e.g. "tls-parameters-4". Omit to read the only sub-registry, or to list them when there are several.

  Exemple d'appel

  {"name": "iana_get_registry_records", "arguments": {"registry": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"cap": 1, "error": {}, "notes": [], "shown": 1, "notice": "texte", "offset": 1, "source": {}, "columns": [], "records": [], "truncated": true, "references": [], "totalCount": 1}}

• iana_get_rfc_status≈ 3078 tokens

  Get the current status of up to ten distinct RFCs, Internet-Drafts, or BCP/STD/FYI series per page from up to 1,000 input items. Canonical aliases resolve once. When more remain, deferred_ids previews the next ten, deferred_count counts the whole remainder, and next_ids_offset continues the same original ids. Retry failed ids separately. Accepts "RFC 9110", "rfc9110", "9110", draft names with or without a revision suffix ("draft-ietf-httpbis-semantics-19"), series numbers ("BCP 14"), RFC and draft file names ("rfc9110.txt"), the URL of an RFC or draft on datatracker.ietf.org, tools.ietf.org, or ietf.org or of an RFC on rfc-editor.org, and a series URL at rfc-editor.org/info/ or datatracker.ietf.org/doc/ ("https://datatracker.ietf.org/doc/bcp14/"). RFCs return current and as-published status, stream, working group, obsoletes/obsoleted-by and updates/updated-by relations, the series they belong to, and the errata page; drafts return their state, IESG state, intended status, expiry, the document that replaced them, and the RFC they became; a series returns its member RFCs. Unknown ids return found: false. A call makes at most 20 Datatracker requests, retries included (an RFC or a series needs one, plus one per call for the RFCs' series; a draft three, or four with a revision suffix): each id is taken in request order if its requests still fit, and the others come back in failed with reason request_limit, to pass in another call.

  Paramètres, retour & exemple (2)

  Paramètres

  • ids · array · requis
    Up to 1,000 normalized nonblank RFC, Internet-Draft, or series items; aliases are canonically deduplicated before selecting ten distinct ids. One comma-, semicolon-, or newline-separated string is also accepted. Resubmit the same ids with next_ids_offset as ids_offset to continue.
  • ids_offset · integer · optionnel
    Number of canonically distinct ids to skip, default 0. Pass next_ids_offset with the same original ids to continue; retry failed ids separately.

  Exemple d'appel

  {"name": "iana_get_rfc_status", "arguments": {"ids": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "failed": [], "notice": "texte", "documents": [], "total_ids": 1, "deferred_ids": [], "deferred_count": 1, "deferred_reason": "texte", "next_ids_offset": 1, "deferred_guidance": "texte"}}

• iana_lookup_http_field≈ 1620 tokens

  Look up a registered HTTP field (header or trailer) name. Pass exactly one of `name` (case-insensitive, e.g. "Cache-Status") or `keyword` (words matched against field names and comments). Returns the registration status — permanent, provisional, deprecated, or obsoleted — the Structured Field type when registered, and the defining reference. Many widely used headers are unregistered; a miss means only that IANA has no entry.

  Paramètres, retour & exemple (5)

  Paramètres

  • name · string · optionnel
    Exact field name, case-insensitive, e.g. "Content-Type" (a trailing ":" is ignored). Pass this or keyword, not both.
  • limit · integer · optionnel
    Requested maximum results, 1–1,000,000; values above 100 are clamped to 100 and disclosed as requested_limit and effective_limit. Default 25.
  • offset · integer · optionnel
    Number of keyword matches to skip; pass the next_offset of the previous response to get the next page. Default 0.
  • status · string · optionnel · permanent | provisional | deprecated | obsoleted
    Keep only fields with this registration status. Applies to both modes.
  • keyword · string · optionnel
    Words matched as whole tokens against field names and registry comments, e.g. "cache". Pass this or name, not both.

  Exemple d'appel

  {"name": "iana_lookup_http_field", "arguments": {"name": "texte", "limit": 1, "offset": 1, "status": "permanent", "keyword": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"cap": 1, "mode": "name", "error": {}, "found": true, "shown": 1, "fields": [], "notice": "texte", "source": {}, "truncated": true, "totalCount": 1, "next_offset": 1, "effective_limit": 1}}

• iana_lookup_http_status≈ 1624 tokens

  Look up an HTTP status code in the IANA registry, or search reason phrases. Pass exactly one of `code` (100–599) or `keyword` (e.g. "too many"). Returns the registered phrase, its class, defining reference with section, and whether it is temporary, obsoleted, or unused; an unassigned code returns found: false with the unassigned range it falls in.

  Paramètres, retour & exemple (4)

  Paramètres

  • code · integer · optionnel
    Status code to look up, 100–599 (a digit string such as "429" also works). Pass this or keyword, not both.
  • limit · integer · optionnel
    Requested maximum results, 1–1,000,000; values above 100 are clamped to 100 and disclosed as requested_limit and effective_limit. Default 25.
  • offset · integer · optionnel
    Number of keyword matches to skip; pass the next_offset of the previous response to get the next page. Default 0.
  • keyword · string · optionnel
    Words matched as whole tokens against registered reason phrases, e.g. "too many" or "gateway". Pass this or code, not both.

  Exemple d'appel

  {"name": "iana_lookup_http_status", "arguments": {"code": 1, "limit": 1, "offset": 1, "keyword": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"cap": 1, "mode": "code", "error": {}, "found": true, "shown": 1, "notice": "texte", "source": {}, "statuses": [], "truncated": true, "totalCount": 1, "next_offset": 1, "effective_limit": 1}}

• iana_lookup_language_tag≈ 3534 tokens

  Parse and validate a BCP 47 language tag against the IANA Language Subtag Registry, or search subtags by description. Pass exactly one of `tag` (e.g. "zh-Hant-TW", "sr-Latn", "en_US") or `description` (e.g. "Swiss German"). A tag is split into language, extlang, script, region, variant, extension, and private-use parts; deprecated subtags report their preferred value, and a canonical tag is returned when valid. Extension singleton allocation and defining RFCs are optional metadata; allocation never validates extension content or changes base validity. A single subtag registered under several types (e.g. "TW") lists the other types.

  Paramètres, retour & exemple (5)

  Paramètres

  • tag · string · optionnel
    A language tag to validate, e.g. "zh-Hant-TW", "sr-Latn", "i-klingon". Underscores are read as hyphens ("en_US" → "en-US"); matching ignores case. Pass this or description, not both.
  • limit · integer · optionnel
    Requested description matches, 1–1,000,000, clamped to 100 with requested_limit and effective_limit disclosed. Default 25. Tag mode always returns every part of the tag.
  • offset · integer · optionnel
    Number of description matches to skip; pass the next_offset of the previous response to get the next page. Default 0.
  • description · string · optionnel
    Words matched as whole tokens against subtag descriptions, e.g. "Swiss German" or "Cyrillic". Pass this or tag, not both.
  • subtag_type · string · optionnel · language | extlang | script | region | variant | grandfathered | redundant
    Description mode only: return only records of this Type.

  Exemple d'appel

  {"name": "iana_lookup_language_tag", "arguments": {"tag": "texte", "limit": 1, "offset": 1, "description": "texte", "subtag_type": "language"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"cap": 1, "mode": "tag", "error": {}, "shown": 1, "valid": true, "issues": [], "notice": "texte", "source": {}, "matches": [], "subtags": [], "tag_input": "texte", "truncated": true}}

• iana_lookup_media_type≈ 2121 tokens

  Look up registered media (MIME) types. Pass exactly one of `type` (a full name such as "application/json"; parameters after ";" are ignored) or `keyword` (words matched against registered type names and status annotations, e.g. "geo json"; never against file extensions). An exact `type` lookup also reads the registration template and returns its file-extension, intended-usage, and deprecated-alias statements as written, each only when the template has it. Some registered types have no registration template (`template.available: false`); their references are the defining documents. Deprecated and obsoleted types are reported with their replacement when the registry names one. Unregistered "x-" types are not in the registry.

  Paramètres, retour & exemple (5)

  Paramètres

  • type · string · optionnel
    Full media type, case-insensitive, e.g. "application/json" ("; charset=utf-8" and other parameters are dropped). Pass this or keyword, not both.
  • limit · integer · optionnel
    Requested maximum results, 1–1,000,000; values above 100 are clamped to 100 and disclosed as requested_limit and effective_limit. Default 25.
  • offset · integer · optionnel
    Number of keyword matches to skip; pass the next_offset of the previous response to get the next page. Default 0.
  • keyword · string · optionnel
    Words matched as whole tokens against registered type names and status annotations, e.g. "geo json". File extensions are not searched: look up the expected type with type to read its template's file-extension statement, when the template has one. Pass this or type, not both.
  • top_level · string · optionnel · application | audio | example | font | haptics | image | message | model
    Keep only types under this top-level type, e.g. "image". Keyword mode only.

  Exemple d'appel

  {"name": "iana_lookup_media_type", "arguments": {"type": "texte", "limit": 1, "offset": 1, "keyword": "texte", "top_level": "application"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"cap": 1, "mode": "type", "error": {}, "found": true, "shown": 1, "notice": "texte", "source": {}, "truncated": true, "totalCount": 1, "media_types": [], "next_offset": 1, "effective_limit": 1}}

• iana_lookup_pen≈ 1537 tokens

  Look up a Private Enterprise Number (PEN). Pass exactly one of `pen` (a number such as 32473, or an OID under 1.3.6.1.4.1 such as 1.3.6.1.4.1.32473.1.2) or `organization` (words matched against organization names). Returns the organization and its OID prefix. Arcs below the enterprise number are assigned by the enterprise, not IANA. Contact details are not returned.

  Paramètres, retour & exemple (4)

  Paramètres

  • pen · string · optionnel
    Enterprise number, e.g. "32473", or an OID under 1.3.6.1.4.1 naming it, e.g. "1.3.6.1.4.1.32473.1.2" (a leading dot and the iso.org.dod.internet.private.enterprise prefix are accepted). Pass this or organization, not both.
  • limit · integer · optionnel
    Requested maximum results, 1–1,000,000; values above 100 are clamped to 100 and disclosed as requested_limit and effective_limit. Default 25.
  • offset · integer · optionnel
    Number of organization matches to skip; pass the next_offset of the previous response to get the next page. Default 0.
  • organization · string · optionnel
    Words matched as whole tokens against the names of assigned entries, e.g. "cisco systems"; look up a number with pen to see a reserved or unassigned one. Pass this or pen, not both.

  Exemple d'appel

  {"name": "iana_lookup_pen", "arguments": {"pen": "texte", "limit": 1, "offset": 1, "organization": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"cap": 1, "mode": "pen", "error": {}, "found": true, "shown": 1, "notice": "texte", "source": {}, "sub_arcs": "texte", "truncated": true, "totalCount": 1, "enterprises": [], "next_offset": 1}}

• iana_lookup_port≈ 1983 tokens

  Look up IANA service name and transport protocol port assignments. Pass exactly one of `port` (a number, 0–65535), `service` (an exact service name such as "postgresql"), or `keyword` (words matched against service names and descriptions). Results list every transport (tcp, udp, sctp, dccp) separately, report the registry range row containing an unassigned port, and classify the port as System (0–1023), User (1024–49151), or Dynamic/Private (49152–65535). Service names registered without a port (DNS-SD names) appear with no port.

  Paramètres, retour & exemple (6)

  Paramètres

  • port · integer · optionnel
    Port number, 0–65535 (a digit string such as "443" also works). Returns every row for that port plus the range row containing it. Pass exactly one of port, service, or keyword.
  • limit · integer · optionnel
    Requested maximum results, 1–1,000,000; values above 100 are clamped to 100 and disclosed as requested_limit and effective_limit. Default 25.
  • offset · integer · optionnel
    Number of keyword matches to skip; pass the next_offset of the previous response to get the next page. Default 0.
  • keyword · string · optionnel
    Words matched as whole tokens against service names and descriptions, e.g. "network time". Pass exactly one of port, service, or keyword.
  • service · string · optionnel
    Exact service name, case-insensitive, up to 15 characters, e.g. "postgresql" or "whois++". Pass exactly one of port, service, or keyword.
  • transport · string · optionnel · tcp | udp | sctp | dccp
    Keep only rows for this transport protocol. Rows without a transport (most range rows and every service name without a port) are always kept. Applies to every mode.

  Exemple d'appel

  {"name": "iana_lookup_port", "arguments": {"port": 1, "limit": 1, "offset": 1, "keyword": "texte", "service": "texte", "transport": "tcp"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"cap": 1, "mode": "port", "error": {}, "found": true, "shown": 1, "notice": "texte", "source": {}, "truncated": true, "port_class": {}, "totalCount": 1, "assignments": [], "next_offset": 1}}

• iana_lookup_uri_scheme≈ 1646 tokens

  Look up a registered URI scheme. Pass exactly one of `scheme` (e.g. "mailto"; a trailing ":" or "://" is ignored) or `keyword` (words matched against scheme names and descriptions). Returns the status — permanent, provisional, or historical — description, references, and well-known URI support.

  Paramètres, retour & exemple (5)

  Paramètres

  • limit · integer · optionnel
    Requested maximum results, 1–1,000,000; values above 100 are clamped to 100 and disclosed as requested_limit and effective_limit. Default 25.
  • offset · integer · optionnel
    Number of keyword matches to skip; pass the next_offset of the previous response to get the next page. Default 0.
  • scheme · string · optionnel
    Exact scheme name, case-insensitive, e.g. "https" (a trailing ":" or "://" is ignored). Pass this or keyword, not both.
  • status · string · optionnel · permanent | provisional | historical
    Keep only schemes with this registration status. Applies to both modes.
  • keyword · string · optionnel
    Words matched as whole tokens against scheme names and descriptions, e.g. "websocket". Pass this or scheme, not both.

  Exemple d'appel

  {"name": "iana_lookup_uri_scheme", "arguments": {"limit": 1, "offset": 1, "scheme": "texte", "status": "permanent", "keyword": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"cap": 1, "mode": "scheme", "error": {}, "found": true, "shown": 1, "notice": "texte", "source": {}, "schemes": [], "truncated": true, "totalCount": 1, "next_offset": 1, "effective_limit": 1}}

• iana_search_registries≈ 1469 tokens

  Find IANA protocol registries and sub-registries by keyword over their titles and protocol categories, e.g. "tls cipher", "dns resource record", "protocol numbers". Returns the registry and sub-registry ids that iana_get_registry_records reads, with registration procedure and defining documents. Covers every registry linked from the IANA protocol registries index.

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · integer · optionnel
    Requested maximum results, 1–1,000,000; values above 50 are clamped to 50 and disclosed as requested_limit and effective_limit. Default 15.
  • query · string · requis
    Words matched as whole tokens, singular or plural, against registry titles, categories, and ids, e.g. "tls cipher". An exact registry or sub-registry id ranks first, then the closest titles.
  • offset · integer · optionnel
    Number of matches to skip; pass the next_offset of the previous response to get the next page. Default 0.

  Exemple d'appel

  {"name": "iana_search_registries", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"cap": 1, "error": {}, "shown": 1, "notice": "texte", "source": {}, "truncated": true, "registries": [], "totalCount": 1, "next_offset": 1, "effective_limit": 1, "requested_limit": 1}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://iana-registries.caseyjhand.com/mcp