timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Free AI search visibility audit for any website, by Search Scope, an SEO consultancy in Perth.
作者提供的原文
教 AI 做这类工作的 Skill,可与本项一起使用
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…
scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place
此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列
| 1. 在 Claude 连接器目录中 | 否 | |
|---|---|---|
| 2. 团队实测过 | 否 | |
| 3. 适合泰国用户 | 否 | |
| 4. 不计星标的使用量 | 20/100 | 热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0 |
| 5. 登记日期 | 2026-11-14 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 4/4 项(仅展示,不用于排序)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Search Scope AI Visibility Auditor。按照 https://mcp.popnx.com/i/au-searchscope-ai-visibility-auditor.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 4/4 项检查 · 你的提问会经过开发者的服务器(mcp.searchscope.com.au) · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Search Scope AI Visibility Auditorhttps://mcp.searchscope.com.au/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsSearch Scope AI Visibility Auditor
用 Search Scope AI Visibility Auditor 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Search Scope AI Visibility Auditor,或回答中出现 Search Scope AI Visibility Auditor 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Search Scope AI Visibility Auditorhttps://mcp.searchscope.com.au/mcp开启新聊天,输入前先从插件列表中选择 Search Scope AI Visibility Auditor
用 Search Scope AI Visibility Auditor 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Search Scope AI Visibility Auditor,或回答中出现 Search Scope AI Visibility Auditor 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user ai-visibility-auditor https://mcp.searchscope.com.au/mcp应能看到 Search Scope AI Visibility Auditor 在列表中并显示已连接
用 Search Scope AI Visibility Auditor 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Search Scope AI Visibility Auditor,或回答中出现 Search Scope AI Visibility Auditor 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 Search Scope AI Visibility Auditor 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Search Scope AI Visibility Auditor,或回答中出现 Search Scope AI Visibility Auditor 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 Search Scope AI Visibility Auditor 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Search Scope AI Visibility Auditor,或回答中出现 Search Scope AI Visibility Auditor 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://mcp.searchscope.com.au/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user ai-visibility-auditor https://mcp.searchscope.com.au/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"ai-visibility-auditor": {
"url": "https://mcp.searchscope.com.au/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"ai-visibility-auditor": {
"type": "http",
"url": "https://mcp.searchscope.com.au/mcp"
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
工具名称和描述与服务器在 2026年11月20日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
audit_ai_visibilityAudit a public website for AI search / GEO readiness by fetching and analysing a small prioritised sample of its pages (homepage, about, services or products, pricing, locations, key guides). Returns ten sections plus a page-by-page rewrite section: A executive summary, B entity
extract_site_entitiesBuild a practical entity map for a public website from a small sample of its pages: the primary entity (brand or organisation), related entities grouped into people, organisation/brand, products, services, locations and topics, explicit relationships (Brand -> offers -> Service,
generate_geo_query_universeGenerate a commercially useful set of AI-search prompts to monitor for a website, grouped by intent: informational, problem-aware, commercial, recommendation, comparison, alternatives, brand, category, local and trust/validation. Each prompt includes intent, buyer stage, the idea
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过域名 searchscope.com.au 验证(注册中心会核实域名所有权)
代码最后更新于4天前
不适用:由 searchscope.com.au 的所有者自己运行的云端服务器,你不会运行仓库里的代码
在 425 毫秒内响应(HTTP 200)
无需登录
已读取 3 个工具描述,未发现针对 AI 的隐藏指令
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/au-searchscope-ai-visibility-auditor)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 4 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于4天前,最新版本(1.0.0)于6天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Keyword research, site audits, rank tracking and AI visibility for your AI agent.
Official Exa MCP for web search, content fetching, and multi-step research.
Official Microsoft Learn MCP Server – real-time, trusted docs & code samples for AI and LLMs.
cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls
| 本项 Search Scope AI Visibility Auditor | OpenSEO | Exa | Microsoft Learn MCP | Docs | COTAL actions (cotal.ai) | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 是 | 是 | 是 | 否 | 否 |
| 基础检查 | 4/4 | 5/5 | 2/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | MIT | MIT | CC-BY-4.0 | NOASSERTION | Apache-2.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
A free remote MCP server from Search Scope that lets Claude, ChatGPT, Cursor and other MCP-compatible assistants audit a public website for AI search visibility, entity clarity, retrieval readiness, information gain and GEO opportunities.
Stateless, read-only, no accounts, no database, no paid APIs. The MCP endpoint needs no key; the REST API takes an optional free one.
https://mcp.searchscope.com.au/mcpAccept: application/json)https://mcp.searchscope.com.au/api/v1 (docs at mcp.searchscope.com.au/docs/api, OpenAPI 3.1 at /api/v1/openapi.json)/health returns {"status":"ok","service":"Search Scope AI Visibility Auditor"}Connect it in one line:
claude mcp add --transport http searchscope-auditor https://mcp.searchscope.com.au/mcp
Search Scope is an SEO consultancy in Victoria Park, Perth, Western Australia. It was founded in 2021 by Dorian Menard, an SEO consultant who has worked in SEO since 2013. Search Scope works with multi-location and national brands across Australia, providing multi-location SEO, national SEO, AI search visibility, Google Business Profile management and Google Maps and local SEO, with no lock-in contracts.
Search Scope built this auditor and runs it as a free public tool. It shows what an AI assistant can and cannot read about a business. If you want the fixes implemented, or ongoing tracking of whether ChatGPT, Gemini, Perplexity and Google AI Overviews actually name your brand, talk to Search Scope.
It fetches a small prioritised sample of a site (homepage, about, services or products, pricing, locations, key guides), extracts on-page signals with deterministic heuristics, and returns structured findings a professional SEO can act on. It does not call an LLM, does not measure real citations inside ChatGPT, Claude, Gemini or Google AI Overviews, and never invents evidence. Everything reported is either observed on the fetched pages or explicitly labelled as an inferred gap.
Three focused tools, following Cloudflare's guidance that a few well-described tools beat a large API surface.
audit_ai_visibilityInput: { "url": "https://example.com", "maxPages": 8 } (maxPages optional, default 8, hard maximum 15).
Returns Markdown text plus structuredContent with ten sections:
| Section | Content |
|---|---|
| A. Executive summary | Short diagnosis, six qualitative ratings, headline facts |
| B. Entity clarity | Primary entity, supporting entities, unclear relationships, confidence notes |
| C. AI retrievability | Per-page rating with the rubric, question-heading answer verdicts, site-wide issues |
| D. Information gain | First-party evidence phrases actually found (with excerpts) and what was not detected |
| E. Trust / corroboration | Named people, organisation identity, contact details, citations, credentials, third-party evidence, gaps |
| F. Internal linking / architecture | Orphan-like pages, hierarchy issues, ambiguous anchors, missing commercial-to-supporting links |
| G. Structured data | Schema types found, relevant omissions, issues; explicitly notes schema is not a ranking factor |
| H. Commercial query coverage | Inferred offerings, category, locations, likely intents with the page that covers each, gaps |
| I. Top 10 actions | Ranked by commercial impact, then AI/search visibility impact, then ease, each with evidence and, where one exists, a concrete how |
| I2. Page-by-page rewrites | The offending text quoted from the page with a prefilled replacement: opening paragraphs, opening sentences for question headings, internal links to add with suggested anchor text, and a paste-ready JSON-LD block |
| J. 20 prompts to monitor | Balanced across informational, commercial, comparison, recommendation, alternatives, brand, category, trust and local (only when a location is detected) |
extract_site_entitiesInput: { "url": "https://example.com", "maxPages": 8 }.
Returns the primary entity; related entities grouped into people, organisation/brand, products, services, locations and topics; relationships (Brand -> offers -> Service, Brand -> located in -> City, Person -> founder of -> Brand); ambiguities; missing entity support; schema types found; suggested schema types appropriate to the visible business. Every detection carries a confidence (high, medium, low) and the source it came from.
generate_geo_query_universeInput: { "url": "https://example.com", "service": "optional override", "location": "optional override", "count": 40 } (count default 40, max 100; pass location: "none" to force non-local prompts).
Returns prompts grouped by intent (informational, problem-aware, commercial, recommendation, comparison, alternatives, brand, category, local, trust/validation). Each prompt has intent, buyerStage, idealPageType and commercialPriority.
The same three tools as plain JSON endpoints, for platforms that speak HTTP rather than MCP (RapidAPI, Make, Zapier, Postman and other OpenAPI importers). Code: src/api/. The tools themselves run through src/tools/run.ts, which the MCP server uses too, so input validation, the SSRF gate, the crawl and the site-text defusing exist once.
| Endpoint | Body | Returns |
|---|---|---|
POST /api/v1/audit | url, optional maxPages | { "data": , "report": " " } |
POST /api/v1/entities | url, optional maxPages | same shape, for extract_site_entities |
POST /api/v1/queries | url, optional service, location, count | same shape, for generate_geo_query_universe |
GET /api/v1/status | none | connection test for automation platforms; crawls nothing |
POST /api/v1/keys | none | a new free API key |
GET /api/v1/openapi.json | none | OpenAPI 3.1 document, generated from the same Zod schemas the Worker validates with |
Request bodies are the MCP tools' input schemas made strict, so an unknown or misspelt field is a 400 rather than silently ignored. Errors are {"error": {"code", "message"}} with codes invalid_json, invalid_input, target_rejected (400), invalid_api_key (401), host_not_allowed, origin_not_allowed (403), payload_too_large (413), site_unreadable (422), rate_limited (429), audit_failed (500), unavailable and keys_unavailable (503). The human docs page is /docs/api.
curl -X POST https://mcp.searchscope.com.au/api/v1/audit \
-H "content-type: application/json" \ -d '{"url":"https://example.com.au"}'
Optional free keys. Every endpoint works without a key. A key exists for platforms whose connection screen insists on one, and so a misconfigured connection fails its test call with a 401 instead of silently working. Keys are issued instantly from the docs page or POST /api/v1/keys, with no sign-up and nothing stored: a key is ssk_ plus a random id plus an HMAC of that id under the API_KEY_SIGNING_SECRET Worker secret, checked in constant time. A key gives no extra allowance. It is only read from Authorization: Bearer (never from the URL), is never echoed in a response, and has its own budget the size of one client's, so a key pasted somewhere public cannot be shared out beyond that. A header that is present must hold a valid key (401 otherwise); with no signing secret set, a request that sends a key gets 503 keys_unavailable and keyless requests carry on. Keys cannot be revoked one by one; rotating the secret invalidates all of them.
RapidAPI. RapidAPI forwards every request from its own servers, so all its users would share one IP budget. When the RAPIDAPI_PROXY_SECRET Worker secret is set and a request carries a matching X-RapidAPI-Proxy-Secret header (compared in constant time), the client budget is keyed on X-RapidAPI-User instead. Without the secret, or with a wrong one, those headers are ignored and the request is limited per IP like any other, so the username header cannot be forged to dodge the limit.
Platform notes. How long an audit takes depends on the site and on maxPages; the crawl stops after 25 seconds at most (crawlBudgetMs). Zapier stops an action after 30 seconds, so integrations there should send a smaller maxPages. Make, Zapier, Pabbly and Albato call from shared servers, so at busy times their users share one client budget; per-key budgets with stored keys would be the next step if that becomes a real constraint.
Requirements: Node 22+, npm.
npm install --legacy-peer-deps # the agents SDK declares many optional peers; npm 10 needs this flag
npm run dev # wrangler dev on http://localhost:8787 curl http://localhost:8787/health
To audit a local mock site while developing (the SSRF rules reject loopback targets by default):
node scripts/mock-site.mjs 80 # serves the test fixture on http://127.0.0.1
npx wrangler dev --var DEV_ALLOW_LOOPBACK_TARGETS:1
The flag only has effect when the request itself arrives on a loopback host, so it is inert on workers.dev or a custom domain even if set by mistake.
npx @modelcontextprotocol/inspector --cli http://localhost:8787/mcp --method tools/list
npx @modelcontextprotocol/inspector --cli http://localhost:8787/mcp --method tools/call \ --tool-name audit_ai_visibility --tool-arg url=https://example.com.au maxPages=8 npx @modelcontextprotocol/inspector # web UI; connect with transport "Streamable HTTP" and the /mcp URL
Automated tests run inside the Workers runtime (workerd) via @cloudflare/vitest-plugin, so HTMLRewriter, timeouts and fetch semantics match production:
npm run typecheck
npm test
The suite covers URL validation (malformed, localhost, 127.0.0.1, private IPv4, private IPv6, cloud metadata, credentials, ports), redirect re-validation into private space, hostnames whose DNS answers point at private space, the DNS-over-HTTPS check itself (CNAME chains, AAAA-only and IPv4-mapped answers, NXDOMAIN, HTTP and network failures), maxPages and the hard cap, non-HTML and oversized responses, timeouts, sitemap and robots parsing, link extraction, de-duplication, the HTTP surface, Host and Origin checks, the request body limit, tools/list, and every tool called end to end through the official MCP client against an in-memory fixture site. test/api.test.ts covers the REST API the same way: every endpoint, the OpenAPI document (every $ref resolves, schemas match the