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.

io.github.uchit/aipatterns-mcp-server

NPM · AIPATTERNS-MCP-SERVER

Search AU enterprise AI patterns, benchmarks, incidents, and regulatory changes.

0 this week 86 Trust /100

Last scanned (18 hours ago)

Scores higher than 90% of npm servers

Category AI and Machine Learning

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 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
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability86
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 465 tokens (~93/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
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
    • Stability: 0.97 → pass security
  • 2 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 27 Oct 26 +1
    • Stability: 0.97 → pass security
  • 26 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 20 Oct 26 +1
    • Stability: 0.97 → pass security
  • 19 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +2
    • Stability: 0.87 → pass security
  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 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/aipatterns-mcp-server@1.1.0

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 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~465 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
get_incidents ~92

Retrieve notable Australian AI incidents. Useful for understanding real-world failures, regulatory enforcement actions, and which patterns could have prevented the incident.

NameTypeReqDescription
limitnumber–Maximum number of incidents to return (default 5)
sectorstring–Filter by sector: banking, insurance, government, retail, healthcare, utilities
severitystring–Filter by severity: critical, high, medium, low

No output schema declared.

No examples provided.

get_pattern ~62

Retrieve full detail of a specific AI pattern from aipatterns.com.au, including implementation guidance and regulatory context. Use the slug returned by search_patterns.

NameTypeReqDescription
slugstringyesPattern slug, e.g. "agentic-ai/agent-checkpoint-and-recovery"

No output schema declared.

No examples provided.

get_regulatory_changes ~107

Retrieve recent and upcoming Australian AI regulatory changes (APRA, OAIC, ASIC, TGA, Privacy Act reform). Useful for understanding compliance obligations when building AI systems for the Australian market.

NameTypeReqDescription
impact_levelstring–Filter by impact level: critical, high, medium, low
limitnumber–Maximum number of changes to return (default 5)
regulatorstring–Filter by regulator abbreviation: APRA, OAIC, ASIC, TGA

No output schema declared.

No examples provided.

get_sector_benchmark ~79

Get the AU AI Maturity Index benchmark score for a specific sector. Returns overall score, dimension scores (adoption, governance, investment, incidents), sector rank, and national averages. Scores computed from Q2 2026 evidence base.

NameTypeReqDescription
sectorstringyesOne of: banking, insurance, government, retail, healthcare, utilities

No output schema declared.

No examples provided.

search_patterns ~125

Search the aipatterns.com.au AI pattern library. Returns matching patterns with slug, title, description, maturity level, and category. Useful for finding design patterns relevant to a specific AI use case, capability, or compliance concern.

NameTypeReqDescription
categorystring–Optional category filter (e.g. agentic-ai, governance, security, rag, observability, compliance, human-in-the-loop)
maturitystring–Optional maturity filter (e.g. production, beta, experimental)
querystringyesSearch term to match against pattern title, description, or content

No output schema declared.

No examples provided.

Install

How do I install the io.github.uchit/aipatterns-mcp-server server?

io.github.uchit/aipatterns-mcp-server runs locally as an npm package, launched with npx -y aipatterns-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 · aipatterns-mcp-server

# add to Claude Code
claude mcp add uchit-aipatterns-mcp-server -- npx -y aipatterns-mcp-server
Common questions

What is the io.github.uchit/aipatterns-mcp-server server?

io.github.uchit/aipatterns-mcp-server is listed in the public MCP registry as io.github.uchit/aipatterns-mcp-server. Search AU enterprise AI patterns, benchmarks, incidents, and regulatory changes. This page covers its npm package (aipatterns-mcp-server).

Is the io.github.uchit/aipatterns-mcp-server server safe to use?

io.github.uchit/aipatterns-mcp-server scores 86 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. 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.uchit/aipatterns-mcp-server server expose?

io.github.uchit/aipatterns-mcp-server exposes 5 tools: search_patterns, get_pattern, get_incidents, get_sector_benchmark, get_regulatory_changes. Their descriptions and schemas cost roughly 465 tokens of context every time the server is loaded.

Is the io.github.uchit/aipatterns-mcp-server server still maintained?

io.github.uchit/aipatterns-mcp-server 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 io.github.uchit/aipatterns-mcp-server server under?

io.github.uchit/aipatterns-mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.