Home / MCP registry index / online.pageaudit/pageaudit

Pageaudit

online.pageaudit/pageaudit in the official MCP registry. Endpoint https://pageaudit.online/mcp. Source: github.com/wrpbr/pageaudit.

The registry describes it as: Technical SEO, passive security and page-delivery audits with evidence and suggested fixes.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http pageaudit https://pageaudit.online/mcp

{
  "mcpServers": {
    "pageaudit": {
      "url": "https://pageaudit.online/mcp"
    }
  }
}

code --add-mcp '{"name":"pageaudit","type":"http","url":"https://pageaudit.online/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

list_sites add_site get_site search_console track_search_queries connect_search_console sync_search_console disconnect_search_console prompt_allowance generate_fix_prompt generate_domain_fix_prompt generate_site_fix_prompt get_fix_prompt list_audit_fix_prompts list_domain_fix_prompts list_site_fix_prompts weekly_site_report save_weekly_site_report weekly_site_report_history ai_search_visibility ai_search_history save_ai_search_queries journeys configure_journeys connection_review review_connection cancel_connection_review domain_portfolio preview_domain_alerts apply_domain_alerts domain_status check_domain set_domain_expiry configure_domain_dns configure_domain_monitor domain_history acknowledge_domain_event audit_site check_ai_access api_index health list_tools get_tool audit_url create_guest list_tabs create_tab run_tab tab_history watch_tab lab_test lab_result get_audit get_badge embed_snippet billing list_plans buy_plan cancel_plan contact and 2 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-30): 756246058dfffd36. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/online-pageaudit-pageaudit/badge.svg)](https://lazaretto.dev/mcp-registry/online-pageaudit-pageaudit)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Analytics and SEO MCP servers · Security MCP servers