← Registry

Developer Tools

vitalsbeacon.com

Measures web page performance and quality using a real Lighthouse run in a real browser.

1 endpoint1 known toolsFirst detected August 27, 2026Last detected August 27, 2026

ENDPOINT 1

https://api.vitalsbeacon.com/mcp

No auth detected

MCP server metadata

Name
vitalsbeacon
Version
1.2.0
Capabilities
tools
Server instructions

Run a real Lighthouse audit on any public web page. No API key and no signup. Free, 50 calls per hour per IP address, with results cached for 24 hours. A fresh audit takes 20 to 60 seconds and audits run one at a time, so allow for a wait. Performance scores are noisy on shared hardware: report a single run as a band, not an exact figure.

Known tools 1

audit_performance

Measure how fast and how well-built a public web page is, using a real Lighthouse run in a real browser.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.vitalsbeacon]
url = "https://api.vitalsbeacon.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "vitalsbeacon": {
      "type": "http",
      "url": "https://api.vitalsbeacon.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: vitalsbeacon
Remote MCP URL: https://api.vitalsbeacon.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "vitalsbeacon": {
      "url": "https://api.vitalsbeacon.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "vitalsbeacon": {
      "type": "http",
      "url": "https://api.vitalsbeacon.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "vitalsbeacon",
  "transport": "streamable-http",
  "url": "https://api.vitalsbeacon.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.