io.github.wrenfielddata/seo-data
Wrenfield SEO Data
Is the Wrenfield SEO Data MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-08.
Keyword search volume, CPC, domain authority, organic traffic, Google Trends and competitor ads.
needs auth probed 2026-11-14 · unchanged since 2026-11-08 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token","error_description":"Missing or invalid access token. Pass an Apify API token in the - Endpoint
- https://mcp.apify.com?tools=wrenfield-data/keyword-search-volume,wrenfield-data/ai-search-volume-checker,wrenfield-data/keyword-demand-by-country,wrenfield-data/local-keyword-demand,wrenfield-data/domain-authority-traffic-checker,wrenfield-data/google-trends-scraper,wrenfield-data/google-ads-transparency-scraper,wrenfield-data/competitor-keywords,wrenfield-data/keyword-difficulty-checker,wrenfield-data/keyword-research-tool,wrenfield-data/seo-toolkit,wrenfield-data/google-autocomplete-keyword-expander,wrenfield-data/people-also-ask-scraper,wrenfield-data/keyword-gap-report,wrenfield-data/bulk-pagespeed-checker,wrenfield-data/amazon-keyword-research (streamable-http)
- Host
- mcp.apify.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcp.apify.com?tools=wrenfield-data/keyword-search-volume,wrenfield-data/ai-search-volume-checker,wrenfield-data/keyword-demand-by-country,wrenfield-data/local-keyword-demand,wrenfield-data/domain-authority-traffic-checker,wrenfield-data/google-trends-scraper,wrenfield-data/google-ads-transparency-scraper,wrenfield-data/competitor-keywords,wrenfield-data/keyword-difficulty-checker,wrenfield-data/keyword-research-tool,wrenfield-data/seo-toolkit,wrenfield-data/google-autocomplete-keyword-expander,wrenfield-data/people-also-ask-scraper,wrenfield-data/keyword-gap-report,wrenfield-data/bulk-pagespeed-checker,wrenfield-data/amazon-keyword-research registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server console-backend.apify.com, PKCE S256, grants authorization_code, refresh_token, urn:ietf:params:oauth:grant-type:device_code.
Scopes full_api_access.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/wrenfielddata/wrenfield-mcp
- Website
- https://wrenfielddata.com
- Registry
- active, updated 2026-11-03 · registry entry
Compare this server with others.
More servers
Other registry entries on mcp.apify.com, the ones next to this name; all of them.
- MessNoMore Data Tools io.github.wong13977-oss/messnomore-data-tools · needs auth
- Wrenfield AI Search Visibility io.github.wrenfielddata/ai-search-visibility · needs auth
- Wrenfield Company Data io.github.wrenfielddata/company-data · needs auth
- Wrenfield Local Leads io.github.wrenfielddata/local-leads · needs auth
- AI Brand Visibility Tracker io.github.wulfcare/ai-brand-visibility · not probed
- Google Play & App Store reviews io.github.wulfcare/app-reviews · needs auth
- ChatGPT, Gemini, Copilot & AI Mode answers io.github.wulfcare/chatgpt-gemini-copilot-search · not probed
- Google Flights io.github.wulfcare/google-flights · not probed
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.