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월 13일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.
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개월 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 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.
Search and read Empryo's documentation. Read-only, no auth, no local access.
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