Understand Anything - MCP

NPM · UA-MCP · SCANNED AUG 3

A powerful MCP server for codebase architecture analysis and automated governance.

Available components

+22 this week 68 68 Trust /100

Trust breakdown (6 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 →

Supply Chain Security87

No malware found by supply-chain analysis.Pass
Only part of the dependency tree could be resolved (113 of 114), so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (113 of 114), so this covers what we could see, not the whole tree. 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 14 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability71

AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 702 tokens (~46/item across 15 items; 15 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management23

Stability observed for 7 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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · ua-mcp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add uamcp-ua-mcp -- npx -y ua-mcp

# add to Codex CLI

codex mcp add uamcp-ua-mcp -- npx -y ua-mcp

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "uamcp-ua-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "ua-mcp"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add uamcp-ua-mcp --command npx --arg -y --arg ua-mcp

# ~/.hermes/config.yaml

mcp_servers:
  uamcp-ua-mcp:
    command: "npx"
    args: ["-y", "ua-mcp"]

// mcp.json

{
  "mcpServers": {
    "uamcp-ua-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ua-mcp"
      ]
    }
  }
}

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.

3 Aug 26 +4
- Stability: unverified → 0.23 ▲ functional
2 Aug 26 +59
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- Licence: MIT functional
31 Jul 26 −41
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
27 Jul 26 46

First indexed and scored.

Show 2 earlier entries Hide earlier entries

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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 113 packages

113 packages in the resolved dependency tree · 113 deprecated · 32 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 15 exposed · ~643 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.

Tool Tokens

ua_architecture_report ~33

Generate a module-level architecture report from the knowledge graph. Returns a breakdown of files per directory to identify main components.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ua_ci_check ~68

Run a CI-style impact analysis on a PR diff to identify risk factors. Returns affected files, risk level, and potential issues.

Input Output Examples

Name	Type	Req	Description
pr_diff	string	yes	Required. The raw git diff string representing the pull request changes. Must contain '+++ b/' or '--- a/' paths.

No output schema declared.

No examples provided.

ua_dependency_report ~37

Generate a top-level dependency report from the knowledge graph. Identifies the most heavily depended-on files in the codebase (high fan-in).

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ua_explain ~65

Explain a specific part of the codebase by retrieving its 1-hop dependencies. Call this to understand what a file imports and where it is used.

Input Output Examples

Name	Type	Req	Description
target	string	yes	Required. The precise file path or module name to explain. Example: 'src/core/db.ts'.

No output schema declared.

No examples provided.

ua_find_callers ~84

Find all callers of a specific function or file up to a certain depth. Helps trace execution paths.

Input Output Examples

Name	Type	Req	Description
maxDepth	number	—	Optional. Maximum search depth. Defaults to 2 (max 3).
target	string	yes	Required. The target file or function ID (e.g., 'src/api/handler.ts' or 'func:processData').

No output schema declared.

No examples provided.

ua_graph_summary ~33

Get a high-level statistical summary of the codebase knowledge graph. Returns total node and edge counts to gauge project size.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ua_impact_analysis ~52

Analyze the downstream impact of changing a specific file. Returns a list of files that depend on it.

Input Output Examples

Name	Type	Req	Description
target	string	yes	Required. The file being modified (e.g., 'src/core/types.ts').

No output schema declared.

No examples provided.

ua_init_rules ~27

Initialize a starter .ua-rules.json file in the workspace if one doesn't already exist.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ua_onboarding_doc ~32

Generate an onboarding overview document for new developers. Call this first when entering a new codebase to get oriented.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ua_precheck ~57

Pre-flight architectural risk check. Call this before modifying any critical systems or refactoring to estimate risk radius.

Input Output Examples

Name	Type	Req	Description
target	string	yes	Required. The primary file or module you plan to modify (e.g., 'src/core/db.ts').

No output schema declared.

No examples provided.

ua_rules ~23

Evaluate architectural constraints against the current knowledge graph. Generates a full violation report.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ua_rules_check ~24

Mid-session continuous audit. Evaluate constraints to ensure recent changes haven't introduced violations.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ua_scan ~31

Check if a knowledge graph file is present and currently loaded. Returns instructions on how to generate the graph if missing.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ua_status ~34

Check the operational status of the Understand-Anything MCP server. Call this to verify if the knowledge graph is successfully loaded and active.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ua_validate_graph ~43

Validate the structural integrity and syntax of the loaded knowledge graph JSON.

Input Output Examples

Name	Type	Req	Description
graphData	string	yes	Required. The raw JSON string representation of the knowledge graph to validate.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug