# HubVibe Site Audits [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/Its-fortunatefolly/HubVibe  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/hubvibe-site-audits

## Description
Rule-based site audits: accessibility, SEO, security headers, performance. Metered per call.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "hubvibe-site-audits": {
    "url": "https://hubvibe-io.com/mcp"
  }
}
```

## Documentation

## What HubVibe Site Audits does

HubVibe Site Audits MCP server provides rule-based checks for a live webpage. The service evaluates the page itself rather than asking a language model to judge compliance. Checks that cannot execute are reported as errors instead of being treated as passing results.

The available audit routes cover four areas:

- WCAG 2.1 A/AA issues on the rendered page, using axe-core.
- SEO signals including the title, meta description, headings, canonical URL, OpenGraph data, structured data, and language attribute.
- Security controls including HTTPS, HSTS, CSP, content-type sniffing protection, clickjacking protection, Referrer-Policy, and CORS.
- Performance measurements from one real page load, including DOM nodes, transferred bytes, and request count.

A bundle audit runs all four checks against one URL and charges once. WCAG and SEO also accept raw HTML input. Each completed job has a receipt available through HubVibe’s receipt endpoint.

## How it works

Send a POST request with a JSON body such as `{"url":"https://example.com"}` to an audit route. The individual checks cost $0.05 each, while the full bundle costs $0.15. An unauthenticated request returns HTTP 402 with the payment terms instead of running the audit.

An agent can read that response, sign an x402 payment using USDC on Base or an available Solana rail, and retry with the payment header. HubVibe verifies payment before execution and settles only after producing an audit result. If the audit fails to run or settlement is refused, the result is withheld and the failed call is not charged according to the README.

HubVibe Site Audits MCP server is also published at the service’s `/mcp` endpoint and listed in the official MCP registry as `io.github.Its-fortunatefolly/hubvibe`. The service publishes discovery metadata through its agent and x402 catalog documents.

## Setup and configuration

The README documents a hosted service at `https://hubvibe-io.com`; it does not provide local installation steps or server-side environment variables for the MCP endpoint. Agents can call the hosted HTTP routes directly, or use the bundled `HubVibeTollbooth` Python client for payment handling.

The tollbooth reads either `HUBVIBE_WALLET_KEY` or `HUBVIBE_API_KEY` from the environment. A wallet key is an EVM private key funded with USDC on Base. The client supports a hard maximum price before signing; the documented default for a bundle is $0.15. A prepaid API key can be supplied instead of a wallet key.

For CI, the repository provides a GitHub Action that accepts a URL and wallet key, displays findings in the job summary, and can fail a build when a regression is detected. The action also supports `fail-on-error: false` to avoid blocking deployment when the audit service itself cannot run.

## Tools and capabilities

HubVibe Site Audits exposes these audit capabilities through the hosted service:

- Run a WCAG audit on a rendered URL or supplied HTML.
- Check SEO metadata and document structure.
- Inspect selected security headers and transport protections.
- Measure basic page-load size and request characteristics.
- Run the complete four-check bundle.
- Return structured findings with rules, impact, affected nodes, and fix links where available.

## Limitations and notes

The checks are deterministic rules, not a complete human accessibility or security review. Performance values come from one page load and may not represent every device or network condition. The service audits the provided live URL, so protected, unavailable, or dynamically failing pages may produce execution errors.

Payment is required per call; the README does not describe a free audit mode. The listed prices apply to the hosted deployment and may differ on another deployment. The broader HubVibe catalog contains other workers, but those capabilities are outside the site-audit scope described here.

_Full upstream README: https://allmcps.com/mcp/hubvibe-site-audits/readme_