io.github.Alvi97/angular-signal-forms-migration-mcp
NPM · ANGULAR-SIGNAL-FORMS-MIGRATION-MCP · SCANNED SEP 24
Finds Angular Reactive Forms and returns verified Signal Forms recipes. Never edits code.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 30 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1517 tokens (~252/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.Alvi97/angular-signal-forms-migration-mcp server?
io.github.Alvi97/angular-signal-forms-migration-mcp runs locally as an npm package, launched with npx -y angular-signal-forms-migration-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · angular-signal-forms-migration-mcp
claude mcp add alvi97-angular-signal-forms-migration-mcp -- npx -y angular-signal-forms-migration-mcp
{
"mcpServers": {
"alvi97-angular-signal-forms-migration-mcp": {
"command": "npx",
"args": [
"-y",
"angular-signal-forms-migration-mcp"
]
}
}
} {
"servers": {
"alvi97-angular-signal-forms-migration-mcp": {
"command": "npx",
"args": [
"-y",
"angular-signal-forms-migration-mcp"
]
}
}
} codex mcp add alvi97-angular-signal-forms-migration-mcp -- npx -y angular-signal-forms-migration-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"alvi97-angular-signal-forms-migration-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"angular-signal-forms-migration-mcp"
],
"enabled": true
}
}
} openclaw mcp add alvi97-angular-signal-forms-migration-mcp --command npx --arg -y --arg angular-signal-forms-migration-mcp
mcp_servers:
alvi97-angular-signal-forms-migration-mcp:
command: "npx"
args: ["-y", "angular-signal-forms-migration-mcp"] {
"McpServers": {
"alvi97-angular-signal-forms-migration-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"angular-signal-forms-migration-mcp"
]
}
}
} assistant mcp add alvi97-angular-signal-forms-migration-mcp -t stdio -c npx -a -y angular-signal-forms-migration-mcp
{
"mcpServers": {
"alvi97-angular-signal-forms-migration-mcp": {
"command": "npx",
"args": [
"-y",
"angular-signal-forms-migration-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Sept 26 −4
- Stability: pass → 0.77 functional
- 23 Sept 26 +1
- Stability: 0.97 → pass security
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Analysed npm/angular-signal-forms-migration-mcp@0.9.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_migration_complexity Summarise the size and shape of a Signal Forms migration ~97
Scans .ts and .html files (or a directory) and summarises the migration: total findings, counts per construct, the mechanical/judgment split, and a suggested file order (simplest first, so all-mechanical files land before the ones needing design decisions). Read-only: this tool never modifies your files.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute path to a .ts file or a directory to scan recursively. |
| Name | Type | Req | Description |
|---|---|---|---|
| angularVersion | string|null | yes | – |
| blockingPrerequisite | string|null | yes | – |
| byConstruct | object | yes | – |
| judgmentCount | integer | yes | – |
| mechanicalCount | integer | yes | – |
| referenceOnlyFiles | array | yes | – |
| sharedValidatorFiles | array | yes | – |
| signalFormsAvailable | boolean|null | yes | – |
| suggestedOrder | array | yes | – |
| totalFindings | integer | yes | – |
No examples provided.
find_form_candidates Find Angular Reactive Forms migration candidates ~259
Scans .ts and .html files (or a directory) for Angular Reactive Forms constructs and classifies each finding as "mechanical" (safe to transliterate) or "judgment" (a human must decide the target design). Read-only: this tool never modifies your files. Results are PAGED (default 200 findings) — check `incomplete`: non-null means there is more, and says how to get it. Filter with `constructs` / `classification` to work one decision at a time.
| Name | Type | Req | Description |
|---|---|---|---|
| classification | string | – | Return only "mechanical" or only "judgment" findings. |
| constructs | array | – | Return only these construct names (e.g. ["FormArray.push"]). Use it to pull one decision at a time. Filtering is announced in `incomplete`. |
| limit | integer | – | Maximum findings to return. Defaults to 200. A whole workspace can be far larger than one context window, so the response is a window and says so when it is. |
| offset | integer | – | Index of the first finding to return. Defaults to 0. Page with page.nextOffset. |
| path | string | yes | Absolute path to a .ts file or a directory to scan recursively. |
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | – |
| incomplete | string|null | yes | Non-null when this response is NOT the full result, with the call that returns the rest. Null means complete. Never treat a filtered or paged list as the whole job. |
| page | object | yes | – |
| totalFindings | integer | yes | Findings in the whole scan, unfiltered. |
No examples provided.
get_angular_upgrade_plan Plan the Angular upgrade that Signal Forms requires ~243
Signal Forms needs Angular 21+. When a project is older, this returns the upgrade plan as markdown, reproducing angular.dev/update-guide from Angular's own published step data — not written by this server. The current version is detected from the project; you choose application complexity (1 Basic, 2 Medium, 3 Advanced) and whether you use ngUpgrade, Angular Material or Windows, exactly as the official guide asks. Read-only: this tool never modifies your files.
| Name | Type | Req | Description |
|---|---|---|---|
| fromMajor | integer | – | Override the detected current major version. |
| level | – | – | Application complexity, as on angular.dev/update-guide: 1 Basic, 2 Medium, 3 Advanced. Defaults to 3. |
| material | boolean | – | "I use Angular Material." |
| ngUpgrade | boolean | – | "I use ngUpgrade to combine AngularJS & Angular." |
| path | string | yes | Absolute path inside the Angular project. The current version is read from its package.json. |
| toMajor | integer | – | Target major. Defaults to the version the recipes are verified against. |
| windows | boolean | – | "I use Windows." Swaps in cmd-compatible commands. |
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | – |
No examples provided.
get_migration_report Generate a Signal Forms migration report ~108
Scans .ts and .html files (or a directory) and returns a MARKDOWN REPORT combining findings, complexity, a suggested file order, the constructs present with their recipe names, and a warning for any version-sensitive recipe involved. Returns the report as a string — it does NOT write a file; you decide whether to save it. Read-only: this tool never modifies your files.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute path to a .ts file or a directory to scan recursively. |
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | – |
No examples provided.
get_signalforms_recipe Get an Angular Signal Forms migration recipe ~99
Returns a verified before/after migration recipe for a single Reactive Forms construct (e.g. "FormControl", "FormBuilder.group", "Validators.required"). An unknown construct returns found:false plus the list of available constructs — it is never an error. Read-only: this tool never modifies your files.
| Name | Type | Req | Description |
|---|---|---|---|
| construct | string | yes | Reactive Forms construct to look up, e.g. "FormControl", "FormBuilder.group", "Validators.required". |
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | – |
| availableConstructs | array | – | – |
| before | string | – | – |
| caveats | array | – | – |
| construct | string | yes | – |
| description | string | – | – |
| found | boolean | yes | – |
| provenance | object | – | – |
No examples provided.
verify_migration Verify an already-migrated Signal Forms file ~139
Reads code you have ALREADY migrated and reports Signal Forms traps that COMPILE and are still wrong — a missed signal call in a position TypeScript does not check, a deprecated-but-valid v21 rule shape, a pre-release API name, an AbstractControl left in a form() model, Reactive Forms imports left behind. Run it after tsc, not instead of it: anything the compiler already reports is deliberately not repeated here. Read-only. It proves the ABSENCE OF KNOWN DEFECTS, never correctness.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute path to an ALREADY-MIGRATED .ts file, or a directory to scan. |
| Name | Type | Req | Description |
|---|---|---|---|
| checksRun | array | yes | – |
| checksSkipped | array | yes | – |
| disclaimer | string | yes | – |
| errorCount | integer | yes | – |
| files | array | yes | – |
| infoCount | integer | yes | – |
| notMigratedFiles | array | yes | – |
| warningCount | integer | yes | – |
No examples provided.
What is the io.github.Alvi97/angular-signal-forms-migration-mcp server?
io.github.Alvi97/angular-signal-forms-migration-mcp is listed in the public MCP registry as io.github.Alvi97/angular-signal-forms-migration-mcp. Finds Angular Reactive Forms and returns verified Signal Forms recipes. Never edits code. This page covers its npm package (angular-signal-forms-migration-mcp).
Is the io.github.Alvi97/angular-signal-forms-migration-mcp server safe to use?
io.github.Alvi97/angular-signal-forms-migration-mcp scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.Alvi97/angular-signal-forms-migration-mcp server expose?
io.github.Alvi97/angular-signal-forms-migration-mcp exposes 6 tools: find_form_candidates, get_signalforms_recipe, analyze_migration_complexity, get_migration_report, get_angular_upgrade_plan, verify_migration. Their descriptions and schemas cost roughly 945 tokens of context every time the server is loaded.
Is the io.github.Alvi97/angular-signal-forms-migration-mcp server still maintained?
io.github.Alvi97/angular-signal-forms-migration-mcp is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.Alvi97/angular-signal-forms-migration-mcp server under?
io.github.Alvi97/angular-signal-forms-migration-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.