opencidian
https://opencidian-mcp.perxel.com
Registry code: de2b104cc25bfffd
OpenCidian: a Chinese-Vietnamese dictionary. Use it for a word's pinyin, Hán Việt or Vietnamese meaning instead of guessing. lookup takes hanzi, pinyin or Vietnamese; search_meaning finds Chinese words for a Vietnamese or English meaning; get_character for one character's readings and parts; words_with for words that contain a character; annotate_text for a whole sentence. Every field has `src`: say which source a value comes from when it matters. `vi: null` means the dictionary has no Vietnamese for that word, and no entries means the word isn't in it: say so rather than make one up. Hán…
- endpoint
- https://opencidian-mcp.perxel.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 opencidian live?
- Yes — it answered the hub's last check (checked 12h ago). It answered 100% of checks over the last 30 days.
- Is opencidian free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does opencidian have?
- 7 tools: annotate_text, lookup, get_character, words_with, search_meaning, suggest_correction, about.
- Is opencidian 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.
90 days 100%· all time 100%
last good check
of 7 tools
- unknown → live
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.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
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.
annotate_text unknown 12h ago
Splits Chinese text into words (longest match against the dictionary) and gives each its pinyin, Hán Việt per character, Vietnamese and English senses and entry `id`. `kind` is word, unknown (Chinese not in the dictionary: say so) or other (punctuation, Latin, digits). `otherReadings` > 0 means the word has more readings than the one shown: look it up when the reading matters. The split is by dictionary match, not grammar, and can be wrong (哪国人 comes out 哪 + 国人): check a split that changes the meaning.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "text" ], "properties": { "text": { "type": "string", "maxLength": 2000, "minLength": 1, "description": "Chinese text, up to 2000 characters: a sentence, a lesson's dialogue, a sign." } } }arguments 15 lineslookup unknown 12h ago
Dictionary entries for a Chinese word, a pinyin syllable or a Vietnamese word: simplified and traditional forms, pinyin, Hán Việt per character (Thiều Chửu), Vietnamese senses (CVDICT), English senses (CC-CEDICT), HSK level. Every field carries `src`, the source it came from. `kinds` says how the query was read and each entry's `match` which reading found it. `vi: null` means CVDICT has no Vietnamese for that word: say so, don't translate the English as if it were the dictionary's. No entries means the word isn't in the dictionary: say so, don't guess.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "q" ], "properties": { "q": { "type": "string", "maxLength": 100, "minLength": 1, "description": "Chinese characters (觉得, 覺得), pinyin with or without tones (jué de, jue2 de5, jue de) or Vietnamese (cảm thấy)." }, "by": { "enum": [ "hanzi", "pinyin", "vi" ], "type": "string", "description": "Force how q is read. Leave out to let the server tell hanzi, pinyin and Vietnamese apart." }, "limit": { "type": "integer", "maximum": 50, "minimum": 1, "description": "Entries to return, 1-50 (default 10)." } } }arguments 30 linesget_character unknown 12h ago
Everything known about one character: Hán Việt readings (Thiều Chửu first, Unihan when Thiều Chửu has none), pinyin readings, a short English gloss, stroke count, radical, its parts (decomposition) and how it was formed (etymology: the meaning part and the sound part, each with its Hán Việt), and its traditional or simplified forms. Every field carries `src`. For the words a character is in, use words_with; for a character used as a word, lookup.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "char" ], "properties": { "char": { "type": "string", "pattern": "^\\p{Script=Han}$", "description": "One Chinese character, simplified or traditional (觉 or 覺)." } } }arguments 14 lineswords_with unknown never probed
Words of two characters or more that contain a character (simplified or traditional), HSK words first, then shorter words. Each comes as a full entry: pinyin, Hán Việt, Vietnamese and English senses, HSK level, `src` per field.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "char" ], "properties": { "char": { "type": "string", "pattern": "^\\p{Script=Han}$", "description": "One Chinese character, simplified or traditional (觉 or 覺)." }, "limit": { "type": "integer", "maximum": 100, "minimum": 1, "description": "Words to return, 1-100 (default 20)." } } }arguments 20 linessearch_meaning unknown never probed
Vietnamese or English → Chinese: entries whose Vietnamese (CVDICT) or English (CC-CEDICT) senses match the meaning, HSK words first. These are candidates, not one translation: compare their senses and HSK levels before picking one, and say when several fit.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "meaning" ], "properties": { "lang": { "enum": [ "vi", "en" ], "type": "string", "description": "The language of `meaning`: vi (default) or en." }, "limit": { "type": "integer", "maximum": 50, "minimum": 1, "description": "Entries to return, 1-50 (default 10)." }, "meaning": { "type": "string", "maxLength": 100, "minLength": 1, "description": "A meaning to find Chinese words for, in Vietnamese (cảm thấy, with or without diacritics) or English (to feel)." } } }arguments 29 linessuggest_correction unknown never probed
Sends a correction for a wrong or missing value (Hán Việt, Vietnamese meaning, English, pinyin, a missing word) as a public GitHub issue in OpenCidian/opencidian-data; a maintainer reviews it, nothing changes in the data until then. Returns the issue number and link. Only use it when the user asks to report a mistake or agrees to, with evidence from a dictionary or textbook, never for a guess. The issue is public: put no personal details in it. A few per minute for all callers together.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "word", "field", "suggested", "evidence" ], "properties": { "word": { "type": "string", "maxLength": 40, "minLength": 1, "description": "The word or character the fix is for, in hanzi (说, 觉得)." }, "field": { "enum": [ "hanviet", "vi", "en", "pinyin", "missing", "other" ], "type": "string", "description": "What is wrong: hanviet (Hán Việt reading), vi (Vietnamese meaning), en (English), pinyin, missing (a word the dictionary lacks), other." }, "pinyin": { "type": "string", "maxLength": 60, "description": "The pinyin, only when the fix is for one reading of the word (觉 jiào, not jué)." }, "current": { "type": "string", "maxLength": 2000, "description": "The value OpenCidian gives now, copied from a lookup." }, "evidence": { "type": "string", "maxLength": 2000, "minLength": 1, "description": "Where the right value comes from: a dictionary (Thiều Chửu, hvdic.thivien.net, a textbook) with a page or link. Not your own guess." }, "suggested": { "type": "string", "maxLength": 2000, "minLength": 1, "description": "The value it should be." } } }arguments 52 linesabout unknown never probed
The dataset's version and build date, its licence (CC BY-SA 4.0), the full attribution to quote when reusing it, and every source with its pinned version and licence (CC-CEDICT, CVDICT, Thiều Chửu, Unihan, Make Me a Hanzi, the HSK lists). Use it to say where an answer comes from or how to cite OpenCidian.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }arguments 5 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idde2b104cc25bfffd.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/de2b104cc25bfffd/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/de2b104cc25bfffd?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.