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 分),不能用钱买。
质量: 基础检查通过 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 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 4/4 项检查 · 你的提问会经过开发者的服务器(neuronto.com) · ✓ 命令已检查 2026年11月20日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Neuronto ARD Registry: Agentic Resource Discovery (ARD) Indexhttps://neuronto.com/mcp在 Claude 检测到的登录设置页点击 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 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index,或回答中出现 Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
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 告诉我你能帮我做什么,然后做一件给我看✓ 如果 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/mcp应能看到 Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index 在列表中并显示已连接
用 Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index 告诉我你能帮我做什么,然后做一件给我看✓ 如果 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 告诉我你能帮我做什么,然后做一件给我看✓ 如果 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 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index,或回答中出现 Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
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天前进入注册中心。
支持 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.
Official Exa MCP 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
| 本项 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