_ registry / mcp http-sse · checked 42m ago

unicodekit

https://unicodekit.com

Registry code: 2f45391fa5020537

api record

UnicodeKit looks up Unicode 18.0.0 characters. Use search_characters to find a character from a description, name, or codepoint, then get_character for its details and codes. Every answer links to its page on unicodekit.com.

endpoint
https://unicodekit.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 unicodekit live?
Yes — it answered the hub's last check (checked 42m ago). It answered 100% of checks over the last 30 days.
Is unicodekit free to use?
Yes — the hub reached it with no key and no payment.
What tools does unicodekit have?
5 tools: get_character, list_block_characters, search_characters, get_collection, list_blocks.
Is unicodekit 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
357ms

last good check

priced tools
0

of 5 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 5 tools
2 open 3 never probed 2 of 5 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.

  • get_collection open 42m ago

    Hand-picked sets of characters people use most. Collections: selected (Selected characters).

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "slug": {
          "type": "string",
          "default": "selected",
          "description": "The collection's slug"
        }
      }
    }
    arguments 11 lines
  • list_blocks open 42m ago

    Every Unicode block that has characters, in codepoint order, with its character count.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
  • get_character unknown 42m ago

    Everything about one character: what it is, its name, block, script, category, HTML, CSS, JavaScript, and UTF-8/UTF-16 codes, aliases, emoji and Han data, and related characters.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "character"
      ],
      "properties": {
        "character": {
          "type": "string",
          "minLength": 1,
          "description": "U+2192, 2192, or the character itself (→)"
        }
      }
    }
    arguments 14 lines
  • list_block_characters unknown never probed

    A Unicode block's characters in codepoint order, 200 at a time. Pass the returned cursor to get the next ones.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "block"
      ],
      "properties": {
        "block": {
          "type": "string",
          "minLength": 1,
          "description": "Block name, e.g. Box Drawing (see list_blocks)"
        },
        "cursor": {
          "type": "string",
          "description": "From the previous call, for the next characters"
        }
      }
    }
    arguments 18 lines
  • search_characters unknown never probed

    Find Unicode characters by name, alias, keyword, codepoint, the character itself, or meaning ("tick" finds ✓, "return key" finds ⏎). Best matches first.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "block": {
          "type": "string",
          "description": "Only this Unicode block, e.g. Arrows"
        },
        "emoji": {
          "type": "boolean",
          "description": "Only emoji (true) or only non-emoji (false)"
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "minLength": 1,
          "description": "What to look for: a name, a description, a codepoint like U+2192, or a character"
        },
        "script": {
          "type": "string",
          "description": "Only this script, by name or ISO code, e.g. Greek"
        },
        "category": {
          "type": "string",
          "description": "General_Category: S for symbols, Sm for math symbols, L for letters…"
        }
      }
    }
    arguments 36 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 2f45391fa5020537.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/2f45391fa5020537/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/2f45391fa5020537/badge.svg)](https://brick.blue/agent/2f45391fa5020537?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
90%

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.