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

scythian

https://scythian.valksor.com

Registry code: adb9b37c3c1f24d5

api record

Grounds you in real Scythian lexicography: the English Wiktionary's Proto-Scythian entries — the reconstructed Eastern Iranian steppe language of the Scythians, Sarmatians and Saka. The corpus is a few dozen reconstructed lemmas (asterisked, e.g. *tiɣri 'bitter'); treat every form as a scholarly reconstruction, not an attested spelling, and never invent words beyond it — that is also why this server offers no translation prompts. Primary flow: call scythian_search(word) — plain ASCII works (tigri finds *tiɣri; θ may be typed t or th), and by default each match returns its full descendants…

endpoint
https://scythian.valksor.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 scythian live?
Yes — it answered the hub's last check (checked 3m ago). It answered 99% of checks over the last 30 days.
Is scythian free to use?
Yes — the hub reached it with no key and no payment.
What tools does scythian have?
2 tools: scythian_search, scythian_get_descendants.
Is scythian 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
99.3%

90 days 99.3%· all time 99.3%

latency
206ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 434 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • look up a proto-scythian word
  • get descendants of a scythian lemma
takes → gives
text → data
tools
2 reads
_ 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

inferred, not observed

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

_ what it can do 2 tools
2 never probed 0 of 2 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.

  • scythian_search reads unknown 3m ago

    Look a Proto-Scythian lemma up on Wiktionary and return its senses plus its full descendants payload — the reconstructed etymology and the reflex tree down to Ossetian and Khotanese, attested scholarship, not invention. Plain ASCII spellings are folded to the reconstruction's diacritics and the result notes the resolution. With search_language='eng' the query is an English word instead: the result lists the lemmas whose glosses match it (the translations block) plus their expanded entries. Returns Markdown plus the same result as structuredContent matching the declared outputSchema. Results are cached server-side; first-time queries reach the live upstream politely and calls are rate limited — on a rate-limit error, wait a few seconds and retry. Content is from en.wiktionary.org (CC BY-SA 4.0 — attribute and share alike if republished).

    mcp-tool

    {
      "type": "object",
      "$defs": {
        "SearchLanguage": {
          "enum": [
            "xsc",
            "eng"
          ],
          "type": "string",
          "title": "SearchLanguage",
          "description": "The query language. ``xsc`` (ISO 639-3 Scythian; Wiktionary's entry code is\n``xsc-pro``) looks a Proto-Scythian lemma up directly — ASCII spellings are\nfolded (``tigri`` finds ``*tiɣri``) via the reverse index. ``eng`` searches in\nreverse: the English query is matched against the indexed glosses of all\nlemmas, and each match is then looked up normally."
        }
      },
      "title": "scythian_searchArguments",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "title": "Query",
          "maxLength": 80,
          "minLength": 1,
          "description": "The word to look up, in the language search_language names. Scythian (default): a SINGLE Proto-Scythian lemma — plain ASCII works ('tigri' finds *tiɣri: macrons and carons are folded, and ɣ→g, δ→d, β→b, ə→e, θ→t or th), with or without the reconstruction asterisk. English (search_language='eng'): the English word whose Proto-Scythian equivalents you want — matched against every entry's glosses."
        },
        "max_forms": {
          "anyOf": [
            {
              "type": "integer",
              "maximum": 12,
              "minimum": 0
            },
            {
              "type": "null"
            }
          ],
          "title": "Max Forms",
          "default": null,
          "description": "Optional override for how many descendants payloads to expand this call (0–12). On an uncached query each payload is one politely paced upstream fetch, so high values on cold queries are slow. Omit for the server default."
        },
        "include_forms": {
          "type": "boolean",
          "title": "Include Forms",
          "default": true,
          "description": "When true (default), each match's full descendants payload — etymology, glosses and the reflex tree down to Ossetian and Khotanese — is returned INLINE in ONE call, no follow-up scythian_get_descendants. Set false for a cheap screen of which entries exist. Bounded by a per-search cap — use max_forms to adjust per call. For eng queries this governs the expanded entries; the matched-lemmas list itself is always returned."
        },
        "search_language": {
          "$ref": "#/$defs/SearchLanguage",
          "default": "xsc",
          "description": "Language the query word is in: 'xsc' (default) looks the Proto-Scythian lemma up directly; 'eng' finds the lemmas whose English glosses match the query (the local gloss index — reconstructed languages have no translation tables) and returns their full entries. Glosses are in English either way."
        }
      }
    }
    arguments 53 lines
  • scythian_get_descendants reads unknown 3m ago

    Fetch the full descendants payload — etymology, glosses and the reflex tree (Sarmatian→Alanic→Ossetian, Saka→Khotanese) — for a lemma identified by a search result's descendant handle (entry_id + word_class). Use this only when a search ran without inline payloads or left a match un-expanded — a default search already returns each match's payload inline. Returns Markdown plus the payload as structuredContent with the shape {"result": <payload>} per the declared outputSchema — switch on result.category ('descendants' | 'not_found') before reading the body. Content from en.wiktionary.org (CC BY-SA 4.0).

    mcp-tool

    {
      "type": "object",
      "title": "scythian_get_descendantsArguments",
      "required": [
        "entry_id",
        "word_class"
      ],
      "properties": {
        "entry_id": {
          "type": "string",
          "title": "Entry Id",
          "pattern": "^\\*?[^\\W\\d_][\\w\\u0300-\\u036F'-]{0,79}$",
          "maxLength": 80,
          "minLength": 1,
          "description": "The bare lemma (no asterisk) from a search result's descendant handle, e.g. 'tiɣri', 'baga' — a typed leading asterisk is tolerated."
        },
        "word_class": {
          "enum": [
            "abbreviation",
            "acronym",
            "adjective",
            "adverb",
            "affix",
            "article",
            "character",
            "circumfix",
            "classifier",
            "combining form",
            "conjunction",
            "contraction",
            "counter",
            "determiner",
            "diacritical mark",
            "idiom",
            "infix",
            "initialism",
            "interfix",
            "interjection",
            "letter",
            "ligature",
            "noun",
            "number",
            "numeral",
            "participle",
            "particle",
            "phrase",
            "postposition",
            "prefix",
            "preposition",
            "prepositional phrase",
            "pronoun",
            "proper noun",
            "proverb",
            "punctuation mark",
            "romanization",
            "root",
            "suffix",
            "symbol",
            "verb"
          ],
          "type": "string",
          "title": "Word Class",
          "description": "The part-of-speech section from a search result's descendant handle, e.g. 'noun', 'adjective', 'proper noun'."
        }
      }
    }
    arguments 66 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 adb9b37c3c1f24d5.

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

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.

_ also on valksor.com 6 entries

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.