Understand Anything - MCP
NPM · UA-MCP · SCANNED SEP 20
A powerful MCP server for codebase architecture analysis and automated governance.
Available components
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
- 34 of 114 dependencies flagged as unhealthy. 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 62 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).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 Management90
- Stability observed for 27 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 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
How do I install the Understand Anything - MCP server?
Understand Anything - MCP runs locally as an npm package, launched with npx -y ua-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · ua-mcp
claude mcp add uamcp-ua-mcp -- npx -y ua-mcp
{
"mcpServers": {
"uamcp-ua-mcp": {
"command": "npx",
"args": [
"-y",
"ua-mcp"
]
}
}
} {
"servers": {
"uamcp-ua-mcp": {
"command": "npx",
"args": [
"-y",
"ua-mcp"
]
}
}
} codex mcp add uamcp-ua-mcp -- npx -y ua-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"uamcp-ua-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"ua-mcp"
],
"enabled": true
}
}
} openclaw mcp add uamcp-ua-mcp --command npx --arg -y --arg ua-mcp
mcp_servers:
uamcp-ua-mcp:
command: "npx"
args: ["-y", "ua-mcp"] {
"McpServers": {
"uamcp-ua-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"ua-mcp"
]
}
}
} assistant mcp add uamcp-ua-mcp -t stdio -c npx -a -y ua-mcp
{
"mcpServers": {
"uamcp-ua-mcp": {
"command": "npx",
"args": [
"-y",
"ua-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 17 Sept 26 −3
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 14 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
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 20 Sept 2026 · Analysed npm/ua-mcp@1.2.16
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 114 packages
| Packages resolved | 114 |
|---|---|
| Stale | 34 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
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 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.
| 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 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.
| 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.
| 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 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.
| 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 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 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.
| 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 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 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 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 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.
| 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.
What is the Understand Anything - MCP server?
Understand Anything - MCP is listed in the public MCP registry as io.github.uamcp/ua-mcp. A powerful MCP server for codebase architecture analysis and automated governance. This page covers its npm package (ua-mcp).
Is the Understand Anything - MCP server safe to use?
Understand Anything - MCP scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 Understand Anything - MCP server expose?
Understand Anything - MCP exposes 15 tools: ua_status, ua_scan, ua_graph_summary, ua_architecture_report, ua_dependency_report, and 10 more. Their descriptions and schemas cost roughly 643 tokens of context every time the server is loaded.
Is the Understand Anything - MCP server still maintained?
Understand Anything - MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 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 Understand Anything - MCP server under?
Understand Anything - 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.