io.github.joelp22-maker/referencesource-rules

Est-ce que io.github.joelp22-maker/referencesource-rules est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.joelp22-maker/referencesource-rules » 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 5 outils

• get_rule≈ 426 tokens

  Everything this register holds for one final rule: title, agency, effective date, the rule's own DATES paragraph, the CFR parts it amends, its publication date, a link to the rule on federalregister.gov, and a verbatim quote of the Federal Register API record it was read from. Document numbers look like "2026-13685" and appear in every other tool's results.

  Paramètres, retour & exemple (1)

  Paramètres

  • document_number · string · requis
    Federal Register document number, e.g. "2026-13685".

  Exemple d'appel

  {"name": "get_rule", "arguments": {"document_number": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"rule": {}, "register": {}}}

• list_agencies≈ 290 tokens

  Which agencies have rules coming? Returns each agency in this register with how many rules it has taking effect, the soonest and latest of those dates. Call it to get an agency name exactly as the Federal Register writes it before filtering with list_rules_taking_effect — "Federal Aviation Administration", not "FAA".

  Paramètres, retour & exemple (1)

  Paramètres

  • query · string · optionnel
    Optional case-insensitive substring filter on the agency name.

  Exemple d'appel

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

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"agencies": [], "coverage": "texte", "register": {}, "agencies_total": 1}}

• list_rules_amending_cfr_part≈ 750 tokens

  Is anything changing in the part of the CFR I am subject to? Give a CFR title and part — "49 CFR 192", "40 CFR 52", "21 CFR 1308" — and get the already-published final rules that amend it, soonest effective date first, with each rule's DATES paragraph and a verbatim quote. The part is matched whole, so "40 CFR 5" never returns rules about 40 CFR 52.

  Paramètres, retour & exemple (3)

  Paramètres

  • from · string · optionnel
    Optional ISO date; only rules taking effect on or after it.
  • limit · integer · optionnel
    How many to return, 1–20. Default 20.
  • cfr_part · string · requis
    The CFR title and part together, e.g. "49 CFR 192". A bare part number is refused: it is ambiguous across the fifty CFR titles.

  Exemple d'appel

  {"name": "list_rules_amending_cfr_part", "arguments": {"cfr_part": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"rules": [], "cfr_part": "texte", "coverage": "texte", "register": {}, "rules_matched": 1, "rules_returned": 1}}

• list_rules_taking_effect≈ 824 tokens

  What lands on me, and when? Lists already-published US federal final rules whose effective date falls between two dates, soonest first, optionally from one agency. Each with the rule title, the agency, the CFR parts amended, the document number, the rule's own DATES paragraph and a verbatim quote of the Federal Register record. This is the compliance-calendar question — use it for "what takes effect in Q4", not for searching the Federal Register by topic.

  Paramètres, retour & exemple (4)

  Paramètres

  • to · string · requis
    ISO end date, inclusive, e.g. "2026-12-31".
  • from · string · requis
    ISO start date, inclusive, e.g. "2026-10-01".
  • limit · integer · optionnel
    How many to return, 1–20. Default 20.
  • agency · string · optionnel
    Optional agency filter, matched case-insensitively as a substring of the agency name ("Coast Guard", "aviation"). Call list_agencies for the names as the Federal Register writes them.

  Exemple d'appel

  {"name": "list_rules_taking_effect", "arguments": {"to": "texte", "from": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"to": "texte", "from": "texte", "rules": [], "coverage": "texte", "register": {}, "rules_matched": 1, "rules_returned": 1}}

• verify_quote≈ 756 tokens

  Is this right? Check a claim about a final rule — its effective date, its agency, the CFR parts it amends — against the Federal Register record instead of trusting it. Says whether the claim matches a stored value, appears only in the verbatim quote, or differs (and then what the record says instead). Effective dates are exactly where a confident wrong answer costs money.

  Paramètres, retour & exemple (3)

  Paramètres

  • field · string · optionnel
    Which field the claim is about, if you know it. Without it, every stored field of the record is checked.
  • claimed_value · string · requis
    The value to check, exactly as claimed, e.g. "Terminated" or "2026-10-29".
  • document_number · string · requis
    Federal Register document number of the rule the claim is about, e.g. "2026-13685".

  Exemple d'appel

  {"name": "verify_quote", "arguments": {"claimed_value": "texte", "document_number": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"match": {}, "record": {}, "verdict": "matches_record", "attestation": "texte", "quote_source": "texte", "claimed_value": "texte", "stored_values": {}, "in_source_quote": true}}

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://referencesource.org/mcp/rules