Skip to main content
Glama

regsub-mcp

MCPize MCP server for regulatory submission intelligence — ICH guideline lookup, CTD module mapping, eCTD structure guidance, and FDA/EMA query support

Connect via MCPize

Use this MCP server instantly with no local installation:

npx -y mcpize connect @pubspro/regsub-mcp --client claude

Or connect at: https://mcpize.com/mcp/regsub-mcp

Available Tools

6 tools
check_ctd_completenessA

Check a list of provided CTD sections against required sections and identify gaps.

Inputs: provided_sections (required), submission_type (required), module (required).

check_ich_complianceB

Check a description of a study or document against ICH guideline requirements and return a compliance assessment.

Inputs: description (required), guideline_code (required).

generate_submission_checklistB

Generate a submission readiness checklist for a given submission type and agency.

Inputs: submission_type (required), agency (required).

get_agency_deficiency_guidanceA

Retrieve common deficiency areas for FDA or EMA submissions by domain (CMC, Clinical, Labelling, Pharmacovigilance).

Inputs: agency (required), domain (required).

lookup_ich_guidelineA

Look up an ICH guideline by code (e.g. E6(R3), M4, Q1A). Returns scope, key requirements, and official URL.

Inputs: guideline_code (required).

map_ctd_sectionA

Map a document type or data package to the correct CTD/eCTD module and section. Returns the full section hierarchy.

Inputs: module (required), submission_type.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct function: completeness checking, compliance assessment, checklist generation, deficiency guidance, guideline lookup, and CTD section mapping. No overlap.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case (e.g., check_ctd_completeness, lookup_ich_guideline), making them predictable and easy to parse.

    Tool Count5/5

    With 6 tools, the set is well-scoped for the regulatory submission domain, covering essential actions without being overwhelming or too sparse.

    Completeness4/5

    The tools cover key workflows: checking compliance, mapping sections, generating checklists, and retrieving guidance. Minor gaps exist (e.g., no tool for direct submission or formatting), but these are acceptable given the advisory focus.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers