Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/Alvi97/angular-signal-forms-migration-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/alvi97/angular-signal-forms-migration-mcp/angular-signal-forms-migration-mcp)<a href="https://agentmods.dev/mcp/alvi97/angular-signal-forms-migration-mcp/angular-signal-forms-migration-mcp"><img src="https://agentmods.dev/badge/mcp/alvi97/angular-signal-forms-migration-mcp/angular-signal-forms-migration-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
angular-signal-forms-migration-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"angular-signal-forms-migration-mcp": {
"command": "npx",
"args": [
"-y",
"angular-signal-forms-migration-mcp"
],
"env": {}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 10 lines scan A 94899ebb29db
angular-signal-forms-migration-mcp is an MCP server published in the GitHub repository Alvi97/angular-signal-forms-migration-mcp (0 stars, last pushed 14d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
ui-mcp
Forge Space MCP server for UI and backend generation via stdio transport. Runs locally from the @forgespace/ui-mcp npm package.
ui-toolkit-mcp
Full-stack UI toolkit MCP server: generate components, manage design tokens, and audit markup across React, Vue, Svelte, Angular, and Web Components. Runs locally from the @elsahafy/ui-toolkit-mcp npm package.
mcp-server
Unified MCP server for Ignite UI — documentation, API, and CLI scaffolding. Runs locally from the @igniteui/mcp-server npm package.
neuralng
Read-only discovery for NeuralNg Angular components, APIs, packages, icons and theme recipes. Runs locally from the @neural-ng/mcp-server npm package.
angular-cli
CLI tool for Angular. Runs locally from the @angular/cli npm package.
gradient
MCP server for CSS gradient generation — linear, radial, conic. Runs locally from the gradient-forge-mcp npm package.