timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Stale-proof repository memory with citations + just-in-time verification + TTL (repo-scoped).
教 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)排序,由以下部分组成
| 热度 | 4/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 3/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 7/100 |
质量: 基础检查通过 2/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
通过 2/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
Claude 暂时无法连接 Verified Repo Memory
还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器
ChatGPT 暂时无法连接 Verified Repo Memory
还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器
Claude Code 暂时无法连接 Verified Repo Memory
还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器
Cursor 暂时无法连接 Verified Repo Memory
还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器
VS Code 暂时无法连接 Verified Repo Memory
还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器
还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器
VRM_TTL_DAYS envVRM_DATA_DIR envVRM_MAX_FILE_BYTES envVRM_SECRET_SCAN 机密 必填 env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月18日
注册名称已通过 GitHub 账户 cognitivemyriad 验证,该账户拥有此仓库
代码最后更新于9个月前,已超过 6 个月
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
OSV.dev 中没有 @cognitivemyriad/vrm-local@0.1.2 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月16日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/cognitivemyriad-verified-repo-memory)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 2 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:VRM_SECRET_SCAN
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于9个月前,最新版本(0.1.2)于9个月前进入注册中心。
同一分类中有: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.
Connect AI agents to Exa 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
| 本项 Verified Repo Memory | OpenSEO | Exa | Microsoft Learn MCP | Docs | COTAL actions (cotal.ai) | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 是 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 是 | 是 | 是 | 否 | 否 |
| 基础检查 | 2/3 | 5/5 | 2/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | MIT | MIT | CC-BY-4.0 | NOASSERTION | Apache-2.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Stale-proof repository memory with citations + just-in-time verification + TTL (repo-scoped).
An MCP server providing "safe memory" for AI coding agents. Memories are scoped per repository, backed by code citations, and verified just-in-time so an agent never receives stale information when the underlying code has changed.
Run via npx:
npx -y @cognitivemyriad/vrm-local --repo /path/to/repo
*(Alternatively, run from source: npm ci && npm run build && node build/index.js --repo /path/to/repo)*
Store: Input:
{
"subject": "API version sync", "fact": "When changing API version, update client/server/docs together.", "citations": [{ "path": "src/api.ts", "startLine": 10, "endLine": 15 }] }
Output:
{
"stored": true, "memoryId": "uuid-...", "expiresAt": "2026-03-21T00:00:00Z" }
Retrieve: Input:
{ "query": "API version" }
Output:
{
"query": "API version", "valid": [ ... ], "stats": { "verified": 1, "validCount": 1 } }
graph TD
A[Agent] -->|Store Fact + Citation| B(Verified Repo Memory) B --> C{Save to Disk} C -->|Hash Code Snippet| D[(memories.json)]
A -->|Retrieve Fact| B B --> E{JIT Verification} E -->|Check File Hash| F{Unchanged or Relocated?} F -->|Yes| G[Return VALID Memory] F -->|No| H[Return STALE/MISSING]
vrm_retrieve, the server checks the physical file. If the snippet has moved, it relocates the citation. If it has been changed or deleted, the memory is marked STALE/MISSING and omitted from the results.Data is strictly repo-scoped and saved in: /.verified-repo-memory
This includes memories.json and a fingerprint/metadata file to prevent accidental cross-repo pollution. Add this directory to your .gitignore.
stdio local-only server without HTTP calls.../) out of the repository root, as well as accessing .git/ or .verified-repo-memory/.stderr.--no-secret-scan).To add this server to the Claude Desktop app, edit your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonAdd the following configuration:
{
"mcpServers": { "verified-repo-memory": { "command": "npx", "args": [ "-y", "@cognitivemyriad/vrm-local", "--repo", "/absolute/path/to/your/repo" ] } } }
To add this server to Claude Code using stdio transport:
claude mcp add mcp-verified-repo-memory --transport stdio -- npx -y @cognitivemyriad/vrm-local
*Note for Windows users:* You may need to prepend cmd /c to the command:
claude mcp add mcp-verified-repo-memory --transport stdio -- cmd /c npx -y @cognitivemyriad/vrm-local
This section explains how to publish the package to NPM and register it with the Anthropic MCP Registry so that it becomes publicly available.
NPM (Node Package Manager) is the package distribution platform. Publishing here allows anyone to install your tool with a single command.
1. Log in to NPM from the terminal:
npm login
A browser window will open. Sign in with your NPM account. When prompted, enter your 2FA code from your authenticator app.
2. Publish the package:
npm publish --access public
This command does the following:
npm run build).tgz archive of the compiled fileshttps://registry.npmjs.org/3. Verify the publication:
Visit https://www.npmjs.com/package/@cognitivemyriad/vrm-local in your browser. Your package page should appear.
Note: If you need to re-publish, you must increment the version number in
package.jsonandserver.jsonfirst (npm version patch). NPM does not allow overwriting existing versions.
The MCP Registry is Anthropic's official directory of MCP servers. Registering here allows Claude Desktop, Claude Code, and other MCP clients to discover and install your server.
Important: The NPM package must be published first (Step 1). The MCP Registry validates that the NPM package exists before accepting the registration.
mcp-publisher CLI tool# macOS (Homebrew)
brew install nicholasgriffintn/tap/mcp-publisher
npx @anthropic-ai/mcp-publisher
1. Log in to the MCP Registry via GitHub:
mcp-publisher login github
A browser window will open. Authorize the application with your GitHub account.
2. Publish to the MCP Registry:
mcp-publisher publish
This command reads server.json in the current directory and registers the server with the MCP Registry. The registry will:
server.json schema3. Verify the registration:
Visit https://registry.modelcontextprotocol.io and search for your server name.
Note: Once a version is published to the MCP Registry, it is immutable and cannot be changed. To publish updates, increment the version in both
package.jsonandserver.json, publish to NPM first, then runmcp-publisher publishagain.
When releasing a new version, always update the version number in all three locations:
# 1. Bump version in package.json
npm version patch # 0.1.2 → 0.1.3
npm publish --access public mcp-publisher publish
| File | Field | Must Match |
|---|---|---|
package.json | version | ✅ |
server.json | version (top-level) | ✅ |
server.json | packages[0].version | ✅ |