_ registry / mcp http-sse · checked 1h ago

Yutai

https://mcp.yutai.com

Registry code: 74dace97112f818a

api record

Yutai is the neutral loyalty network for tokenized equity. These tools read the public Yutai ledger with no credential. Search companies, read one company, read the facts of token instruments, search the developer docs, read the benefits behind instruments in one market, list the chains and tokenizer programmes, read one stock's public market activity, or read how each data domain stands today. Two prompts and four resources carry the docs and the interface description. Each address may make sixty calls a minute. Nothing here writes, and nothing here moves a token or a share. Read the…

endpoint
https://mcp.yutai.com/mcp
protocol
http-sse ·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 Yutai live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is Yutai free to use?
Yes — the hub reached it with no key and no payment.
What tools does Yutai have?
9 tools: get_market_activity, get_company, list_instruments, get_benefit_availability, get_status, search_docs, list_chains, list_tokenizers, ….
Is Yutai 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
100%

90 days 100%· all time 100%

latency
197ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
3 open 6 never probed 3 of 9 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.

  • list_chains open 1h ago

    Read the chains Yutai's ledger covers, each with its tokenizers, stocks, supply and holder figures and the newest health reading beside them.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • list_tokenizers open 1h ago

    Read the tokenizer programmes Yutai's ledger covers, each with its issuer, its reach, its supply and its holder figures.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • search_companies open 1h ago

    Search the public Yutai registry for companies, the share classes each one carries and the token instruments listed for a share class. Answers one page at a time, with the link to the next page when more companies follow.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "isin": {
      "type": "string",
      "pattern": "^[A-Z]{2}[A-Z0-9]{9}[0-9]$",
      "description": "Narrow the page to the company the ISIN belongs to: the share class's ISIN, such as US0000000009."
    },
    "chain": {
      "type": "string",
      "pattern": "^[-a-z0-9]{3,8}:[-_a-zA-Z0-9]{1,32}$",
      "description": "Narrow the page to the companies with an instrument on the chain: its CAIP-2 id, such as eip155:88880."
    },
    "limit": {
      "anyOf": [
        {
          "type": "number"
        },
        {
          "type": "string",
          "pattern": "^[0-9]{1,4}$"
        }
      ],
      "description": "The page's size: from 1 to 200 rows, 50 when left out."
    },
    "cursor": {
      "type": "string",
      "description": "The page link the previous answer carried: the nextCursor field's value of the page before this one."
    },
    "country": {
      "type": "string",
      "pattern": "^[A-Z]{2}$",
      "description": "Narrow the page to the companies of one country: its two-letter country code, such as US."
    }
  }
}
    arguments 37 lines
  • get_market_activity unknown never probed

    Read one stock's public on-chain activity: its holder count, each token's supply by chain and tokenizer, and its recent large movements. Give a chain or a tokenizer to narrow the tokens and the movements.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "stock"
  ],
  "properties": {
    "chain": {
      "enum": [
        "eip155:1",
        "eip155:10",
        "eip155:56",
        "eip155:196",
        "eip155:999",
        "eip155:4663",
        "eip155:5000",
        "eip155:8453",
        "eip155:42161",
        "eip155:57073",
        "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp",
        "eip155:143",
        "ton:-239",
        "tron:0x2b6653dc",
        "eip155:43114",
        "eip155:88888"
      ],
      "type": "string"
    },
    "stock": {
      "type": "string",
      "pattern": "^[a-z0-9][a-z0-9.-]{0,63}$"
    },
    "tokenizer": {
      "type": "string",
      "pattern": "^[a-z0-9][a-z0-9.-]{0,63}$"
    }
  }
}
    arguments 38 lines
  • get_company unknown never probed

    Read one company from the public Yutai registry by its legal name, with its share classes and token instruments. Give the two-letter country when two companies share a name.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 256,
      "minLength": 1
    },
    "country": {
      "type": "string",
      "pattern": "^[A-Z]{2}$"
    }
  }
}
    arguments 18 lines
  • list_instruments unknown never probed

    Read the facts of one or more token instruments by their instrument ids, including the programme behind each one, its legal form and any instrument the token converts into.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "instrumentIds"
  ],
  "properties": {
    "instrumentIds": {
      "type": "array",
      "items": {
        "type": "string",
        "pattern": "^[-a-z0-9]{3,8}:[-_a-zA-Z0-9]{1,32}\\/[-a-z0-9]{3,8}:[-.%a-zA-Z0-9]{1,128}$"
      },
      "maxItems": 100,
      "minItems": 1,
      "description": "The instruments to read the facts of: one or more, at most 100 in one read, each a CAIP-19 instrument id such as eip155:88880/erc20:0x0000000000000000000000000000000000000000."
    }
  }
}
    arguments 19 lines
  • get_benefit_availability unknown never probed

    Read the benefits the companies behind one or more token instruments offer in one market, each with what a holder must do to reach it, how it is delivered, and whether it is an illustrative example. Give one or more instrument ids and the two-letter country.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "instruments",
    "country"
  ],
  "properties": {
    "country": {
      "type": "string",
      "pattern": "^[A-Z]{2}$",
      "description": "The market whose stored policy shapes the answer: its two-letter country code, such as PT."
    },
    "instruments": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 200,
      "minItems": 1,
      "description": "The instruments to read: one or more, at most 200 in one read, each an ISIN such as US0000000009 or a CAIP-19 instrument id such as eip155:88880/erc20:0x0000000000000000000000000000000000000000."
    }
  }
}
    arguments 24 lines
  • get_status unknown never probed

    Read how each of Yutai's data domains stands today, each with the plain sentence for its mode, beside the answer's version, the build and its instant.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • search_docs unknown never probed

    Search the Yutai developer docs and read the matching pages as short snippets, each with the page's own address. Give a word or a phrase; the answer names up to the number of pages you ask for, five by default.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 5,
      "maximum": 10,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1
    }
  }
}
    arguments 20 lines
_ try it 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 74dace97112f818a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/74dace97112f818a/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/74dace97112f818a/badge.svg)](https://brick.blue/agent/74dace97112f818a?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 know
card completeness
100%

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
0
ok
0
failed
0
success rate
—
median latency
—
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
—

0 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.