@enemyrr/mcp-server-pagespeed

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is @enemyrr/mcp-server-pagespeed?

@enemyrr/mcp-server-pagespeed is a Model Context Protocol server that provides Google PageSpeed Insights analysis, enabling AI models to analyze webpage performance through a standardized interface.

how to use @enemyrr/mcp-server-pagespeed?

To use the server, clone the repository, build the project, and add it to Cursor IDE settings. You can also run it directly from the command line using npx mcp-server-pagespeed.

key features of @enemyrr/mcp-server-pagespeed?

  • Real-time webpage performance analysis
  • Detailed loading experience metrics
  • Prioritized improvement suggestions
  • Comprehensive error handling
  • TypeScript support

use cases of @enemyrr/mcp-server-pagespeed?

  1. Analyzing webpage performance for SEO optimization.
  2. Providing developers with insights on loading times and user experience.
  3. Generating improvement suggestions for better webpage performance.

FAQ from @enemyrr/mcp-server-pagespeed?

  • What does the analyze_pagespeed tool do?

It analyzes a webpage using the Google PageSpeed Insights API and returns performance scores and improvement suggestions.

  • How do I handle errors?

The server provides detailed error messages for invalid URLs, API request failures, and connection issues.

  • Can I contribute to the project?

Yes! Contributions are welcome, and you can submit a Pull Request on GitHub.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago