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/hasanaydin7/NeuralTechWrote 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/hasanaydin7/neuraltech/neural-mcp-neuralng)<a href="https://agentmods.dev/mcp/hasanaydin7/neuraltech/neural-mcp-neuralng"><img src="https://agentmods.dev/badge/mcp/hasanaydin7/neuraltech/neural-mcp-neuralng/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/hasanaydin7/neuraltech/neural-mcp-neuralng"><img src="https://agentmods.dev/badge/mcp/hasanaydin7/neuraltech/neural-mcp-neuralng.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
neuralng 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 12d 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
{
"neuralng": {
"command": "npx",
"args": [
"-y",
"@neural-ng/mcp-server"
],
"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.
- 12d ago First seen · 10 lines scan A 1ee514b940ff
neuralng is an MCP server published in the GitHub repository hasanaydin7/NeuralTech (8 stars, last pushed yesterday), 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
angular-cli
CLI tool for Angular. Runs locally from the @angular/cli npm package.
ng-blatui
MCP server "ng-blatui", hosted remotely at ngblatui.remix-it.com, as configured in anousss007/ng-blatui.
liquefy-ui
Answers questions about liquefy-ui from its real API surface, so an agent stops inventing props. Runs locally from the @liquefy-ui/mcp npm package.
uswds
Unofficial Model Context Protocol server for working with U.S. Web Design System components, patterns, templates, tokens, and accessibility guidance. Runs locally from the uswds-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.