x=hub

your toolset

    build deployment
    sign in

    PageSpeed Insights MCP

    mcpother official scan blocked
    com.considus/pagespeed-insights-mcp · v1.5.1
    deploy just this

    One run is noise, so this reports the median of several distinct PageSpeed analyses and the spread.

    run it

    blocked by the security scan
    Blocked by the security scanThe worker scanned github.com/considus/pagespeed-insights-mcp at 2985ed379b98 for v1.5.1 with [email protected][email protected] on 2026-10-17, before building it, and found code that looks malicious: threat-filesystem-autostart in setup.py:207, threat-filesystem-autostart in setup.py:731. It built nothing, and the hub offers no way to run this version: no package, no image, no build, no web service. An operator can look at the findings and let it run; a new version is scanned again.

    connect to it

    copy what your client needs
    {
      "mcpServers": {
        "pagespeed-insights": {
          "command": "CHANGE_ME",
          "args": []
        }
      }
    }
    #!/usr/bin/env bash
    # Registers every server with Claude Code (run once; `claude mcp list` to check).
    set -euo pipefail
    set -a; [ -f .env ] && source .env; set +a
    claude mcp add pagespeed-insights -- CHANGE_ME
    
    {
      "mcpServers": {
        "pagespeed-insights": {
          "command": "CHANGE_ME",
          "args": []
        }
      }
    }
    {
      "servers": {
        "pagespeed-insights": {
          "type": "stdio",
          "command": "CHANGE_ME",
          "args": []
        }
      }
    }
    name: my-agent
    target: local
    servers:
    - hub: com.considus/pagespeed-insights-mcp
    
    • not probed yet: tools unpinned, ingest lists them
    • blocked: the worker's security scan of github.com/considus/pagespeed-insights-mcp at 2985ed379b98 on v1.5.1 found code that looks malicious (threat-filesystem-autostart); nothing is deployed for it

    tools

    Probe result: faileddocker: security scan: github.com/considus/pagespeed-insights-mcp at 2985ed379b98 has code that looks malicious: threat-filesystem-autostart in setup.py:207, threat-filesystem-autostart in setup.py:731

    runs · 1

    the latest tests of this entry by the hub and its workers, newest first
    dateworkermethodstatussandboxreason
    2026-10-17 15:17 local-mac-vm docker failed gvisor docker: security scan: github.com/considus/pagespeed-insights-mcp at 2985ed379b98 has code that looks malicious: threat-filesystem-autostart in setup.py:207, th…