pqc-migration-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| credential_sizeC | Total on-wire bytes for a KEM + signature credential, with a per-component breakdown. |
| describe_familyA | Detail for one failure family: the invariants it breaks, the unrepaired designs that fail it, and what each did. Does not return repairs. |
| fragmentsB | How many fragments an object becomes on a transport, and whether fragmentation is therefore mandatory. |
| list_failure_familiesA | All 39 post-quantum migration failure families, with case counts and published prior-art analogues. |
| reassembly_windowC | The two-sided reassembly-capacity window. Returns is_empty=true when NO capacity cap is both feasible and safe, plus the maximum concurrency that would be safe. |
| score_submissionB | Score a PQC-MFB submission ({case_id: bool}). Returns coverage, regressions, and which families have zero coverage. |
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 6 tools
Each tool targets a distinct aspect of PQC migration analysis: failure families, reassembly capacity, submission scoring, credential size, family details, and fragmentation. No overlaps in functionality.
Most tools follow a verb_noun pattern with underscores (list_failure_families, score_submission, describe_family). 'credential_size' and 'reassembly_window' are noun-like but still clear; 'fragments' is a single noun, slightly deviating.
The set includes 6 tools, which is well within the ideal 3-15 range. Each tool addresses a specific need without redundancy, making the scope manageable and focused.
The tools cover querying failure families and scoring submissions, but lack submission management, repair retrieval (noted in describe_family), and listing submissions. Some gaps exist for a full workflow.