_ registry / mcp + a2a streamable-http · checked 5m ago

neuronto

https://neuronto.com

Registry code: 4058d311829d84cd

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://neuronto.com/mcp
door code
1ff45aee3f20e9ed
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is neuronto live?
Yes — it answered the hub's last check (checked 5m ago). It answered 97% of checks over the last 30 days.
Is neuronto free to use?
Yes — the hub reached it with no key and no payment.
What tools does neuronto have?
4 tools: find_resource, find_tool, publish_resource, registry_stats.
Is neuronto safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
97%

90 days 97.8%· all time 97.7%

latency
387ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 983 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
used for
  • search for mcp servers
  • search for mcp tools
  • publish mcp server
  • get registry statistics
takes → gives
text, data → data
tools
3 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • registry_stats reads open 21h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • find_resource reads unknown 21h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "kind": {
          "enum": [
            "any",
            "mcp-server",
            "skill",
            "a2a-agent",
            "agent",
            "webmcp",
            "plugin",
            "openapi",
            "graphql",
            "dataset",
            "package",
            "doc",
            "catalog",
            "registry"
          ],
          "type": "string",
          "default": "any",
          "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."
        },
        "limit": {
          "type": "integer",
          "default": 8,
          "maximum": 50,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "The task, in plain language. For example: 'scrape a website behind cloudflare'."
        },
        "network": {
          "type": "string",
          "description": "Payment network, for example base, solana, tempo or stripe."
        },
        "payment": {
          "enum": [
            "any",
            "free",
            "payable",
            "x402",
            "mpp",
            "card"
          ],
          "type": "string",
          "default": "any",
          "description": "Keep only resources with this payment requirement. 'free' means none is known; 'payable' means a price or a 402 is known."
        },
        "federate": {
          "type": "boolean",
          "default": true,
          "description": "Also query upstream registries live and fuse the rankings. Off is faster."
        },
        "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."
        }
      }
    }
    arguments 66 lines
  • find_tool reads unknown 21h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "What the tool should do. For example: 'extract text from a pdf'."
        },
        "with_schema": {
          "type": "boolean",
          "default": false,
          "description": "Include each tool's full JSON input schema. Verbose; off by default."
        }
      }
    }
    arguments 23 lines
  • publish_resource changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "domain": {
          "type": "string",
          "description": "A domain serving /.well-known/ard.json, e.g. example.com"
        },
        "endpoint": {
          "type": "string",
          "description": "Absolute URL of an MCP server, e.g. https://example.com/mcp"
        }
      }
    }
    arguments 13 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 4058d311829d84cd.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4058d311829d84cd/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/4058d311829d84cd/badge.svg)](https://brick.blue/agent/4058d311829d84cd?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
1
ok
1
failed
0
success rate
100%
median latency
376ms
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

1 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on neuronto.com 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.