Ask your AI why a landing page is slow, and what to fix first.
Google Lighthouse scores for performance, accessibility, SEO and best practices, plus real-user Core Web Vitals — LCP, INP and CLS — where Google has field data for the page, answered inside ChatGPT, Claude, Codex or Cursor. No Google Cloud project or key of your own: toolfare runs each audit through the same connection.
1Connect your AI app
Pick the app you use. You do this once, and every API on toolfare is then available in it.
Add toolfare as a connector in Claude
Add to Claudehttps://api.toolfare.ai/mcp
- 1Open Customize → Connectors and choose "Add custom connector".
- 2Paste this URL as the remote MCP server URL.
- 3Leave the OAuth client id and secret under Advanced settings empty.
- 4Complete the browser authorization, then return to your conversation.
Custom connectors are available on Free, Pro, Max, Team and Enterprise. A Free account may hold one custom connector in total.
Claude’s own instructions2What to ask
Copy a prompt into your AI app once you’re connected. It picks the right one of the 1 tools and tells you the price first.
Lighthouse scores and Core Web Vitals
FreePerformance, accessibility, best practices and SEO scores of a public page
- “Why is this landing page slow?”
- “Check the Core Web Vitals for our homepage.”
- “Run a Lighthouse audit on our pricing page and tell me what to fix first.”
1Create an API key
One key and one endpoint for every API on toolfare.
export TOOLFARE_API_KEY='tf_live_…'
2Every tool and its input
Send the tool name and its arguments as JSON; the reply is JSON too.
pagespeed_runPerformance, accessibility, best practices and SEO scores of a public page
Free
Required parameters:
urlOptional parameters:
categories, locale, strategy
Use it when
- Someone asks why a page is slow, or what to fix first.
- You need Core Web Vitals for a landing page before or after a change.
- You want an SEO or accessibility audit of a single page.
Look elsewhere when
- The page is not publicly reachable. Google fetches it itself, so a staging URL behind a login cannot be measured.
- You want the site’s search rankings or traffic rather than its speed. Use this instead
PageSpeed directly, or through toolfare
Directly
- The PageSpeed Insights website, one URL at a time
- A Google Cloud project and API key for higher rate limits
- Your own code to read Lighthouse JSON
Through toolfare
- Quoted before it runs — at zero — on the same balance as everything else
- No Google Cloud project and no key to hand to an agent
- Page speed beside traffic and SEO data in the same question
You get the same free audit Google offers, asked from your chat. Nothing is monitored over time, and no fix is applied for you — the value is in the conversation, not in exclusive data.
Limits
- Public URLs only.
- Field Core Web Vitals appear only where Google has enough real-user data for the page; otherwise you get the lab scores alone.
- A single audit is a single run — scores move between runs, so compare like with like.
- Pay as you go from your toolfare balance, in US dollars; there is no subscription. A call runs when your balance covers its quote.