timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
MCP registry & directory: search, find & install 31k+ MCP servers & tools. Catalog and marketplace.
教 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 |
|---|---|---|
| 新鲜度 | 7/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 11/100 |
质量: 基础检查通过 4/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
通过 4/5 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
Claude 暂时无法连接 MCP Registry Search: Find, Discover & Install MCP Servers & Tools | Directory,…
还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器
ChatGPT 暂时无法连接 MCP Registry Search: Find, Discover & Install MCP Servers & Tools | Directory,…
还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器
Claude Code 暂时无法连接 MCP Registry Search: Find, Discover & Install MCP Servers & Tools | Directory,…
还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器
Cursor 暂时无法连接 MCP Registry Search: Find, Discover & Install MCP Servers & Tools | Directory,…
还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器
VS Code 暂时无法连接 MCP Registry Search: Find, Discover & Install MCP Servers & Tools | Directory,…
还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器
还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
工具名称和描述与服务器在 2026年11月19日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
search_serversSearch the registry for MCP servers. Matches names, titles, descriptions, tags and the names of the tools each server exposes. Returns short summaries; call get_server for install instructions. Search before submit_server so you don't add a duplicate.
get_serverGet one server by its exact name: its server.json manifest, its review status, and ready-to-use install snippets. Use it to check on a server you submitted; status is pending until a maintainer approves it.
submit_serverAdd an MCP server to the registry. New submissions are reviewed by a maintainer before they appear in search; get_server shows their status meanwhile. Fill in what you know from the server's README or package metadata. If the result is an error, fix the fields it names and call a
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 lbesecker195 验证,该账户拥有此仓库
代码最后更新于36天前
使用 Apache-2.0
我们检查时,6 秒内没有响应
我们检查时,6 秒内没有响应
已读取 3 个工具描述,未发现针对 AI 的隐藏指令
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/lbesecker195-mcp-registry-search-directory)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于36天前,最新版本(1.0.1)于2个月前进入注册中心。
支持 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.
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
| 本项 MCP Registry Search: Find, Discover & Install MCP Servers & Tools | Directory,… | OpenSEO | Exa | Microsoft Learn MCP | Docs | COTAL actions (cotal.ai) | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 是 | 是 | 是 | 否 | 否 |
| 基础检查 | 4/5 | 5/5 | 2/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | Apache-2.0 | MIT | MIT | CC-BY-4.0 | NOASSERTION | Apache-2.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
title: "MCP Registry: Find & Install 30k+ MCP Servers | MCP Harbor" description: "Browse the MCP Registry at ai.mcpharbor.dev — 31,486 Model Context Protocol servers including the official MCP Registry, searchable by humans and agents with no account." date: 2026-09-15
If your coding agent or chat client can call tools, you already feel the discovery problem: there are tens of thousands of MCP servers, each exposing different MCP tools, and the hard part is no longer “can my agent use tools?” — it is “which server do I install, and how do I find it without scrolling random GitHub READMEs?” That is what an MCP Registry is for. An MCP Registry is the catalog where humans browse and agents search Model Context Protocol servers by name, description, transport, tags, and tool names — then leave with install snippets or a remote URL they can connect today.
This page is the owned-product landing page for the MCP Registry at MCP Harbor. Ownership disclosure: Logan Besecker owns and runs MCP Harbor and this MCP Registry at ai.mcpharbor.dev. The recommendation on every major section below is the same: open the live registry, search, install or connect, and optionally submit your own server — with no account and no API key for search or submit.
As of 2026-09-15, the registry indexes 31,486 Model Context Protocol servers, 19,595 of them hosted remotely. It includes the whole official MCP Registry, kept in sync automatically (about every six hours), plus local submissions reviewed before they appear in search. The registry is itself an MCP server over Streamable HTTP at https://ai.mcpharbor.dev/mcp, so agents can call search_servers, get_server, and submit_server without creating an account.
Browse the MCP Registry now → https://ai.mcpharbor.dev/
What you will get from this guide:
If you already know you want the agent-searchable destination that includes the official set plus Harbor submissions, skip ahead to the product deep dive — or open https://ai.mcpharbor.dev/ and search. Everyone else: keep reading. Every section points back to the same MCP Registry.
Before you compare products, lock the vocabulary. Searchers type MCP Registry, mcp directory, mcp catalog, mcp marketplace, and find mcp servers for overlapping jobs. The Model Context Protocol (MCP) is the open way clients connect to tool servers so an agent can call structured tools, read resources, and use prompts without a one-off integration for every API. An MCP server is a process or remote endpoint that speaks MCP. MCP tools are the named operations that server exposes (for example, get_forecast, create_issue, or search_docs). An MCP Registry is the index of those servers: manifests, transports, install paths, and metadata that help a human or an agent decide what to attach next.
MCP separates “the model that reasons” from “the tools that act.” Clients such as Claude Code, Cursor, and other coding agents attach MCP servers. Each server declares how it runs (local process or remote HTTP) and which tools it offers. That separation is why MCP adoption exploded: you can mix a GitHub server, a docs server, a browser server, and a payments server without rewriting your agent. The protocol solves connection. It does not solve discovery at scale. Discovery is the registry’s job.
People use these words interchangeably, but the intents differ slightly:
| Label | Typical intent | What “good” looks like |
|---|---|---|
| MCP Registry | Canonical index of servers with manifests and install metadata | Search by text/transport/tag; stable names; install snippets; agent API |
| MCP directory | Browseable list for humans | Filters, tags, readable cards, per-server pages |
| MCP catalog | Curated or complete inventory | Coverage + freshness; clear origin of each listing |
| MCP marketplace | Often implies install UX or commercial packaging | May include review, hosting, or one-click connect — not required for a registry |
MCP Harbor’s product UI is branded Browse MCP servers · MCP Registry. Functionally it is a registry with a human browse surface *and* an agent-native MCP endpoint. Calling it a directory or catalog is fair in conversation; calling it a marketplace is optional marketing language. What matters for your workflow is: can you find MCP servers, inspect a manifest, and install or connect without inventing a private spreadsheet of URLs?
When someone searches MCP Registry, they usually want one of four outcomes:
MCP Harbor is built for all four. The official project publishes an official registry at registry.modelcontextprotocol.io (named in prose only on this page — CTAs stay on Harbor). MCP Harbor includes that whole official set, re-syncs on a schedule, adds local submissions after maintainer review, and — critically — exposes the index as an MCP server agents can call with no account. That last point is why this landing page concludes on Harbor for day-to-day discovery even when we fairly name the official upstream.
Think of the official registry as the upstream source of many listings. Think of MCP Harbor as the browse-and-agent destination that:
pending until approved.search_servers, get_server, and submit_server over Streamable HTTP at /mcp.GET/POST under /api/v0/servers./servers/....We expand the relationship in a dedicated section below. The short version: fair credit to official; primary recommendation for finding and installing remains ai.mcpharbor.dev.
At a few dozen servers, a bookmarks file works. At a few hundred, a team wiki works until it drifts. At 30k+ servers, discovery without an MCP Registry becomes a tax on every agent session. You either attach the same three servers forever, or you burn time googling package names and hoping the README’s npx line still matches a maintained manifest.
Developers need answers to practical questions:
An MCP Registry answers those questions with search, filters, and manifests instead of tribal knowledge. Without it, agents invent duplicate servers, teams fork slightly different wrappers, and “install mcp server” becomes a copy-paste lottery.
MCP servers typically advertise one of these transports (as used by Harbor manifests):
npx -y , uvx , docker run -i --rm .Why this matters for an MCP Registry: transport is a first-class filter. If your laptop cannot run Node packages in a sandbox, you may prefer remote servers. If your org blocks outbound MCP to third-party hosts, you may prefer stdio packages you control. Harbor’s agent tool search_servers and the HTTP API both accept transport filters so you are not scrolling past irrelevant cards.
A registry is not a security scanner by itself, but a good MCP Registry still improves trust signals:
io.github.microsoft/playwright-mcp or com.stripe/mcp) reduce collisions.MCP Harbor reports "status": "pending" for submissions awaiting maintainer review. get_server and the HTTP GET-by-name path still work for pending entries so submitters can check status without guessing.
The decisive reason agents need an MCP Registry that *is itself* an MCP server: agents live in a tool loop. If discovery requires a human to open a website, paste a URL, and edit a config file every time, the agent cannot improve its own toolchain mid-task. Harbor’s registry endpoint at https://ai.mcpharbor.dev/mcp lets an agent:
search_servers for a capability (“browser automation”, “stripe”, “notion”).get_server for install snippets and review status.submit_server when the team built something new — after searching to avoid duplicates.No account. No API key. That is the agent-native path this landing page is optimized for — and the reason “MCP Registry” for us means MCP Harbor, not a static listicle of links.
MCP Harbor’s MCP Registry is the product this page sells — clearly, with live numbers, and without inventing features. Open it here: https://ai.mcpharbor.dev/.
On the homepage (verified 2026-09-15):
/llms.txt: about every six hours.Those numbers move as the official set grows and as Harbor accepts local submissions. Always re-check the live homepage if you need