uiflowchartcreatorSAFE
MCP server for creating UI flowcharts
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
UIFlowchartCreator is an MCP (Model Context Protocol) server for creating UI flowcharts. This tool helps developers and designers visualize user interfaces and their interactions.
GitHub Repository
The source code for this project is available on GitHub: https://github.com/umshere/uiflowchartcreator
Features
- Generate UI flowcharts based on input specifications
- Integrate with MCP-compatible systems
- Easy-to-use API for flowchart creation
Installation
npm install uiflowchartcreator
Usage
To use UIFlowchartCreator in your MCP-compatible system, add it to your MCP configuration:
{
"mcpServers": {
"uiflowchartcreator": {
"command": "node",
"args": ["path/to/uiflowchartcreator/build/index.js"],
"env": {}
}
}
}For detailed usage instructions and API documentation, please refer to the source code and comments in src/index.ts.
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
License
This project is licensed under the ISC License.
dff64d145aa4OBSERVED · 2026-10-12Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add uiflowchartcreator --env GITHUB_TOKEN=${GITHUB_TOKEN} -- npx -y [email protected]{
"mcpServers": {
"uiflowchartcreator": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"GITHUB_TOKEN": "${GITHUB_TOKEN}"
}
}
}
}Exposed tools (1)
1 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
generate_ui_flow | read | Generate a UI flow diagram by analyzing React/Angular repositories. This tool scans the codebase to identify components, their relationships, and the overall UI structure. |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (3 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (2)
@modelcontextprotocol/sdk, axios, @types/axios, @types/node, typescript
Gates applied: no_behavioural_pass, no_license.
dff64d145aa4full audit observations/trust-audit/mcp-server/umshere__uiflowchartcreator.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-12 | dff64d145aa4 | SAFE | B | 89 | first audit |
Questions
What is the uiflowchartcreator MCP server?
MCP server for creating UI flowcharts
What tools does uiflowchartcreator expose?
1 in total: 1 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is uiflowchartcreator safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does uiflowchartcreator need?
It reads GITHUB_TOKEN from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does uiflowchartcreator run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as uiflowchartcreator at 1.0.3.
How current is this page?
The grade is for one exact copy of the source (dff64d145aa4), read on 2026-10-12. The repository is watched and re-audited when it changes.