World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Autonomous UX and a11y audit, fix, and verify loop. 38 tools, framework-aware patches.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 3/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 3/100 |
Quality: Passed 2/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Vertaaux MCP. Follow https://mcp.popnx.com/i/petrilahdelma-vertaaux-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 2/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Vertaaux MCP for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "vertaaux": { "command": "npx", "args": [ "-y", "@vertaaux/mcp-server" ], "env": { "VERTAAUX_API_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For VERTAAUX_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Vertaaux MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
SettingsDeveloperEdit Config
{
"mcpServers": {
"vertaaux": {
"command": "npx",
"args": [
"-y",
"@vertaaux/mcp-server"
],
"env": {
"VERTAAUX_API_KEY": "your-value"
}
}
}
}Paste the key only into the app’s field, never into a chat or to anyone
Use Vertaaux MCP and tell me what you can do for me, then show me one thing✓ If Claude says it is using Vertaaux MCP or shows a Vertaaux MCP tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Vertaaux MCP yet
Vertaaux MCP runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Vertaaux MCP
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
You need a Vertaaux MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Vertaaux MCP for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user vertaaux --env VERTAAUX_API_KEY=your-value -- npx -y @vertaaux/mcp-server 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For VERTAAUX_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Vertaaux MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user vertaaux --env VERTAAUX_API_KEY=your-value -- npx -y @vertaaux/mcp-serverReplace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
You should see Vertaaux MCP listed as connected
Use Vertaaux MCP and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Vertaaux MCP or shows a Vertaaux MCP tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
You need a Vertaaux MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Vertaaux MCP for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "vertaaux": { "command": "npx", "args": [ "-y", "@vertaaux/mcp-server" ], "env": { "VERTAAUX_API_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For VERTAAUX_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Vertaaux MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
In the Vertaaux MCP settings, VERTAAUX_API_KEY is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Vertaaux MCP and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Vertaaux MCP or shows a Vertaaux MCP tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
You need a Vertaaux MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Vertaaux MCP for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "vertaaux": { "type": "stdio", "command": "npx", "args": [ "-y", "@vertaaux/mcp-server" ], "env": { "VERTAAUX_API_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For VERTAAUX_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Vertaaux MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
In the Vertaaux MCP settings, VERTAAUX_API_KEY is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Vertaaux MCP and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Vertaaux MCP or shows a Vertaaux MCP tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user vertaaux --env VERTAAUX_API_KEY=your-value -- npx -y @vertaaux/mcp-serverClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"vertaaux": {
"command": "npx",
"args": [
"-y",
"@vertaaux/mcp-server"
],
"env": {
"VERTAAUX_API_KEY": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"vertaaux": {
"command": "npx",
"args": [
"-y",
"@vertaaux/mcp-server"
],
"env": {
"VERTAAUX_API_KEY": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"vertaaux": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@vertaaux/mcp-server"
],
"env": {
"VERTAAUX_API_KEY": "your-value"
}
}
}
}VERTAAUX_API_KEY secret required envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The publisher (PetriLahdelma) is not the repo owner (VertaaUX); someone else may have listed it
Code last changed 5 months ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for @vertaaux/mcp-server@1.2.2
Checks only this package version, not every dependency · checked Nov 16, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/petrilahdelma-vertaaux-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 2 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: VERTAAUX_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 5 months ago, and the latest version (1.2.2) reached the registry 6 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| This one Vertaaux MCP | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | Yes | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 2/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
The only MCP server with an autonomous audit, fix, and verify loop. Detects UX and accessibility issues across 7 categories, generates framework-aware patches (React, Vue, Angular, Svelte), opens atomic GitHub PRs via the Git Trees API, and verifies the fix landed in production. Built for CI/CD pipelines with policy-as-code thresholds.
suggest_fix detects React/Vue/Angular/Svelte/Nuxt via the nearest package.json and emits idiomatic patches (JSX rewrites for React, HTML attrs preserved elsewhere).generate_pr applies N patches in a single commit or zero. Conflict graph + AST gate (Babel, vue-eslint-parser, svelte/compiler) refuse unparseable patches before they reach the PR.rule:hash format stable across audit runs so agents can reference findings without storing state.audit_a11y combines axe-core, AccessLint, and VertaaUX analyzers in a single call.policy_check mirrors the GitHub Action's threshold evaluator exactly so CI and agent verdicts match.@modelcontextprotocol/sdknpx -y @modelcontextprotocol/cli install io.github.PetriLahdelma/vertaaux-mcp
npm install -g @vertaaux/mcp-server
VERTAAUX_API_KEY=vx_live_... vertaaux-mcp
Drift policy:
smithery.yaml,glama.json, andserver.jsonare auto-generated from the live MCP tool registry bynpm run generate:manifests. Never hand-edit them. Seedocs/REGISTRY-PUBLISHING.mdfor the runbook.
# Install & build
npm install && npm run build
VERTAAUX_API_KEY=vx_live_... npm start
VERTAAUX_API_KEY=vx_live_... npm run start:http
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": { "vertaaux": { "command": "node", "args": ["/path/to/mcp-server/dist/index.js"], "env": { "VERTAAUX_API_KEY": "vx_live_..." } } } }
Add to .vscode/settings.json:
{
"mcp.servers": { "vertaaux": { "command": "node", "args": ["./mcp-server/dist/index.js"], "env": { "VERTAAUX_API_KEY": "vx_live_..." } } } }
Add to .cursor/mcp.json:
{
"mcpServers": { "vertaaux": { "command": "node", "args": ["/path/to/mcp-server/dist/index.js"], "env": { "VERTAAUX_API_KEY": "vx_live_..." } } } }
| Variable | Required | Default | Purpose |
|---|---|---|---|
VERTAAUX_API_KEY | Yes | — | API authentication key |
VERTAAUX_API_BASE | No | https://vertaaux.ai/api/v1 | API endpoint URL |
PORT | No | 8787 | HTTP transport port |
GITHUB_TOKEN | No | — | GitHub API access for generate_pr |
| Tool | Description |
|---|---|
| `audit_url` | Run UX & accessibility audit on a deployed URL. Returns top 5 issues with severity breakdown. |
| `audit_repo` | Static analysis on local codebase (React/Vue/Svelte/HTML). Finds missing alt text, unlabeled buttons/inputs/links. |
| `audit_artifact` | Audit from HAR files (response times, failed requests, large payloads) or Lighthouse JSON (accessibility findings). |
| `get_findings` | Retrieve findings from a completed audit with filtering by severity, rule, and pagination. |
| `get_audit` | Get audit job status and results by job ID. |
| Tool | Description |
|---|---|
| `explain_finding` | Deep-dive into a finding: WCAG criteria, repro steps, fix guidance, before/after code examples. |
| `suggest_fix` | Generate search/replace patch with confidence score. Supports single and batch mode. |
| `generate_patch` | Generate accessibility fix patch for a specific issue from an audit. |
| `run_verification_suite` | Verify a patch fixes the issue without regressions via before/after audit. |
| `generate_pr` | Create a draft GitHub PR with fix patches. Requires GITHUB_TOKEN. |
| `create_pr_comment` | Generate a PR comment with suggestion blocks, ordered by severity. |
| Tool | Description |
|---|---|
| `analyze_component` | Heuristic UX review of component code (no browser needed). Checks images, buttons, inputs, links. |
| `run_llm_audit` | Provider-agnostic LLM audit (Mistral/OpenAI via Vertaa adapter). |
| `capture_screenshot` | Capture screenshot by running a quick audit. |
| `compare_competitors` | Compare UX metrics against competitor URLs with category-level score deltas. |
| `explain_issue` | Format an issue into developer-friendly markdown guidance. |
| Tool | Description |
|---|---|
| `create_webhook` | Register webhook for audit notifications. |
| `list_webhooks` / `delete_webhook` | Manage webhooks. |
| `create_schedule` | Cron-based scheduled audits with score threshold alerts. |
| `get_schedule` / `list_schedules` / `update_schedule` / `delete_schedule` | Manage schedules. |
| `get_quota` | Check plan and remaining credits. |
| `get_engines` | List available engine versions. |
| Tool | Description |
|---|---|
| `audit_a11y` | Multi-engine accessibility audit using axe-core, AccessLint, and custom analyzers. Returns WCAG-mapped findings with structured fix suggestions and fixability ratings. Supports min_impact filtering and mode (basic/standard/deep). |
| `diff_a11y` | Compare current accessibility findings against a saved baseline. Returns fixed, new, and unchanged findings with net change summary. Requires a prior audit_a11y call to establish the baseline. |
| Tool | Description |
|---|---|
| `run_audit` | DEPRECATED — Use audit_url instead. |
Pre-built workflow prompts for common audit scenarios:
| Prompt | Description | Arguments |
|---|---|---|
| `quick_audit` | Audit a URL and summarize top issues with fix recommendations | url |
| `fix_accessibility` | Full audit → patch → PR comment workflow | url |
| `compare_ux` | Compare against competitors and identify UX gaps | url, competitors, industry? |
| `monitor_regression` | Set up scheduled monitoring with alerts | url, frequency? |
| `audit_codebase` | Static analysis on local codebase | path |
The server exposes MCP resources via vertaa:// URIs:
| URI Pattern | Description |
|---|---|
vertaa://audits/{auditId} | Full audit result |
vertaa://audits/{auditId}/summary | Lightweight summary |
vertaa://audits/{auditId}/findings/{findingId} | Single finding detail |
vertaa://screenshots/{auditId} | Screenshot metadata |
vertaa://screenshots/{auditId}/annotated | Annotated screenshot |
vertaa://history/{encodedUrl} | Audit history for URL |
vertaa://history/{encodedUrl}/trend | Score trend analysis |
vertaa://guidelines/{topic} | UX guidelines (buttons, forms, navigation, color-contrast, errors, content) |
Configure domain allowlists, rate limits, and PII redaction programmatically:
import { configureEnterpriseControls } from './server.js';
configureEnterpriseControls({ allowlist: { allowed_domains: ['*.example.com'], denied_domains: ['internal.example.com'], }, budget: { max_requests: 100, max_pages: 50, max_duration_ms: 60000, max_concurrency: 3, }, redaction: { redact_emails: true, redact_phone_numbers: true, redact_credit_cards: true, custom_patterns: [ { name: 'api_key', pattern: 'sk_[a-zA-Z0-9]{20,}', replacement: '[REDACTED]' } ], }, });
1. audit_url({ url: "https://example.com", mode: "deep" })
→ Returns audit_id with top 5 issues
mcp-server/
├── src/ │ ├── index.ts # Main entry, tool registration │ ├── server.ts # MCP server config, resources, middleware │ ├── a11y-tools.ts # Multi-engine a11y audit & baseline diffing tools │ ├── http.ts # HTTP transport entry point │ ├── prompts.ts # MCP prompt templates │ ├── analysis.ts # Component analysis engine │ ├── patch.ts # Patch generation │ ├── verification.ts # Patch verification │ ├── pr-comment.ts # PR comment generation │ ├── tools/ │ │ ├── audit-url.ts # audit_url tool │ │ ├── audit-repo.ts # audit_repo tool (static analysis) │ │ ├── audit-artifact.ts # audit_artifact tool (HAR/Lighthouse) │ │ ├── get-findings.ts # get_findings tool │ │ ├── explain-finding.ts# explain_finding tool │ │ ├── suggest-fix.ts # suggest_fix tool │ │ ├── generate-pr.ts # generate_pr tool │ │ └── index.ts # Tool exports │ ├── transports/ │ │ ├── stdio.ts # Stdio transport (default) │ │ └── http.ts # HTTP streaming transport │ ├── middleware/ │ │ ├── allowlist.ts # Domain/path allowlist │ │ ├── budget.ts # Rate limiting & quotas │ │ ├── redaction.ts # PII redaction │ │ └── index.ts # Middleware stack │ ├── resources/ │ │ ├── audit-results.ts # vertaa://audits/* resources │ │ ├── screenshots.ts # vertaa://screenshots/* resources │ │ ├── historical.ts # vertaa://history/* resources │ │ ├── legacy.ts # Guidelines resources │ │ └── index.ts # Resource exports │ ├── schemas/ │ │ ├── audit.ts # Audit schemas (mode, findings) │ │ ├── findings.ts # Finding schemas │ │ ├── controls.ts # Enterprise control schemas │ │ ├── errors.ts # Error schemas │ │ └── index.ts │ ├── utils/ │ │ ├── error-recovery.ts # Structured errors with recovery guidance │ │ ├── change-tracker.ts # Baseline change tracking │ │ └── deterministic-id.ts # Stable finding IDs │ └── index.test.ts # Test suite ├── README.md ├── package.json ├── tsconfig.json └── vitest.config.ts
npm test # Run test suite
npm run test:watch # Watch mode npm run test:coverage # Coverage report
npm run build # TypeScript → dist/
All errors include structured recovery guidance:
{
"code": "AUDIT_NOT_FOUND", "message": "Audit abc123 not found.", "recovery": { "action": "Start a new audit for this URL", "tool": "audit_url", "params": { "url": "h