timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Deploy full-stack apps (frontend, backend, Postgres, Redis) from your agent and get live URLs.
教 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-10 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 5/5 项(仅展示,不用于排序)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Rivtor。按照 https://mcp.popnx.com/i/rivtor.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(api.rivtor.com) · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Rivtorhttps://api.rivtor.com/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsRivtor
用 Rivtor 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Rivtor,或回答中出现 Rivtor 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Rivtorhttps://api.rivtor.com/mcp开启新聊天,输入前先从插件列表中选择 Rivtor
用 Rivtor 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Rivtor,或回答中出现 Rivtor 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user rivtor https://api.rivtor.com/mcp应能看到 Rivtor 在列表中并显示已连接
用 Rivtor 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Rivtor,或回答中出现 Rivtor 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 Rivtor 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Rivtor,或回答中出现 Rivtor 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 Rivtor 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Rivtor,或回答中出现 Rivtor 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://api.rivtor.com/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user rivtor https://api.rivtor.com/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"rivtor": {
"url": "https://api.rivtor.com/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"rivtor": {
"type": "http",
"url": "https://api.rivtor.com/mcp"
}
}
}Claude Code
claude mcp add --scope user rivtor -- npx -y rivtor mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"rivtor": {
"command": "npx",
"args": [
"-y",
"rivtor",
"mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"rivtor": {
"command": "npx",
"args": [
"-y",
"rivtor",
"mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"rivtor": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"rivtor",
"mcp"
]
}
}
}RIVTOR_TOKEN 机密 env说明仍为英文原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过域名 rivtor.com 验证(注册中心会核实域名所有权)
代码最后更新于9天前
使用 MIT
在 899 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
OSV.dev 中没有 rivtor@0.6.1 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/rivtor)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于9天前,最新版本(1.2.1)于9天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:QueryWeaver, Supabase, Neon, DBCode, Keboola MCP
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
An MCP server for Text2SQL: transforms natural language into SQL using graph schema understanding.
Official Neon MCP server for managing Neon projects and Lakebase Postgres databases.
Connect your AI assistants to Keboola and expose your data, transformations, SQL queries, ...
| 本项 Rivtor | QueryWeaver | Supabase | Neon | DBCode | Keboola MCP | |
|---|---|---|---|---|---|---|
| 运行位置 | 云端或安装在电脑上都可以 | 需要安装在电脑上 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 需要安装在电脑上 | 云端或安装在电脑上都可以 |
| 需要密钥 | 否 | 否 | 是 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 是 | 是 | 否 | 否 |
| 基础检查 | 5/5 | 3/3 | 5/5 | 5/5 | 2/3 | 5/5 |
| 许可证 | MIT | AGPL-3.0 | Apache-2.0 | MIT | NOASSERTION | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Deploy any app (frontend, backend, workers, Postgres, Redis and object storage) with one command, from your terminal or from an AI agent.
npx rivtor login
npx rivtor deploy
Rivtor detects every service in the folder (Next.js, Vite, Astro, Express, Fastify, NestJS, FastAPI, Flask, Django, Go, Rust, Dockerfile and more), provisions the databases your code needs, wires service URLs together and returns live URLs, usually in about two minutes.
npm i -g rivtor # or run it with npx: npx rivtor <command>
You need Node.js 20 or newer.
Create a token at https://rivtor.com/dashboard/tokens, then run:
rivtor login # paste the token when asked (input is hidden)
rivtor login --token rvt_... # non-interactive
The token is saved to ~/.config/rivtor/config.json with mode 0600 (or $XDG_CONFIG_HOME/rivtor). In CI, set RIVTOR_TOKEN instead. RIVTOR_API_URL changes the API endpoint (default https://api.rivtor.com).
rivtor deploy # deploy the current folder
rivtor deploy ./my-app # deploy another folder rivtor deploy --dry-run # print the detected plan; nothing is deployed rivtor deploy --env-file .env.production # send these variables with the deploy rivtor deploy --no-wait # start and exit right away rivtor deploy --no-verify # skip post-deploy verification, not release security checks rivtor deploy --json # print the raw DeployResult (for scripts and agents) rivtor deploy --clean # rebuild everything from scratch, without build/dependency caches
Redeploys upload only the files that changed: the CLI sends a list of file hashes, and the API asks for the files it doesn't have yet. Dependencies are cached per account and reused until a lockfile, the runtime version or the build env changes. Use --clean if a cached dependency ever looks stale.
What gets uploaded:
.gitignore files (nested ones too) and an optional .rivtorignore.node_modules, .git, build outputs (dist, build, out, .next, ...), virtualenvs and caches are skipped..gitignore allows them. Only .env.example, .env.sample and .env.template are uploaded, so Rivtor can see which variable names your app expects. To send secret values, use --env-file or rivtor env set.The project name comes from --project , then from rivtor.json ({ "project": "my-app" }), then from the folder name. After the first deploy the CLI writes rivtor.json so later deploys go to the same project.
Exit codes: 0 live, 1 failed, 2 needs input (for example a missing secret). When a deploy fails, the CLI prints the cause, the file and line, and the fix.
When the API returns a verification report, deploy output ends with its actual verdict (working, partly_working, or broken), summary, check counts, cause/file/fix for each issue, and a private report link. Missing or skipped reports are explicitly labeled, never inferred as working from deployment success. Review skipped check groups before assuming coverage.
rivtor verify my-app # re-check the current live app without redeploying
rivtor verify my-app --json # complete machine-readable VerificationReport rivtor status my-app # last verdict, report link and open issue count rivtor issues my-app --status open --json rivtor issue-resolve --project my-app rivtor verify-fix --project my-app --yes
Manual verification applies no configuration fixes. It exits 0 only for working; other verdicts and request failures exit 1. Deploy keeps its existing deployment-status exit codes; automation should inspect verification.verdict separately in --json output. --no-wait stops waiting but leaves verification enabled.
Report pages and screenshots require sign-in and project membership. Sharing a report URL does not grant access. See https://rivtor.com/docs/verify.
| Command | What it does | |||
|---|---|---|---|---|
rivtor login [--token ] | Save an API token | |||
rivtor logout | Remove the saved token | |||
rivtor whoami | Show the logged-in account and plan | |||
rivtor deploy [path] [--project] [--dry-run] [--json] [--no-wait] [--env-file] [--clean] [--no-verify] | Deploy a folder | |||
rivtor verify [project] [--json] | Re-check the live app and return a verification report | |||
| `rivtor issues [project] [--status open\ | resolved\ | dismissed\ | all] [--severity]` | List production issues as JSON |
rivtor issue-resolve [--project] [--dismiss] | Resolve an issue or persist a false-positive dismissal | |||
rivtor verify-fix [--project] --yes | Consent to allowlisted configuration fixes and re-verification | |||
rivtor status [project] | Services, URLs, data services and the last deploy | |||
rivtor projects | List your projects | |||
rivtor logs [project] [--service] [--since 1h] [--level error] [--raw] [--build ] | Runtime logs, or a deployment's build log | |||
rivtor env set K=V [K2=V2 ...] [--service] | Set env vars and secrets (services restart; no rebuild) | |||
rivtor env rm K [K2 ...] [--service] | Remove env vars | |||
rivtor env ls | List env vars (values masked) | |||
rivtor env pull [--file ] [--production] [--include-secrets] [--force] | Write env vars to .env.local / .env (counts printed, never values) | |||
rivtor rollback [releaseId] | Roll back to the previous release, or to a specific one | |||
rivtor db query " " | Run read-only SQL | |||
rivtor db url | Get a temporary connection string (valid for 1 hour) | |||
rivtor db connect [--port 54329] | Authenticated tunnel to the project's Postgres on localhost | |||
rivtor db export -o backup.dump | Download a pg_dump in custom format | |||
rivtor domain add [--service] | Attach a custom domain and print the DNS record to create | |||
rivtor destroy [project] [--approval-token ] | Delete a project and all its data (API keys: after your approval) | |||
| `rivtor upgrade [hobby\ | pro\ | team] [--interval month\ | year]` | Open a checkout link |
rivtor mcp | Run the MCP server over stdio | |||
| `rivtor skills install [--target claude\ | codex\ | cursor\ | all] [--project]` | Install the Rivtor agent skill |
rivtor skills path | Print the folder of the bundled skill |
Most commands accept --json and --project .
rivtor mcp runs a local MCP server over stdio. It has the same tools as the remote server, and its deploy tool can upload a folder straight from disk:
deploy, status, logs, env_set, rollback, db, domain_add, destroy, upgrade, list_projects
With these tools an agent can fix its own failed deploys. When a deploy fails, the agent gets a structured error with cause, file and fix. It edits the code and calls deploy again, and only the services that changed are rebuilt. If a secret is missing, the agent asks you for it once, then calls env_set. Secret values are never echoed back.
claude mcp add rivtor -e RIVTOR_TOKEN=rvt_... -- npx -y rivtor mcp
If you already ran rivtor login, you can leave out -e RIVTOR_TOKEN=...:
claude mcp add rivtor -- npx -y rivtor mcp
~/.cursor/mcp.json (or .cursor/mcp.json in a project):
{
"mcpServers": { "rivtor": { "command": "npx", "args": ["-y", "rivtor", "mcp"], "env": { "RIVTOR_TOKEN": "rvt_..." } } } }
~/.codex/config.toml:
[mcp_servers.rivtor]
command = "npx" args = ["-y", "rivtor", "mcp"] env = { RIVTOR_TOKEN = "rvt_..." }
Agents that don't need to upload files from disk can connect to https://api.rivtor.com/mcp with the header Authorization: Bearer rvt_.... The remote deploy tool accepts a git URL, a starter template or inline files.
npx rivtor env pull # writes .env.local (Next.js / Vite) or .env; adds .env* to .gitignore
npx rivtor db connect # keep running: tunnel to the project's Postgres on localhost:54329 npm run dev # DATABASE_URL in the env file points at localhost:54329
env pull writes a local-safe set by default: DATABASE_URL is a temporary login (valid 1 hour; run env pull --force again for a new one) through the tunnel, never the database's own address. Redis runs on Rivtor's private network and is left out. Payment and provider secrets (names with SECRET, PRIVATE, TOKEN, PASSWORD, WEBHOOK, or ending in _KEY) are left out unless you pass --include-secrets; --production writes production values (database passwords left out unless --include-secrets). An existing file is never merged: env pull refuses to replace it without --force. db connect needs Node.js 22+.
Tokens have a scope: read (status, logs, read-only database), deploy (the default for new tokens: also deploy, env, rollback, domains) or admin (everything). They can be limited to one project and given an expiry. destroy with any API token also needs your approval: the first call prints an approval link; approve in the browser, then run rivtor destroy --approval-token .
The package ships an Agent Skill that teaches coding agents the Rivtor loop: deploy, read the DeployResult and verification verdict, fix from error.cause/error.fix, ask for missing secrets