Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

NeuralNg Angular UI Expert MCP

NPM · @NEURAL-NG/MCP-SERVER

Angular UI expert for NeuralNg discovery, composition, validation, icons and project-aware themes.

+5 this week 95 Trust /100

Last scanned (19 hours ago)

Scores higher than 98% of npm servers

Category Developer Tools

Trust breakdown (7 categories)

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 Security100
  • 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
  • 0 of 6 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to hasanaydin7/NeuralTech). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 10776 tokens (~21/item across 506 items; 20 tools + 486 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 42% of tool parameters carry a description.Partial
  • 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 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 1 Nov 26 +5
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • CVE-2026-111770 no longer affects this package ▲ security
    • CVE-2026-111768 no longer affects this package ▲ security
    • CVE-2026-111771 no longer affects this package ▲ security
    • GHSA-f897-62hf-6gxq no longer affects this package ▲ security
    • Known CVEs: fail → pass ▲ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Package version: 1.0.0 → 1.0.1 functional
  • 28 Oct 26 0
    • GHSA-f897-62hf-6gxq affects this package: high ▼ security
  • 21 Oct 26 −5
    • CVE-2026-111771 affects this package: high ▼ security
    • CVE-2026-111770 affects this package: high ▼ security
    • CVE-2026-111768 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 17 Oct 26 0
    • Stability: 0.97 → pass security
  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 4 Nov 2026 · Analysed npm/@neural-ng/mcp-server@1.0.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo hasanaydin7/NeuralTech
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/hasanaydin7/NeuralTech/.github/workflows/publish-npm.yml@refs/tags/npm-release-2026.11.01-01
Rekor log index 3624681002
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:0a15ea73c4c8faefd28d2c8292a8bc1d797b9a1f7271eeedd6d60e30868b883eb79e10467586aaba2348b258ee09951e9b50a9facc1a8c2a227624ff6

Background: How many MCP packages publish verified provenance →

Dependencies 6 packages
Packages resolved 6
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 20 exposed · ~1,170 tokens

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 →

Tool Tokens
compile_theme_recipe ~62

Compile and validate a compact recipe, returning summary, diagnostics, artifact byte sizes and integration instructions without emitting the full token graph.

NameTypeReqDescription
recipeobject–Native recipe object (preferred).
recipe_jsonstring–Legacy JSON-encoded recipe; prefer recipe.
NameTypeReqDescription
artifactsobject––
diagnosticsarrayyes–
integrationobject––
summaryobject––
validbooleanyes–

No examples provided.

create_theme_recipe ~104

Create a deterministic sparse recipe from high-level brand and interface decisions. options accepts string fields: description, preset, primary, surface, radius, border, density, elevation, motion, typographyScale. Use options: {} for neutral defaults. Use preset, not extends; extends belongs to the returned recipe.

NameTypeReqDescription
namestringyes–
optionsobject–Native options object (preferred).
options_jsonstring–Legacy JSON-encoded options; prefer options.
NameTypeReqDescription
recipeobjectyes–
validationobjectyes–

No examples provided.

diff_theme_recipes ~79

Return only the deterministic dotted paths that differ between two compact recipes.

NameTypeReqDescription
leftobject–Native left object (preferred).
left_jsonstring–Legacy JSON-encoded left; prefer left.
rightobject–Native right object (preferred).
right_jsonstring–Legacy JSON-encoded right; prefer right.
NameTypeReqDescription
changesarrayyes–

No examples provided.

edit_theme_recipe ~84

Apply a safe sparse patch with dotted set paths and unset paths, then validate the resulting recipe.

NameTypeReqDescription
patchobject–Native patch object (preferred).
patch_jsonstring–Legacy JSON-encoded patch; prefer patch.
recipeobject–Native recipe object (preferred).
recipe_jsonstring–Legacy JSON-encoded recipe; prefer recipe.
NameTypeReqDescription
recipeobject––
recipeJsonstring––
validationobjectyes–

No examples provided.

get_component ~51

Resolve a component and return its versioned public API. Use summary for discovery, standard for implementation, or full for every class slot and example.

NameTypeReqDescription
componentstringyes–
detailstring––
NameTypeReqDescription
componentobjectyes–

No examples provided.

get_component_contract ~35

Resolve a component by id, class, selector, or entry point and return its public contract.

NameTypeReqDescription
componentstringyes–
NameTypeReqDescription
componentobjectyes–

No examples provided.

get_component_examples ~40

Return bounded, executable examples extracted from the published component README with their heading and language.

NameTypeReqDescription
componentstringyes–
limitinteger––
NameTypeReqDescription
componentobjectyes–
examplesarrayyes–

No examples provided.

get_component_theme_contract ~49

Return only the supported theme properties for one Core or Editor component. Use detail=defaults only when current default values are needed.

NameTypeReqDescription
componentstringyes–
detailstring––
NameTypeReqDescription
componentstringyes–
propertiesarrayyes–
tokenCountintegeryes–

No examples provided.

inspect_neuralng_project ~32

Compatibility alias for inspect_project. It accepts no path and returns the same read-only schema-v2 inspection.

Input schema present but exposes no named parameters.

NameTypeReqDescription
inspectionobjectyes–

No examples provided.

inspect_project ~55

Read the bounded MCP working directory and return a schema-v2 Angular compiler-backed inventory of NeuralNg versions, templates, elements and attribute directives, exact imports, providers, icons, theme/appearance setup, conventions, evidence, and diagnostics.

Input schema present but exposes no named parameters.

NameTypeReqDescription
inspectionobjectyes–

No examples provided.

plan_ui ~49

Turn a product goal into a deterministic, contract-backed component composition with exact imports, providers, state, accessibility checks, and implementation order.

NameTypeReqDescription
goalstringyes–
kindstring––
NameTypeReqDescription
planobjectyes–

No examples provided.

recommend_components ~36

Recommend documented NeuralNg components for a UI goal using deterministic intent matching.

NameTypeReqDescription
goalstringyes–
limitinteger––
NameTypeReqDescription
matchesarrayyes–

No examples provided.

search_components ~57

Search the deterministic NeuralNg component catalog, README files, and llms.txt guidance. Omit query or use an empty string to browse a bounded list in stable id order.

NameTypeReqDescription
limitinteger––
querystring––
NameTypeReqDescription
matchesarrayyes–

No examples provided.

search_icons ~88

Search all 6,184 Neural Icons variants by name, category, or common UI intent and return exact CSS classes, smallest category imports, usage markup, and accessibility guidance. Brand icons are excluded unless explicitly requested.

NameTypeReqDescription
categorystring––
include_brandsboolean––
limitinteger––
querystringyes–
stylestring––
NameTypeReqDescription
iconsobjectyes–

No examples provided.

suggest_consistent_ui ~61

Inspect the current Angular workspace and return a schema-v2 consistency plan with component evidence, version alignment, exact import/provider deltas, theme ownership, bounded risks, and validation next steps.

NameTypeReqDescription
goalstringyes–
kindstring––
NameTypeReqDescription
suggestionobjectyes–

No examples provided.

suggest_form_structure ~38

Return a contract-backed form composition with exact imports, providers, state ownership, accessibility checks, and implementation order.

NameTypeReqDescription
goalstringyes–
NameTypeReqDescription
planobjectyes–

No examples provided.

suggest_page_structure ~38

Return a contract-backed page composition with exact imports, providers, state ownership, accessibility checks, and implementation order.

NameTypeReqDescription
goalstringyes–
NameTypeReqDescription
planobjectyes–

No examples provided.

suggest_table_structure ~38

Return a contract-backed table composition with exact imports, providers, state ownership, accessibility checks, and implementation order.

NameTypeReqDescription
goalstringyes–
NameTypeReqDescription
planobjectyes–

No examples provided.

validate_theme_recipe ~54

Validate compact recipe JSON against the published schema and the complete Core and Editor token contract.

NameTypeReqDescription
recipeobject–Native recipe object (preferred).
recipe_jsonstring–Legacy JSON-encoded recipe; prefer recipe.
NameTypeReqDescription
recipeobject––
validationobjectyes–

No examples provided.

validate_usage ~120

Parse an Angular template with @angular/compiler and validate syntax, NeuralNg elements and attribute directives, bindings, required inputs, literal values, icon-button accessibility, standalone imports, provider requirements, and duplicate Toast channels.

NameTypeReqDescription
importsarray–Standalone declaration names, e.g. ["NeuralButton"].
imports_jsonstring–Deprecated JSON-encoded array; prefer imports.
providersarray–Configured provider names.
providers_jsonstring–Deprecated JSON-encoded array; prefer providers.
templatestringyes–
NameTypeReqDescription
validationobjectyes–

No examples provided.

Install

How do I install the NeuralNg Angular UI Expert MCP server?

NeuralNg Angular UI Expert MCP runs locally as an npm package, launched with npx -y @neural-ng/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @neural-ng/mcp-server

# add to Claude Code
claude mcp add hasanaydin7-neuralng -- npx -y @neural-ng/mcp-server
Common questions

What is the NeuralNg Angular UI Expert MCP server?

NeuralNg Angular UI Expert MCP is listed in the public MCP registry as io.github.hasanaydin7/neuralng. Angular UI expert for NeuralNg discovery, composition, validation, icons and project-aware themes. This page covers its npm package (@neural-ng/mcp-server).

Is the NeuralNg Angular UI Expert MCP server safe to use?

NeuralNg Angular UI Expert MCP scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 NeuralNg Angular UI Expert MCP server expose?

NeuralNg Angular UI Expert MCP exposes 20 tools: search_components, search_icons, get_component, get_component_examples, get_component_contract, and 15 more. Their descriptions and schemas cost roughly 1,170 tokens of context every time the server is loaded.

Is the NeuralNg Angular UI Expert MCP server still maintained?

NeuralNg Angular UI Expert MCP is still listed as active in the MCP registry. We last reached this channel on 4 November 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 NeuralNg Angular UI Expert MCP server under?

NeuralNg Angular UI Expert 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.