io.github.prembobby39-gif/uimax-mcp

Est-ce que io.github.prembobby39-gif/uimax-mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.prembobby39-gif/uimax-mcp » est classé « Vérifié ». Aucun comportement malveillant détecté au test comportemental. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Versions auditées & empreintes

Vérifiez la version que vous utilisez : son empreinte doit correspondre à celle listée ici — sinon vous n'utilisez pas la version auditée.

⚠ La dernière version publiée (0.8.0) n'a pas encore été auditée. Un nouveau pentest est programmé ; les verdicts ci-dessous portent sur les versions listées.

Vous utilisez ce serveur ? Suivez-le (créez un compte) pour être alerté dès qu'une nouvelle version paraît ou que le verdict change.

Les 34 outils

• review_ui≈ 352 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • url · string · requis
    URL of the running application (e.g., http://localhost:3000)
  • width · number · optionnel
    Viewport width in pixels
  • height · number · optionnel
    Viewport height in pixels
  • codeDirectory · string · requis
    Absolute path to the frontend source directory (e.g., /Users/me/project/src)

  Exemple d'appel

  {"name": "review_ui", "arguments": {"url": "texte", "codeDirectory": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• export_report≈ 242 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • url · string · requis
    URL of the running application (e.g., http://localhost:3000)
  • outputPath · string · optionnel
    Output file path for the HTML report (defaults to ./uimax-report.html)
  • codeDirectory · string · requis
    Absolute path to the frontend source directory (e.g., /Users/me/project/src)

  Exemple d'appel

  {"name": "export_report", "arguments": {"url": "texte", "codeDirectory": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• quick_review≈ 170 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • url · string · requis
    URL of the page to review

  Exemple d'appel

  {"name": "quick_review", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• screenshot≈ 212 tokens

  Capture a screenshot of a webpage. Returns a PNG image that you can visually analyze for design issues, layout problems, and UI quality.

  Paramètres, retour & exemple (5)

  Paramètres

  • url · string · requis
    URL of the page to screenshot (e.g., http://localhost:3000)
  • delay · number · optionnel
    Wait time in ms after page load before capturing
  • width · number · optionnel
    Viewport width in pixels
  • height · number · optionnel
    Viewport height in pixels
  • fullPage · boolean · optionnel
    Capture the full scrollable page

  Exemple d'appel

  {"name": "screenshot", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• responsive_screenshots≈ 106 tokens

  Capture screenshots at mobile (375px), tablet (768px), and desktop (1440px) viewports. Perfect for reviewing responsive design.

  Paramètres, retour & exemple (1)

  Paramètres

  • url · string · requis
    URL of the page to capture

  Exemple d'appel

  {"name": "responsive_screenshots", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• check_dark_mode≈ 140 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • url · string · requis
    URL of the page to check

  Exemple d'appel

  {"name": "check_dark_mode", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• compare_screenshots≈ 256 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • urlA · string · requis
    First URL — the 'before' state (e.g., http://localhost:3000)
  • urlB · string · requis
    Second URL — the 'after' state (e.g., http://localhost:3001)
  • width · number · optionnel
    Viewport width in pixels
  • height · number · optionnel
    Viewport height in pixels

  Exemple d'appel

  {"name": "compare_screenshots", "arguments": {"urlA": "texte", "urlB": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• semantic_compare≈ 370 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • width · number · optionnel
    Viewport width in pixels
  • height · number · optionnel
    Viewport height in pixels
  • urlAfter · string · requis
    URL of the 'after' state (e.g., http://localhost:3001)
  • urlBefore · string · requis
    URL of the 'before' state (e.g., http://localhost:3000)
  • changeDescription · string · requis
    What was the intended change? (e.g., 'Changed the hero section background to a gradient and increased heading font size')

  Exemple d'appel

  {"name": "semantic_compare", "arguments": {"urlAfter": "texte", "urlBefore": "texte", "changeDescription": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• accessibility_audit≈ 114 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • url · string · requis
    URL of the page to audit

  Exemple d'appel

  {"name": "accessibility_audit", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• performance_audit≈ 104 tokens

  Measure Core Web Vitals and performance metrics: FCP, LCP, CLS, TBT, load time, resource count, DOM size, and JS heap usage.

  Paramètres, retour & exemple (1)

  Paramètres

  • url · string · requis
    URL of the page to measure

  Exemple d'appel

  {"name": "performance_audit", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• lighthouse_audit≈ 157 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • url · string · requis
    URL of the page to audit (e.g., http://localhost:3000)

  Exemple d'appel

  {"name": "lighthouse_audit", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pwa_audit≈ 142 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • url · string · requis
    URL of the page to check for PWA readiness (e.g., http://localhost:3000)

  Exemple d'appel

  {"name": "pwa_audit", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• security_audit≈ 134 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • url · string · requis
    URL of the page to audit for security (e.g., http://localhost:3000)

  Exemple d'appel

  {"name": "security_audit", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• unused_code≈ 141 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • url · string · requis
    URL of the page to analyze for unused code (e.g., http://localhost:3000)

  Exemple d'appel

  {"name": "unused_code", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• lcp_optimization≈ 134 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • url · string · requis
    URL of the page to analyze LCP (e.g., http://localhost:3000)

  Exemple d'appel

  {"name": "lcp_optimization", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• resource_analysis≈ 139 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • url · string · requis
    URL of the page to analyze resources (e.g., http://localhost:3000)

  Exemple d'appel

  {"name": "resource_analysis", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• analyze_code≈ 124 tokens

  Analyze frontend source code for quality issues: accessibility anti-patterns, CSS problems, component complexity, design inconsistencies, and performance concerns.

  Paramètres, retour & exemple (1)

  Paramètres

  • directory · string · requis
    Absolute path to the frontend source directory (e.g., /Users/me/project/src)

  Exemple d'appel

  {"name": "analyze_code", "arguments": {"directory": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• crawl_and_review≈ 248 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • url · string · requis
    Starting URL to crawl from (e.g., http://localhost:3000)
  • codeDir · string · optionnel
    Optional code directory path (reserved for future use)
  • maxPages · number · optionnel
    Maximum number of pages to audit (1-10, default 5)

  Exemple d'appel

  {"name": "crawl_and_review", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• save_baseline≈ 195 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • url · string · requis
    URL of the running application (e.g., http://localhost:3000)
  • codeDir · string · optionnel
    Project directory for saving .uimax-history.json (defaults to cwd)

  Exemple d'appel

  {"name": "save_baseline", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• compare_to_baseline≈ 194 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • url · string · requis
    URL of the running application (e.g., http://localhost:3000)
  • codeDir · string · optionnel
    Project directory containing .uimax-history.json (defaults to cwd)

  Exemple d'appel

  {"name": "compare_to_baseline", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• check_budgets≈ 258 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • url · string · requis
    URL of the running application (e.g., http://localhost:3000)
  • codeDir · string · optionnel
    Project directory containing .uimaxrc.json with budget config (defaults to cwd)

  Exemple d'appel

  {"name": "check_budgets", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• capture_console≈ 247 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • url · string · requis
    URL of the page to capture console logs from (e.g., http://localhost:3000)
  • waitMs · number · optionnel
    Time in ms to wait after page load for additional console messages (default 3000)

  Exemple d'appel

  {"name": "capture_console", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• capture_network≈ 215 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • url · string · requis
    URL of the page to capture network requests from (e.g., http://localhost:3000)
  • waitMs · number · optionnel
    Time in ms to wait after page load for additional network activity (default 3000)

  Exemple d'appel

  {"name": "capture_network", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• capture_errors≈ 178 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • url · string · requis
    URL of the page to capture errors from (e.g., http://localhost:3000)

  Exemple d'appel

  {"name": "capture_errors", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• navigate≈ 156 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • url · string · requis
    URL to navigate to (e.g., http://localhost:3000)

  Exemple d'appel

  {"name": "navigate", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• click≈ 192 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • url · string · optionnel
    Optional URL to navigate to before clicking
  • selector · string · requis
    CSS selector of the element to click (e.g., 'button.submit', '#login-btn')
  • waitAfter · number · optionnel
    Optional milliseconds to wait after clicking (for animations/transitions)

  Exemple d'appel

  {"name": "click", "arguments": {"selector": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• type_text≈ 228 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • url · string · optionnel
    Optional URL to navigate to before typing
  • text · string · requis
    Text to type into the element
  • selector · string · requis
    CSS selector of the input element (e.g., 'input[name="email"]', '#search')
  • clearFirst · boolean · optionnel
    Clear existing text before typing (default: false)
  • pressEnter · boolean · optionnel
    Press Enter after typing (default: false)

  Exemple d'appel

  {"name": "type_text", "arguments": {"text": "texte", "selector": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• select_option≈ 167 tokens

  Select an option from a dropdown (<select>) element by value. Returns a screenshot after selection so you can visually verify the result.

  Paramètres, retour & exemple (3)

  Paramètres

  • url · string · optionnel
    Optional URL to navigate to before selecting
  • value · string · requis
    Value of the <option> to select
  • selector · string · requis
    CSS selector of the <select> element (e.g., '#country', 'select[name="size"]')

  Exemple d'appel

  {"name": "select_option", "arguments": {"value": "texte", "selector": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• scroll≈ 186 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • url · string · optionnel
    Optional URL to navigate to before scrolling
  • amount · number · optionnel
    Pixels to scroll (default: 500)
  • direction · string · optionnel · up | down
    Scroll direction (default: 'down')
  • toSelector · string · optionnel
    CSS selector of element to scroll into view (overrides direction/amount)

  Exemple d'appel

  {"name": "scroll", "arguments": {"url": "texte", "amount": 1, "direction": "up", "toSelector": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• wait_for≈ 194 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • url · string · optionnel
    Optional URL to navigate to before waiting
  • timeout · number · optionnel
    Maximum wait time in ms (default: 10000)
  • visible · boolean · optionnel
    Wait for element to be visible, not just in DOM (default: false)
  • selector · string · requis
    CSS selector of the element to wait for

  Exemple d'appel

  {"name": "wait_for", "arguments": {"selector": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_element≈ 160 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • url · string · optionnel
    Optional URL to navigate to before inspecting
  • selector · string · requis
    CSS selector of the element to inspect

  Exemple d'appel

  {"name": "get_element", "arguments": {"selector": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_review_history≈ 182 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • url · string · optionnel
    Filter reviews by URL
  • limit · number · optionnel
    Maximum number of reviews to return (default 10)
  • codeDir · string · optionnel
    Project directory containing .uimax-reviews.json (defaults to cwd)

  Exemple d'appel

  {"name": "get_review_history", "arguments": {"url": "texte", "limit": 1, "codeDir": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_review_stats≈ 126 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • codeDir · string · optionnel
    Project directory containing .uimax-reviews.json (defaults to cwd)

  Exemple d'appel

  {"name": "get_review_stats", "arguments": {"codeDir": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• review_diff≈ 176 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • codeDir · string · optionnel
    Project directory containing .uimax-reviews.json (defaults to cwd)
  • reviewIdA · string · requis
    ID of the older review to compare
  • reviewIdB · string · requis
    ID of the newer review to compare (or 'latest' for the most recent review)

  Exemple d'appel

  {"name": "review_diff", "arguments": {"reviewIdA": "texte", "reviewIdB": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

Badge pour votre README

Ce serveur a passé le pentest comportemental. Le badge porte son nom et renvoie à cette fiche — la preuve, c'est la fiche (verdict live qu'on contrôle), pas l'image.

[![Vérifié par MCP Hub](https://dokore.fr/badge/io.github.prembobby39-gif--uimax-mcp.svg)](https://dokore.fr/serveur/io.github.prembobby39-gif--uimax-mcp)

<a href="https://dokore.fr/serveur/io.github.prembobby39-gif--uimax-mcp"><img src="https://dokore.fr/badge/io.github.prembobby39-gif--uimax-mcp.svg" alt="Vérifié par MCP Hub" height="20"></a>

Réévalué en continu : si le comportement change, le verdict tombe et le badge disparaît. Un badge qui ne pointe pas vers une fiche dokore.fr ne prouve rien. Comment ça marche

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

uimax-mcp@0.7.0