timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Agent Resource Discovery (ARD, IETF draft) registry: search every ARD registry + verified MCP tools
この種の作業を 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-02 |
ユーザーのいいね: 0 · 順位に最大 5 点(1 人 1 点)加算。お金では買えません。
品質: 基本チェック 4/4 項目に合格(表示のみ、並び順には不使用)
使っているAIアプリを選んで、設定をコピーしてください。
ひとことで AI にインストールしてもらう
Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index をインストールして。https://mcp.popnx.com/i/neuronto-agents-tools-search-discovery-ard-registry.md に従い、コマンドを見せて、私が OK するまで実行しないで。パソコンで作業できる AI(Claude Code や Cursor など)に貼り付けます。手順を読み、コマンドを見せて、あなたの OK を待ちます。キー不要・登録不要。 · AI が読む全文を見る
チェック 4/4 合格 · 質問内容は提供元のサーバー(neuronto.com)を通ります · ✓ コマンド確認済み 2026年11月13日
まず:どの AI を使っていますか?
使っているアプリを選ぶと、下に手順が表示されます。
Claude につなげます · 約 2 分
キー不要、インストール不要 · claude.ai かデスクトップアプリで一度設定すれば、チャットで使えます · 無料アカウントは 1 つまで · Team/Enterprise はオーナー(Owner)が追加
CustomizeConnectors
ここからコピーして Claude の同じ名前の欄に貼り付け、Continue を押します
Neuronto ARD Registry: Agentic Resource Discovery (ARD) Indexhttps://neuronto.com/mcpClaude が検出したサインイン設定の画面で Continue を押す · Authentication は作者の説明どおり(Sign in now・Sign in when needed・No sign in)を選び Add を押します
+ConnectorsNeuronto ARD Registry: Agentic Resource Discovery (ARD) Index
Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index を使って、私に何ができるか教えて、1 つやってみせて✓ Claude が Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index を使っていると言うか、回答に Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Anthropic のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
ChatGPT との接続はプランしだい
フル MCP:Web 版 ChatGPT の Business・Enterprise・Edu · Pro:読み取り/取得の権限で接続、データを変えるツールは使えないことがあります · Plus:公式ドキュメントで未確認。プラグイン画面にカスタム MCP を追加する項目があれば試せます · Web のみ
Plugins+Add custom MCP server
名前を入れ、Connection にアドレスを貼り付け、注意事項にチェックして Create as a plugin を押します
Neuronto ARD Registry: Agentic Resource Discovery (ARD) Indexhttps://neuronto.com/mcp新しいチャットを開き、入力前にプラグインの一覧から Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index を選びます
Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index を使って、私に何ができるか教えて、1 つやってみせて✓ ChatGPT が Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index を使っていると言うか、回答に Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に OpenAI のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
Claude Code につなげます · 約 2 分
キー不要、インストール不要
Mac:Command+スペースで Terminal と入力 · Windows:PowerShell を開く
claude mcp add --transport http --scope user agents-tools-search-discovery-ard-regist https://neuronto.com/mcpNeuronto ARD Registry: Agentic Resource Discovery (ARD) Index が一覧にあり、接続済みと表示されれば OK です
Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index を使って、私に何ができるか教えて、1 つやってみせて✓ Claude Code が Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index を使っていると言うか、回答に Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Anthropic のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
Cursor につなげます · 約 2 分
キー不要、インストール不要
Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index を使って、私に何ができるか教えて、1 つやってみせて✓ Cursor が Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index を使っていると言うか、回答に Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Cursor のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
VS Code につなげます · 約 2 分
キー不要、インストール不要
Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index を使って、私に何ができるか教えて、1 つやってみせて✓ VS Code が Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index を使っていると言うか、回答に Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に VS Code のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
Windsurf、Zed、Gemini CLI など MCP を使える他のアプリは追加方法がそれぞれ違います。アプリ一覧で確認してください
Web 経由でつなぐアプリ用のアドレス
https://neuronto.com/mcpJSON 設定は下の「開発者向け」にあります
Claude Code
claude mcp add --transport http --scope user agents-tools-search-discovery-ard-regist https://neuronto.com/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"agents-tools-search-discovery-ard-regist": {
"url": "https://neuronto.com/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"agents-tools-search-discovery-ard-regist": {
"type": "http",
"url": "https://neuronto.com/mcp"
}
}
}この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
このサーバーのつなぎ方と、各アプリの公式ドキュメントに基づきます。2026年11月10日に確認。
インターネット経由でつなげるアプリ
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
ツールの名前と説明は、サーバーが2026年11月19日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。
find_resourceSearch for an MCP server, skill, agent, API or other callable capability for a task, across this index and every other public ARD registry at once. Returns ranked matches with a relevance score, the endpoint to connect to, and which registries carry each result. The score is rele
find_toolSearch individual MCP tools by name and behaviour, not the servers that host them. Every tool returned here was read back from a live server's tools/list, so the name and input schema are what the server actually exposes rather than what its description claims. Use this when you
publish_resourceList an MCP server or an ARD-publishing domain in this index so other agents can discover it. Give `endpoint` for an MCP server URL, or `domain` for a site that serves an ARD manifest. The submission is verified before it is indexed: an endpoint must complete an MCP initialize ha
registry_statsHow large this index is, what it holds, how much of it has been verified by introspection, and which upstream registries are federated.
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月20日にチェック
レジストリ名はドメイン neuronto.com で確認済みです(レジストリがドメインの所有を確認しています)
コードの最終更新:一昨日
対象外:neuronto.com の所有者が自ら運営するクラウドのサーバーで、リポジトリのコードを実行しません
94ミリ秒で応答(HTTP 200)
サインイン不要
4件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした
クラウドのアドレスは直近 5 回中 5 回応答 · 最新 94 ms · 確認日 2026年11月19日
作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。
[](https://mcp.popnx.com/en/servers/neuronto-agents-tools-search-discovery-ard-registry)質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。
まだレビューはありません
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック4項目のうち4項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。
作者のクラウドで動きます。インストール不要でインターネット経由でつながりますが、送った内容は作者のサーバーを通ります。
GitHubリポジトリの最終更新は一昨日、最新バージョン(1.3.0)がレジストリに届いたのは18 日前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URL で接続するので、リモート MCP を受け付けるアプリでも使えます。例:Web 版 ChatGPT(Business 以上はフル MCP、Pro は読み取りのみ)。
同じカテゴリには:OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)
同じカテゴリでほかの作者のもの。コマンドは確認済み。公式を先に、次にスター順。
カードの見方:↓ 週あたりのダウンロードi★ GitHubスターi3つの柱:レビュー · チェック · 利用状況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
| これ Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index | OpenSEO | Exa | Microsoft Learn MCP | Docs | COTAL actions (cotal.ai) | |
|---|---|---|---|---|---|---|
| 動く場所 | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 |
| キーが必要 | いいえ | いいえ | いいえ | いいえ | いいえ | いいえ |
| Claude で + から追加 | いいえ | はい | はい | はい | いいえ | いいえ |
| 基本チェック | 4/4 | 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、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
One search across every public ARD registry, plus a verified index of what MCP servers actually expose.
neuronto.com · API · Submit your server · Benchmark · Dataset · Manifest
ARD is short for Agentic Resource Discovery, an open specification for how AI agents find the tools, skills, agents and APIs they need, published in June 2026 by a working group including Google, Microsoft, Hugging Face, AWS, Cisco, GitHub, Nvidia, Salesforce and Snowflake.
An *agentic resource* is anything an AI client can call to get work done: an MCP server, an A2A agent, a skill, an API, a workflow.
ARD answers one question, "what is available for this task?", and then gets out of the way. It is not a runtime and does not replace MCP or A2A. It tells an agent what exists; the agent connects using the resource's own protocol.
Since 30 October 2026 ARD is also three IETF Internet-Drafts in the DAWN effort (Discovery of Agents With Names), under the name Agent Resource Discovery. Same protocol, same /.well-known/ard.json, same urn:air identifiers. This registry follows both the specification (v0.91) and the drafts; see IETF drafts below.
Today an agent can only use capabilities someone installed for it in advance. Every tool has to be wired in by hand, and every tool description has to sit in the context window, competing for space with the actual work. That model does not survive contact with an ecosystem of thousands of tools, let alone millions.
ARD moves the selection problem out of the context window and into a search service, the same shift the early web made when it went from curated link directories to search engines.
For that to work, two sides have to exist. Publishers describe what they offer at a well-known location on their own domain. Registries index those descriptions and answer queries. Neuronto is both.
The specification defines three federation modes and makes auto the default: a registry queries its peers, merges their results, and returns one set.
In practice each public registry answers only from its own catalogue, so the same question asked in four places returns four different answers and the client has to pick a side. That is the problem Neuronto exists to remove.
Ask Neuronto once and the query fans out across every public ARD registry concurrently. Results are fused with reciprocal rank fusion, which combines the orderings rather than the scores, necessary because each registry calibrates differently, and importing another service's scoring would import its biases with it.
The response says which registries answered and which timed out, so a caller always knows how much of the federation is behind an answer.
Federated by default. federation: auto implemented as specified: concurrent fan-out under a hard time budget, fused ranking, per-upstream reporting. A slow peer costs the budget and nothing more.
Complete conformance. Passes the specification's official conformance tool as both a registry and a publisher with zero errors and zero warnings, including the optional GET /agents listing as a properly paginated object.
Type normalisation. Three media types for MCP servers are in circulation (application/mcp-server, application/mcp-server+json, application/mcp-server-card+json) and two URN prefixes appear as discovery identifiers (urn:air: and urn:ai:). Because filters match exactly, entries get dropped silently. Neuronto normalises both on ingest, so a filter for MCP servers returns them however the publisher spelled the type.
A verified tool index, not just a server index. Every other registry stores a server name and whatever prose its publisher wrote. Neuronto handshakes with each indexed MCP endpoint and reads its tools/list, so the index holds the real tool names and input schemas, the thing an agent actually has to match on. Currently 32,183 verified tools across 2,223 servers, plus 1,918 endpoints recorded as requiring credentials, which no other registry reports. Introspection is read only: a tool is never called.
Hybrid retrieval. Sparse BM25 and dense vectors, fused with the same reciprocal rank fusion used for federation, so one query runs lexical, semantic and federated retrieval and returns a single ordering. The dense leg rides inside the federation budget and contributes nothing if it is unavailable, so the lexical fast path is never slowed by it.
Verified liveness. Indexed endpoints are probed and non-responding ones demoted in ranking. Registries built on self-published manifests accumulate dead links quickly; serving them is the fastest way to become the index nobody trusts. Entries are demoted rather than deleted, because services come back.
Manifests generated from evidence, not from a form. Most domains will never author a manifest by hand. They already run an MCP server, or serve an OpenAPI document, or publish llms.txt, and the manifest is a restatement of things a crawler can already find. Neuronto probes a domain, emits an entry only for each resource that actually answered, records what proved it, and hosts the result. Nothing is inferred, because a generated manifest that guesses would put a claim on somebody's domain that they never made and cannot defend.
A private half of the index. The list of internal services an organisation's own agents may call usually lives in a system prompt, where nothing can search it and nobody can audit it. A domain that proves ownership by DNS can register those services, and one query then returns internal and public results together, each labelled with which it is. Private entries are held in separate storage from the public index rather than behind a flag, so no public search, count or page can reach them by construction.
Payment terms, before the call. A paid endpoint used to be found, called, and only then answer 402 Payment Required. Neuronto reads what a resource costs from two places and keeps them apart: what its manifest declares (the pay: terms of the specification's worked example, schema:offers, and catalogue formats that carry a price), and what the endpoint itself answers when it is called without payment (x402 terms in a PAYMENT-REQUIRED header or a 402 body, or an MPP challenge). A server that asks to be paid is recorded as reachable, not as broken. Results carry pay:protocol, pay:price, pay:currency and pay:network, with paymentEvidence saying whether a live 402 confirmed them, and a search can be filtered on them:
curl -sS -X POST https://neuronto.com/search -H 'content-type: application/json' \
-d '{"query":{"text":"crypto token prices","filter":{"pay:protocol":["x402"],"maxPricePerCall":0.01}},"federation":"none"}'
Paying for heavy calls. A self-hosted Neuronto charges nothing. On neuronto.com, the calls that do outbound work for the caller, a federated search, an audit or a manifest build, are free up to an allowance. Past it, the 429 carries an x402 price in a PAYMENT-REQUIRED header, and an agent that pays gets the call instead of a wait; a client that sends x-payment-protocol: x402 gets the 402 directly. Only a call that succeeded is settled. Submitting a resource, claiming a domain, being listed and position in results are never charged. GET https://neuronto.com/x402 states the live terms.
Terms never change a score, and the registry never handles a payment: the caller pays the provider directly.
Settling the payments, if you want that from us as well. Reading a price is one half of the problem; taking the money is the other. Neuronto also operates a hosted x402 facilitator at pay.neuronto.com, which any x402 server can point at in one line: it checks a buyer's signed stablecoin payment and settles it on-chain, and it never holds anyone's funds, because the buyer signs the transfer and the facilitator only broadcasts it. Live on Base, free while it is new. A live endpoint there charges a tenth of a cent and sends it straight back in the same request, so a client can be run end to end for nothing, and pay.neuronto.com/status publishes what it has been observed to do rather than a promise about it.
It is a separate hosted service: it is not part of this repository, nothing here depends on it, a self-hosted Neuronto never contacts it, and no resource is ever ranked differently for using it or for not using it.
Ranking that separates. A relevance score is only useful if the gap between the first and fifth result is legible. Scores are scaled to preserve real separation instead of compressing everything into a narrow band.
Search this index and the whole federation in one call:
curl -s https://neuronto.com/search \
-H 'content-type: application/json' \ -d '{"query":{"text":"scrape a website behind cloudflare"},"federation":"auto"}'
Or install it as an MCP server, so an agent searches from the interface it already speaks:
claude mcp add --transport http neuronto https://neuronto.com/mcp
| Endpoint | Purpose |
|---|---|
POST /search | Ranked results. federation: auto (default), referrals, none. Pages with pageSize, pageToken and nextPageToken. |
POST /explore | Facet counts over the index. |
GET /agents | Deterministic paginated listing, for browsing rather than ranking. |
POST /mcp | Search, tool search, index statistics and publishing, as MCP tools. GET and DELETE answer 405: there is no server-initiated stream, every tool answers inside the request that asked. |
POST /a2a | The same index over A2A. message/send returns a Message. Card at /.well-known/agent-card.json and /.well-known/agent.json. |
POST /tools, GET /tools?q= | Tool level search over verified tools rather than servers. |
POST /submit | Index an MCP endpoint or a manifest-publishing domain. 200 indexed, 202 kept and retried. A target verified in the last 24 hours is answered from its record ("deduplicated": true). |
GET /submit/status/{id} | Where a submission stands, with the last answer its endpoint gave. |
POST /audit | Publishing report: discovery, conformance, coverage, competition. |
POST /manifest/build | Generate a manifest for a domain from resources fetched there. |
GET /m/{host}.json | That generated manifest, hosted. |
GET /agents.md | What to call and how, for an agent that has already arrived. |
POST /claim, POST /claim/verify | Prove domain ownership by DNS TXT, receive a key. GET /claim describes the steps. |
POST /private/entries | Register internal services. Key required. |
GET /bench, GET /adoption | Retrieval measurement, and who publishes a manifest. |
GET /health | Liveness: the service and its database answer, and how old the last index refresh is (ingest_age_s, stale). Never counts anything; the counts it shows are the stored statistics, with asOf. |
| GET /stats, GET /metrics.json | The index statisti