io.github.prembobby39-gif/uimax-mcp
NPM · UIMAX-MCP · SCANNED SEP 20
Frontend expert for Claude Code. Screenshots, Lighthouse, axe-core, code analysis, auto-fix.
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
- A known CVE affects extract-zip, but no fixed version has been published, so there is nothing to upgrade to. View diagnostics → Partial
- No install/post-install scripts declared.Pass
- 66 of 267 dependencies flagged as unhealthy (1 deprecated). 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 175 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3720 tokens (~109/item across 34 items; 34 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 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 34 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 34 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 io.github.prembobby39-gif/uimax-mcp server?
io.github.prembobby39-gif/uimax-mcp runs locally as an npm package, launched with npx -y uimax-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 · uimax-mcp
claude mcp add prembobby39-gif-uimax-mcp -- npx -y uimax-mcp
{
"mcpServers": {
"prembobby39-gif-uimax-mcp": {
"command": "npx",
"args": [
"-y",
"uimax-mcp"
]
}
}
} {
"servers": {
"prembobby39-gif-uimax-mcp": {
"command": "npx",
"args": [
"-y",
"uimax-mcp"
]
}
}
} codex mcp add prembobby39-gif-uimax-mcp -- npx -y uimax-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"prembobby39-gif-uimax-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"uimax-mcp"
],
"enabled": true
}
}
} openclaw mcp add prembobby39-gif-uimax-mcp --command npx --arg -y --arg uimax-mcp
mcp_servers:
prembobby39-gif-uimax-mcp:
command: "npx"
args: ["-y", "uimax-mcp"] {
"McpServers": {
"prembobby39-gif-uimax-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"uimax-mcp"
]
}
}
} assistant mcp add prembobby39-gif-uimax-mcp -t stdio -c npx -a -y uimax-mcp
{
"mcpServers": {
"prembobby39-gif-uimax-mcp": {
"command": "npx",
"args": [
"-y",
"uimax-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.
- 20 Sept 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.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 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.
- 11 Sept 26 −3
- Stability: pass → 0.77 functional
- 10 Sept 26 0
- Stability: 0.97 → pass security
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/uimax-mcp@0.7.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 →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-7pqw-9j4j-h8q3 | CVE-2026-19693 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H | no |
| GHSA-jmr9-qjv8-65gv | CVE-2026-56876 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N | no |
Background: What a vulnerability scan can and cannot prove →
Dependencies 267 packages
| Packages resolved | 267 |
|---|---|
| Deprecated | 1 |
| Stale | 64 |
| No linked repository | 1 |
| 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 →
accessibility_audit ~54
Run an automated accessibility audit using axe-core. Checks for WCAG 2.1 Level A and AA violations, reporting issues by severity with specific fix instructions.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL of the page to audit |
No output schema declared.
No examples provided.
analyze_code ~58
Analyze frontend source code for quality issues: accessibility anti-patterns, CSS problems, component complexity, design inconsistencies, and performance concerns.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | yes | Absolute path to the frontend source directory (e.g., /Users/me/project/src) |
No output schema declared.
No examples provided.
capture_console ~158
Capture all console messages (log, warn, error, info, debug) during page load. Navigates to the URL, listens for console output and uncaught exceptions, then returns structured results with message counts by level. Useful for debugging runtime issues, detecting warnings, and finding errors that only appear in the browser console. Note: Console messages may contain sensitive data (tokens, user info, etc.) — the output is returned unfiltered. This tool is FREE — runs entirely within Claude Code.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL of the page to capture console logs from (e.g., http://localhost:3000) |
| waitMs | number | – | Time in ms to wait after page load for additional console messages (default 3000) |
No output schema declared.
No examples provided.
capture_errors ~105
Capture JavaScript errors, uncaught exceptions, unhandled promise rejections, and failed resource loads (images, scripts, stylesheets, fonts) during page load. Returns structured error list with error kind, message, and source location. Useful for finding runtime JS errors and broken resources that affect user experience. This tool is FREE — runs entirely within Claude Code.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL of the page to capture errors from (e.g., http://localhost:3000) |
No output schema declared.
No examples provided.
capture_network ~128
Capture all network requests during page load with status codes, sizes, timing, and resource types. Provides a summary with total requests, failed requests, total transfer size, and breakdown by resource type. Useful for finding failed API calls, slow requests, large assets, and understanding page load behavior. This tool is FREE — runs entirely within Claude Code.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL of the page to capture network requests from (e.g., http://localhost:3000) |
| waitMs | number | – | Time in ms to wait after page load for additional network activity (default 3000) |
No output schema declared.
No examples provided.
check_budgets ~194
Check if the current site meets performance budgets defined in .uimaxrc.json. Runs fresh audits and compares results against budget thresholds for Lighthouse scores, Web Vitals, accessibility violations, and code issues. Returns pass/fail with details of any exceeded budgets. Configure budgets in .uimaxrc.json under the "budgets" key: { "budgets": { "lighthouse": { "performance": 90, "accessibility": 95 }, "webVitals": { "lcp": 2500, "cls": 0.1 }, "maxAccessibilityViolations": 0 } } This tool is FREE — runs entirely within Claude Code.
| Name | Type | Req | Description |
|---|---|---|---|
| codeDir | string | – | Project directory containing .uimaxrc.json with budget config (defaults to cwd) |
| url | string | yes | URL of the running application (e.g., http://localhost:3000) |
No output schema declared.
No examples provided.
check_dark_mode ~73
Detect whether a webpage supports dark mode. Captures two screenshots — one in light mode and one with prefers-color-scheme: dark emulated — then compares them. Returns both screenshots and a difference percentage. Great for checking if dark mode is properly implemented.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL of the page to check |
No output schema declared.
No examples provided.
click ~107
Click an element by CSS selector. Returns a screenshot after the click so you can visually verify the result. Supports standard CSS selectors. If the page hasn't been navigated yet, provide a URL to navigate first.
| Name | Type | Req | Description |
|---|---|---|---|
| selector | string | yes | CSS selector of the element to click (e.g., 'button.submit', '#login-btn') |
| url | string | – | Optional URL to navigate to before clicking |
| waitAfter | number | – | Optional milliseconds to wait after clicking (for animations/transitions) |
No output schema declared.
No examples provided.
compare_screenshots ~158
Before/after visual comparison with pixel-level diffing. Captures screenshots of two URLs at the same viewport size, computes an accurate pixel-level difference using pixelmatch, and returns BOTH images plus a red-highlighted diff image showing exactly which pixels changed. Use this to verify UI changes, compare staging vs production, or check before/after states of a redesign.
| Name | Type | Req | Description |
|---|---|---|---|
| height | number | – | Viewport height in pixels |
| urlA | string | yes | First URL — the 'before' state (e.g., http://localhost:3000) |
| urlB | string | yes | Second URL — the 'after' state (e.g., http://localhost:3001) |
| width | number | – | Viewport width in pixels |
No output schema declared.
No examples provided.
compare_to_baseline ~116
Compare the current audit state of a URL against its most recent saved baseline. Runs fresh audits, loads the previous baseline from .uimax-history.json, and shows what improved and what regressed. Use this after making changes to verify you improved the metrics you intended. This tool is FREE — runs entirely within Claude Code.
| Name | Type | Req | Description |
|---|---|---|---|
| codeDir | string | – | Project directory containing .uimax-history.json (defaults to cwd) |
| url | string | yes | URL of the running application (e.g., http://localhost:3000) |
No output schema declared.
No examples provided.
crawl_and_review ~163
Crawl multiple pages from a starting URL and run accessibility + performance audits on each. Discovers internal links from the start page, deduplicates them, and visits up to maxPages (default 5, max 10). Each page gets a screenshot, axe-core accessibility audit, and Performance API metrics. Does NOT run Lighthouse (too slow for multi-page). Use this to audit an entire site section quickly. This tool is FREE — runs entirely within Claude Code.
| Name | Type | Req | Description |
|---|---|---|---|
| codeDir | string | – | Optional code directory path (reserved for future use) |
| maxPages | number | – | Maximum number of pages to audit (1-10, default 5) |
| url | string | yes | Starting URL to crawl from (e.g., http://localhost:3000) |
No output schema declared.
No examples provided.
export_report ~146
Generate a standalone HTML report file with all audit findings embedded. Runs the full review pipeline (screenshot, accessibility, performance, code analysis) and outputs a beautiful, shareable HTML file with zero external dependencies. Use this when the user wants a downloadable/shareable report of their UI review. This tool is FREE — runs entirely within Claude Code.
| Name | Type | Req | Description |
|---|---|---|---|
| codeDirectory | string | yes | Absolute path to the frontend source directory (e.g., /Users/me/project/src) |
| outputPath | string | – | Output file path for the HTML report (defaults to ./uimax-report.html) |
| url | string | yes | URL of the running application (e.g., http://localhost:3000) |
No output schema declared.
No examples provided.
get_element ~83
Get detailed information about a DOM element: tag name, text content, all attributes, bounding box, and computed styles (color, font, background, display, visibility). Returns a screenshot so you can visually identify the element in context.
| Name | Type | Req | Description |
|---|---|---|---|
| selector | string | yes | CSS selector of the element to inspect |
| url | string | – | Optional URL to navigate to before inspecting |
No output schema declared.
No examples provided.
get_review_history ~108
View past UIMax reviews for this project. Shows when reviews were run, what scores were achieved, and how many issues were found. Use this to understand the project's frontend health over time. This tool is FREE — runs entirely within Claude Code.
| Name | Type | Req | Description |
|---|---|---|---|
| codeDir | string | – | Project directory containing .uimax-reviews.json (defaults to cwd) |
| limit | number | – | Maximum number of reviews to return (default 10) |
| url | string | – | Filter reviews by URL |
No output schema declared.
No examples provided.
get_review_stats ~70
Get aggregate statistics across all UIMax reviews for this project. Shows total reviews, score trends, most common issues, and most problematic files. This tool is FREE — runs entirely within Claude Code.
| Name | Type | Req | Description |
|---|---|---|---|
| codeDir | string | – | Project directory containing .uimax-reviews.json (defaults to cwd) |
No output schema declared.
No examples provided.
lcp_optimization ~83
Deep Largest Contentful Paint (LCP) analysis. Identifies the LCP element, measures TTFB, resource load time, and render delay. Provides specific optimization suggestions to improve LCP below the 2.5s threshold.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL of the page to analyze LCP (e.g., http://localhost:3000) |
No output schema declared.
No examples provided.
lighthouse_audit ~90
Run a full Lighthouse audit against a URL. Returns scores for Performance, Accessibility, Best Practices, and SEO (0-100), plus detailed audit findings for render-blocking resources, image optimization, unused code, and more. Heavier than performance_audit but provides industry-standard Lighthouse scores.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL of the page to audit (e.g., http://localhost:3000) |
No output schema declared.
No examples provided.
navigate ~91
Navigate to a URL and return page info. Waits for network idle before returning. Returns the final URL, page title, HTTP status code, and a screenshot so you can visually verify the page loaded correctly. Use this when you need to open a page before performing interactions, or to verify a page loads successfully.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL to navigate to (e.g., http://localhost:3000) |
No output schema declared.
No examples provided.
performance_audit ~56
Measure Core Web Vitals and performance metrics: FCP, LCP, CLS, TBT, load time, resource count, DOM size, and JS heap usage.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL of the page to measure |
No output schema declared.
No examples provided.
pwa_audit ~82
Check Progressive Web App readiness: installable manifest, service worker, HTTPS, offline capability, and more. Runs a full Lighthouse audit under the hood and extracts all PWA-related audit results with pass/fail for each requirement.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL of the page to check for PWA readiness (e.g., http://localhost:3000) |
No output schema declared.
No examples provided.
quick_review ~96
Quick design-only review. Captures a screenshot and returns it with a focused design review methodology. No code analysis, no performance audit — just visual/UX feedback. Great for rapid design iteration. After receiving the screenshot, analyze it as a senior UI designer and provide 5-10 high-impact observations with specific fixes. This tool is FREE — runs entirely within Claude Code.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL of the page to review |
No output schema declared.
No examples provided.
resource_analysis ~80
Full resource breakdown of a page: total transfer size, breakdown by type (JS, CSS, images, fonts), number of requests, top 10 largest resources, and render-blocking resources. Helps identify what is making your page heavy.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL of the page to analyze resources (e.g., http://localhost:3000) |
No output schema declared.
No examples provided.
responsive_screenshots ~52
Capture screenshots at mobile (375px), tablet (768px), and desktop (1440px) viewports. Perfect for reviewing responsive design.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL of the page to capture |
No output schema declared.
No examples provided.
review_diff ~102
Compare two specific reviews to see what changed. Shows new issues, resolved issues, and score changes. This tool is FREE — runs entirely within Claude Code.
| Name | Type | Req | Description |
|---|---|---|---|
| codeDir | string | – | Project directory containing .uimax-reviews.json (defaults to cwd) |
| reviewIdA | string | yes | ID of the older review to compare |
| reviewIdB | string | yes | ID of the newer review to compare (or 'latest' for the most recent review) |
No output schema declared.
No examples provided.
review_ui ~228
THE PRIMARY TOOL — Fully automated UI review pipeline. Captures a screenshot, runs accessibility/performance/code audits, then returns ALL data along with an expert frontend review methodology so you can generate a comprehensive review and implement fixes. Use this when the user asks to "review my UI", "audit my frontend", or "find UI issues". After receiving the results, you MUST: 1. Study the screenshot carefully for visual/UX issues 2. Analyze the audit data following the expert methodology provided 3. Generate a comprehensive review with SPECIFIC fixes (exact CSS values, code changes) 4. Implement the fixes directly in the codebase This tool is FREE — it runs entirely within Claude Code using the user's existing plan. No API keys needed.
| Name | Type | Req | Description |
|---|---|---|---|
| codeDirectory | string | yes | Absolute path to the frontend source directory (e.g., /Users/me/project/src) |
| height | number | – | Viewport height in pixels |
| url | string | yes | URL of the running application (e.g., http://localhost:3000) |
| width | number | – | Viewport width in pixels |
No output schema declared.
No examples provided.
save_baseline ~118
Save the current audit state for a URL as a baseline snapshot. Runs screenshot, accessibility, performance, and Lighthouse audits, then saves the results to .uimax-history.json in the project directory. Use this to establish a baseline before making changes, so you can compare later. This tool is FREE — runs entirely within Claude Code.
| Name | Type | Req | Description |
|---|---|---|---|
| codeDir | string | – | Project directory for saving .uimax-history.json (defaults to cwd) |
| url | string | yes | URL of the running application (e.g., http://localhost:3000) |
No output schema declared.
No examples provided.
screenshot ~111
Capture a screenshot of a webpage. Returns a PNG image that you can visually analyze for design issues, layout problems, and UI quality.
| Name | Type | Req | Description |
|---|---|---|---|
| delay | number | – | Wait time in ms after page load before capturing |
| fullPage | boolean | – | Capture the full scrollable page |
| height | number | – | Viewport height in pixels |
| url | string | yes | URL of the page to screenshot (e.g., http://localhost:3000) |
| width | number | – | Viewport width in pixels |
No output schema declared.
No examples provided.
scroll ~100
Scroll the page by a pixel amount or to a specific element. Returns a screenshot after scrolling so you can visually verify the new viewport position.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Pixels to scroll (default: 500) |
| direction | string | – | Scroll direction (default: 'down') |
| toSelector | string | – | CSS selector of element to scroll into view (overrides direction/amount) |
| url | string | – | Optional URL to navigate to before scrolling |
No output schema declared.
No examples provided.
security_audit ~72
Check security posture via Lighthouse: HTTPS usage, mixed content, CSP headers, vulnerable JavaScript libraries, external links without noopener, and more. Returns pass/fail findings with severity levels.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL of the page to audit for security (e.g., http://localhost:3000) |
No output schema declared.
No examples provided.
select_option ~91
Select an option from a dropdown (<select>) element by value. Returns a screenshot after selection so you can visually verify the result.
| Name | Type | Req | Description |
|---|---|---|---|
| selector | string | yes | CSS selector of the <select> element (e.g., '#country', 'select[name="size"]') |
| url | string | – | Optional URL to navigate to before selecting |
| value | string | yes | Value of the <option> to select |
No output schema declared.
No examples provided.
semantic_compare ~224
AI-powered visual comparison. Captures before/after screenshots and provides a structured methodology for Claude to semantically evaluate whether UI changes match the intended design request. Goes beyond pixel diffing to understand intent. Returns both screenshots as images, a pixel-level diff image, the difference percentage, and a detailed semantic methodology prompt. Claude's vision analyzes the screenshots to determine if the changes match what was requested, checking for regressions and unintended side effects. This tool is FREE — it runs entirely within Claude Code using the user's existing plan. No API keys needed.
| Name | Type | Req | Description |
|---|---|---|---|
| changeDescription | string | yes | What was the intended change? (e.g., 'Changed the hero section background to a gradient and increased heading font size') |
| height | number | – | Viewport height in pixels |
| urlAfter | string | yes | URL of the 'after' state (e.g., http://localhost:3001) |
| urlBefore | string | yes | URL of the 'before' state (e.g., http://localhost:3000) |
| width | number | – | Viewport width in pixels |
No output schema declared.
No examples provided.
type_text ~131
Type text into an input field or textarea by CSS selector. Returns a screenshot after typing so you can visually verify the result. Options to clear existing text first and press Enter after typing.
| Name | Type | Req | Description |
|---|---|---|---|
| clearFirst | boolean | – | Clear existing text before typing (default: false) |
| pressEnter | boolean | – | Press Enter after typing (default: false) |
| selector | string | yes | CSS selector of the input element (e.g., 'input[name="email"]', '#search') |
| text | string | yes | Text to type into the element |
| url | string | – | Optional URL to navigate to before typing |
No output schema declared.
No examples provided.
unused_code ~79
Find unused JavaScript and CSS on a page. Runs Lighthouse and extracts the unused-javascript and unused-css-rules audits, showing each resource with total bytes, unused bytes, and potential savings. Great for reducing bundle size.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL of the page to analyze for unused code (e.g., http://localhost:3000) |
No output schema declared.
No examples provided.
wait_for ~113
Wait for an element to appear in the DOM. Returns the element's tag name and text content when found. Use this to wait for dynamic content to load before interacting with it.
| Name | Type | Req | Description |
|---|---|---|---|
| selector | string | yes | CSS selector of the element to wait for |
| timeout | number | – | Maximum wait time in ms (default: 10000) |
| url | string | – | Optional URL to navigate to before waiting |
| visible | boolean | – | Wait for element to be visible, not just in DOM (default: false) |
No output schema declared.
No examples provided.
What is the io.github.prembobby39-gif/uimax-mcp server?
io.github.prembobby39-gif/uimax-mcp is listed in the public MCP registry as io.github.prembobby39-gif/uimax-mcp. Frontend expert for Claude Code. Screenshots, Lighthouse, axe-core, code analysis, auto-fix. This page covers its npm package (uimax-mcp).
Is the io.github.prembobby39-gif/uimax-mcp server safe to use?
io.github.prembobby39-gif/uimax-mcp scores 84 out of 100 on VerifyMCP. We recorded 2 known advisories against 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 io.github.prembobby39-gif/uimax-mcp server expose?
io.github.prembobby39-gif/uimax-mcp exposes 34 tools: review_ui, export_report, quick_review, screenshot, responsive_screenshots, and 29 more. Their descriptions and schemas cost roughly 3,720 tokens of context every time the server is loaded.
Is the io.github.prembobby39-gif/uimax-mcp server still maintained?
io.github.prembobby39-gif/uimax-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 io.github.prembobby39-gif/uimax-mcp server under?
io.github.prembobby39-gif/uimax-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.