Neuronto ARD Registry: Agentic Resource Discovery (ARD) Index

Neuronto ARD Registry: one search across every public ARD registry + 200,000+ verified MCP tools

使うべきか

品質と安全性

A
説明の品質
100%
スキーマの完全性
78%
命名の品質
95%
ポイズニングのリスク
100%
権限の一致
100%
プロトコルへの準拠
100%

ツール定義とプロトコルへの準拠に関する自動分析に基づいています。

コンテキストコスト

~983トークン数(ツール定義)
~1.5 KB一般的なレスポンスサイズ
注意への影響は中程度(128k コンテキストの 0.77%)

これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。

インストール

ワンクリックインストール

これを `claude_desktop_config.json` ファイルに追加してください:

{
  "mcpServers": {
    "agents-tools-search-discovery-ard-registry": {
      "url": "https://neuronto.com/mcp"
    }
  }
}

リモートエンドポイント

https://neuronto.com/mcpstreamable-http

できること

ツール一覧

ツール(4)

🟢 読み取り専用🟡 書き込み🔴 削除⚪ 不明
🟢find_resource(query, kind, limit, federate, payment, ...)

Search 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 relevance only and is not a trust or safety rating. Filter by payment (free, payable, x402, mpp) and a maximum price per call: terms come from the publisher's manifest or the endpoint's own 402 answer, and the caller pays the provider directly.

入力スキーマ

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "The task, in plain language. For example: 'scrape a website behind cloudflare'."
    },
    "kind": {
      "type": "string",
      "enum": [
        "any",
        "mcp-server",
        "skill",
        "a2a-agent",
        "agent",
        "webmcp",
        "plugin",
        "openapi",
        "graphql",
        "dataset",
        "package",
        "doc",
        "catalog",
        "registry"
      ],
      "description": "Restrict to one family of resource. Matching is normalised, so 'mcp-server' finds them under every media type in circulation, and 'a2a-agent' or 'agent' both reach A2A cards and ACP, OASF and AgentFacts descriptors. 'webmcp' is browser-page tools, which are not callable servers.",
      "default": "any"
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 50,
      "default": 8
    },
    "federate": {
      "type": "boolean",
      "default": true,
      "description": "Also query upstream registries live and fuse the rankings. Off is faster."
    },
    "payment": {
      "type": "string",
      "enum": [
        "any",
        "free",
        "payable",
        "x402",
        "mpp",
        "card"
      ],
      "default": "any",
      "description": "Keep only resources with this payment requirement. 'free' means none is known; 'payable' means a price or a 402 is known."
    },
    "max_price_per_call": {
      "type": "number",
      "minimum": 0,
      "description": "Most you will pay for one call, in US dollars. A resource whose price is unknown is excluded."
    },
    "network": {
      "type": "string",
      "description": "Payment network, for example base, solana, tempo or stripe."
    }
  },
  "required": [
    "query"
  ]
}
🟢find_tool(query, limit, with_schema)

Search 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 know the shape of the call you need; use find_resource when you are looking for a service.

入力スキーマ

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "What the tool should do. For example: 'extract text from a pdf'."
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 50,
      "default": 10
    },
    "with_schema": {
      "type": "boolean",
      "default": false,
      "description": "Include each tool's full JSON input schema. Verbose; off by default."
    }
  },
  "required": [
    "query"
  ]
}
🟡publish_resource(endpoint, domain)

List 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 handshake, and a domain must serve a manifest that parses. Nothing is taken on trust, so a listing that succeeds here is one an agent can actually call.

入力スキーマ

{
  "type": "object",
  "properties": {
    "endpoint": {
      "type": "string",
      "description": "Absolute URL of an MCP server, e.g. https://example.com/mcp"
    },
    "domain": {
      "type": "string",
      "description": "A domain serving /.well-known/ard.json, e.g. example.com"
    }
  }
}
🟢registry_stats

How large this index is, what it holds, how much of it has been verified by introspection, and which upstream registries are federated.

入力スキーマ

{
  "type": "object",
  "properties": {}
}

コミュニティ

このサーバーを評価する

エビデンス

最近の観測

検証済みバージョンは記録されていませんツール 4 件