timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Search a product's docs, file bugs and feature requests, and hear back when they ship.
作者提供的原文
教 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
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 20/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Wicket。按照 https://mcp.popnx.com/i/stixels-wicket.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(wicketchat.com) · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 5 分钟
需要 Wicket 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Wickethttps://wicketchat.com/mcp在 Request headers 下添加这个名称和值
AuthorizationBearer <在这里粘贴你的密钥>只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsWicket
用 Wicket 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Wicket,或回答中出现 Wicket 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Wicket
Wicket 连接时需要你自己的密钥,但 OpenAI 帮助页面只说明了 OAuth 登录,没有我们能核实的填密钥方式
A · 使用能连接 Wicket 的应用
可连接 Claude Code · 约 5 分钟
需要 Wicket 的密钥(在开发者网站创建)
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user wicket https://wicketchat.com/mcp --header 'Authorization: Bearer your-value'按 Enter 前,把“your-value”改成你的密钥
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
应能看到 Wicket 在列表中并显示已连接
用 Wicket 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Wicket,或回答中出现 Wicket 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 5 分钟
需要 Wicket 的密钥(在开发者网站创建)
在 Wicket 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Wicket 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Wicket,或回答中出现 Wicket 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 5 分钟
需要 Wicket 的密钥(在开发者网站创建)
在 Wicket 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Wicket 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Wicket,或回答中出现 Wicket 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --transport http --scope user wicket https://wicketchat.com/mcp --header 'Authorization: Bearer your-value'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"wicket": {
"url": "https://wicketchat.com/mcp",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"wicket": {
"type": "http",
"url": "https://wicketchat.com/mcp",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}说明仍为英文原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月21日
注册名称已通过 GitHub 账户 Stixels 验证,该账户拥有此仓库
代码最后更新于6天前
使用 MIT
在 101 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/stixels-wicket)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:Authorization
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于6天前,最新版本(1.0.0)于7天前进入注册中心。
支持 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
| 本项 Wicket | OpenSEO | Exa | Microsoft Learn MCP | Docs | COTAL actions (cotal.ai) | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 是 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 是 | 是 | 是 | 否 | 否 |
| 基础检查 | 5/5 | 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 drop-in help and feedback chat for any web app, plus a Discord community and support inbox behind it. Users write one message. An assistant answers from your docs, and every conversation shows up in your team's Discord, where a reply goes straight back to the user in the app.
#help forum.npm install
npm run demo # open http://localhost:4317
The demo indexes the Escape Director docs, uses a scripted assistant and simulates Discord. To simulate a team reply, run curl -XPOST localhost:4317/__staff -H 'content-type: application/json' -d '{"body":"Hi!"}'.
<script src="https://YOUR-SERVER/widget.js" defer></script>
You can also call Wicket.open(), Wicket.close(), Wicket.toggle(), Wicket.ask("question") (opens the chat and sends it), Wicket.setContext({ roomId }), Wicket.setUser({...}), Wicket.setUserToken(...), Wicket.setTheme({...}), Wicket.setAnchor(element), Wicket.setQuiet(true), Wicket.addBreadcrumb("Paused game") and Wicket.destroy() (removes the widget, for example on sign-out; init brings it back) at any time. The latest context and a fresh userToken go with every message.
Recent activity for bug reports. The widget keeps a short trail of what the person did in your app: the last 20 steps from the last 5 minutes, made of page changes (path only, never the query string), clicks on buttons and links by their visible label or aria-label, and console errors. It never records what anyone types or the value of a field. Add your own steps with Wicket.addBreadcrumb(label), for example "Paused game" or "Sent Clue"; it works before init. The trail stays in the page and is sent only with a bug report: with the first message after "Report a bug", or right after the assistant logs a bug on its own (then it's added to that ticket as a comment). The server caps it, strips anything that looks like an email, card number or token, and puts it in the model's transcript and on the ticket under ## Recent activity, nowhere else. Turn it off with Wicket.init({ trail: false }).
To open the chat from a button in your app's header, hide the launcher and pass the button as anchor:
const button = document.querySelector("#help-chat");
Wicket.init({ hideLauncher: true, anchor: button }); button.addEventListener("click", () => Wicket.toggle()); const off = Wicket.on("unread", (count) => (button.dataset.count = count || ""));
quiet: true (or Wicket.setQuiet(true)) turns the previews off, for screens other people can see; unread still fires so you can show the count yourself.Wicket.on(event, callback) returns a function that unsubscribes. Events: unread (the count, on every change, including back to 0 when the chat opens), open, close, and rating ({ conversationId, messageId, rating } when someone rates an answer; rating is "up", "down" or null when they take it back). You can subscribe before init.Each assistant answer has thumbs up and down on its name line. A thumbs down offers to pass the conversation to the team. Answers can come with How we got this (the numbers behind them) and Ask next questions under the latest one. When the server asks for a bot check, visitors pass a Cloudflare Turnstile check in the panel before their first answer.
A name or id passed in user is only a label. For profiles that depend on who someone is (signed in, their plan) and for per-person budgets, your backend signs a short-lived token and the widget passes it on:
// Your backend, with the same IDENTITY_SECRET Wicket has (HS256 JWT)
jwt.sign({ sub: user.id, name: user.name, email: user.email, plan: user.plan }, process.env.WICKET_IDENTITY_SECRET, { expiresIn: "5m" });
Wicket.init({ userToken: () => fetch("/api/wicket-token").then((r) => r.json()).then((d) => d.token) });
userToken takes the token or a function that returns one. Without a valid token, the person counts as a visitor. Tokens must have an expiry (exp) no more than 24 hours out; a few minutes is best. The widget asks for a fresh one with every message.
Optional claims:
| Claim | What it does |
|---|---|
account | Bill per account instead of per person: everyone with the same account spends from one budget. |
budget | The account's (or person's) monthly AI allowance in dollars. When a profile also has a budget, the lower one applies, so your app stays in charge of the amount. |
env | Which of your environments signed it (staging, production), when one Wicket serves several. Picks the app-tools URL. |
When someone deletes their account in your app, your backend signs a token with scope: "erase" and posts it to /api/erase:
const token = jwt.sign({ sub: user.id, account: user.accountId, scope: "erase" }, process.env.WICKET_IDENTITY_SECRET, { expiresIn: "5m" });
await fetch("https://YOUR-SERVER/api/erase", { method: "POST", headers: { Authorization: Bearer ${token} } });
Wicket deletes every conversation the person started, and with account, every conversation billed to that account. That covers messages, files, the assistant's transcript and the team's Discord post. What each answer cost stays, without any words, so budgets add up. The answer is { deleted, failed }. A 502 means some Discord posts couldn't be removed yet; those conversations are kept, so call again later until you get a 200. Calling again is always safe. Only your backend should sign these tokens: an erase token never signs anyone in, and a widget's sign-in token can't erase.
Let the assistant read the signed-in person's own data, such as their results or settings, through tools your backend offers. Wicket calls them with the person's token, so your backend checks who they are on every call and Wicket never sees data they couldn't see in your app.
profiles:
default: appTools: url: https://api.example.com/wicket/tools # or { production: ..., staging: ... } keyed by the token's env
GET {url}?context= returns { instructions, tools: [{ name, description, inputSchema }] }. instructions are your rules for using the tools; they go into the assistant's prompt. inputSchema is JSON Schema.POST {url}/{name} with { input, context, evidenceStart } returns { content, evidence? }. content is what the model reads. evidence items ({ id, label, value, period?, basis?, caveats? }) show folded under the answer as "How we got this", numbered from evidenceStart + 1 so ids stay unique within an answer. Answer with a 4xx and { error } for a problem the model should hear about.context is what the widget last sent with Wicket.setContext(), for example the page, the record on screen and the date range. Wicket sends it to the model again whenever it changes.Profiles with app tools get more steps per answer (AGENT_MAX_STEPS_WITH_APP_TOOLS, 20 by default).
| Option | Default | What it does |
|---|---|---|
title, subtitle | "Help & feedback" | Header text. |
welcomeTitle, welcomeSubtitle | "Hi {first name} 👋", "How can we help you today?" | Large heading on the start screen. |
greeting | short default | Line under the start screen heading. |
suggestions | 3 quick starts | Buttons shown before the first message. Pass [] to hide them. |
placeholder | "Write a message…" | Text in the empty input. |
logoUrl | animated bot | Square image for the header and the assistant's avatar. Without one, the assistant is a small animated orb in your brand color that blinks, looks around and shows bouncing dots while it thinks. |
launcherLabel | none | Text next to the launcher icon, e.g. "Help". |
hideLauncher | false | Hide the floating button and open the panel from your own button. |
showBranding | true | The small "Powered by" line. It links to your Wicket server's home page, which is the Wicket marketing page unless SITE=false. |
theme.accentColor | #4f46e5 | Brand color. Text on it switches between white and dark automatically. |
theme.mode | "auto" | "light", "dark", or follow the visitor's system. |
theme.radius | 20 | Corner radius in px. |
theme.fontFamily | system font | Any CSS font stack your page loads. |
theme.position | "right" | "left" or "right". |
theme.offset | { x: 20, y: 20 } | Distance from the screen edges. |
theme.zIndex | very high | Stacking order. |
theme.cssVars | none | Override any internal variable, e.g. { "--wk-bg": "#fffaf5" }. |
--wk-user, --wk-user-text, --wk-user-border | accent, text on accent, none | Colors of the person's own messages, set through theme.cssVars. |
The widget renders in a shadow DOM, so your app's CSS can't break it and its CSS can't leak into your app. On phones it opens full screen.
Earlier conversations show under Recent on the start screen, and the clock button in the header lists all of them. The browser keeps each conversation's access token in localStorage (up to 50). For signed-in users (a verified userToken), the server also returns their conversations by user id, so their history, including reports and their progress, follows them to any device or browser. Visitors' history stays in the browser they used.
bot scope with these permissions: Manage Roles, Manage Channels, Move Members, View Channels, Send Messages, Send Messages in Threads, Create Public Threads, Manage Threads, Rea