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

interslavic

https://interslavic.valksor.tools

Registry code: abd57ba6811db4a0

api record

Grounds you in real Interslavic (Medžuslovjansky) lexicography. Interslavic is a CONSTRUCTED pan-Slavic auxiliary language — designed to be understood across Slavic languages, NOT a natural or historically attested one; its grammar is regular, so inflection tables are algorithmically generated, not cited. Dictionary content is the community Interslavic dictionary bundled as a snapshot (offline; no live upstream). Primary flow: call interslavic_search(word) — any form and either script works (an inflected query resolves to its headword via the reverse form index; Latin and Cyrillic both work;…

endpoint
https://interslavic.valksor.tools/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 interslavic live?
Yes — it answered the hub's last check (checked 15h ago). It answered 100% of checks over the last 30 days.
Is interslavic free to use?
Yes — the hub reached it with no key and no payment.
What tools does interslavic have?
3 tools: interslavic_transliterate, interslavic_search, interslavic_get_inflections.
Is interslavic 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
191ms

last good check

priced tools
0

of 3 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

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 3 tools
3 never probed 0 of 3 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.

  • interslavic_transliterate unknown 15h ago

    Transliterate ONE Interslavic word between Latin and Cyrillic. This is bidirectional: it auto-detects the input's script and returns the attested spelling in the OTHER script — Latin input yields Cyrillic, Cyrillic input yields Latin (or pass `target` to force it). Unlike the lossy deromanize tools, this is an EXACT dataset lookup (both spellings are stored per entry): it never guesses — a word not in the dataset returns empty candidates.

    mcp-tool

    {
      "type": "object",
      "title": "interslavic_transliterateArguments",
      "required": [
        "text"
      ],
      "properties": {
        "text": {
          "type": "string",
          "title": "Text",
          "maxLength": 4000,
          "minLength": 1,
          "description": "ONE Interslavic word (not a phrase — the lookup does not tokenize). Auto-detects the script and returns the attested spelling in the OTHER script (Latin↔Cyrillic). A word absent from the dataset, or input with no clear script, returns empty candidates — this is an exact lookup and never guesses."
        },
        "target": {
          "anyOf": [
            {
              "enum": [
                "cyrillic",
                "latin"
              ],
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Target",
          "default": null,
          "description": "Force the output script (cyrillic|latin); omit to auto-detect."
        }
      }
    }
    arguments 33 lines
  • interslavic_search unknown 15h ago

    Look an Interslavic word up in the bundled community dictionary and return its translation matrix (English + 11 Slavic languages) plus its full, algorithmically-generated declension/conjugation table. Any form and either script works; an inflected query resolves to its headword and the result notes it. With search_language='eng' the query is an English word: the result lists its Interslavic equivalents plus their expanded entries. Returns Markdown plus the same result as structuredContent matching the declared outputSchema. Fully offline (bundled snapshot); calls are rate limited per client IP. Content: the Interslavic dictionary (van Steenbergen et al.); reuse licence unconfirmed — attribute the source.

    mcp-tool

    {
      "type": "object",
      "$defs": {
        "SearchLanguage": {
          "enum": [
            "isv",
            "eng"
          ],
          "type": "string",
          "title": "SearchLanguage",
          "description": "The query language. ``isv`` looks an Interslavic word up directly — any of its\ninflected forms resolves to the headword via the bundled reverse form index, and\na Latin or Cyrillic spelling both work. ``eng`` searches in reverse: the English\nquery is matched against the entries' English glosses and each matched Interslavic\nlemma is then looked up normally. The dictionary translates into 11 more Slavic\nlanguages, but only isv and eng are QUERYABLE in v1 — the other columns are\nread-only (returned in each entry's translation matrix)."
        }
      },
      "title": "interslavic_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. Interslavic (default): a SINGLE Interslavic word, any form and either script — an inflected form ('brata') resolves to its headword ('brat') via the reverse form index, Latin and Cyrillic both work for headwords, and diacritics are optional ('delati' finds 'dělati'). English (search_language='eng'): the English word whose Interslavic equivalents you want."
        },
        "max_forms": {
          "anyOf": [
            {
              "type": "integer",
              "maximum": 12,
              "minimum": 0
            },
            {
              "type": "null"
            }
          ],
          "title": "Max Forms",
          "default": null,
          "description": "Optional override for how many inflection tables to expand this call (0–12). Tables are served from the bundled dataset (no network), so this is cheap. Omit for the server default."
        },
        "include_forms": {
          "type": "boolean",
          "title": "Include Forms",
          "default": true,
          "description": "When true (default), each match's full declension/conjugation table is returned INLINE — usable cases/tenses in ONE call, no follow-up interslavic_get_inflections. Set false for a cheap screen of which entries exist. Bounded by a per-search cap — use max_forms to adjust per call. Pronouns, numerals and indeclinables carry no table. For eng queries this governs the expanded Interslavic entries."
        },
        "search_language": {
          "$ref": "#/$defs/SearchLanguage",
          "default": "isv",
          "description": "Language the query is in: 'isv' (default) looks the Interslavic word up directly; 'eng' finds the Interslavic equivalents of an English word (via the gloss index) and returns their full entries. These are the only two queryable languages in v1 — each entry ALSO carries a read-only translation matrix into 11 more languages (Russian, Polish, Czech, Ukrainian, …), but you cannot query IN those."
        }
      }
    }
    arguments 53 lines
  • interslavic_get_inflections unknown 15h ago

    Fetch the full declension (noun/adjective) or conjugation (verb) table for a word identified by a search result's inflection handle (entry_id + word_class). Use this only when a search ran without inline forms or left a match un-expanded — a default search already returns each match's table inline. Returns Markdown plus the table as structuredContent with the shape {"result": <paradigm>} — switch on result.category ('noun' | 'adjective' | 'verb' | 'not_found') before reading the body. Tables are generated by the official Interslavic morphology engine, not attested.

    mcp-tool

    {
      "type": "object",
      "title": "interslavic_get_inflectionsArguments",
      "required": [
        "entry_id",
        "word_class"
      ],
      "properties": {
        "entry_id": {
          "type": "string",
          "title": "Entry Id",
          "pattern": "^[0-9]{1,24}$",
          "description": "The dictionary word id from a search result's inflection handle (a number, e.g. '33555') — NOT the headword itself (Interslavic homographs share a spelling)."
        },
        "word_class": {
          "enum": [
            "adjective",
            "noun",
            "verb"
          ],
          "type": "string",
          "title": "Word Class",
          "description": "The paradigm class from a search result's inflection handle: 'noun', 'adjective' or 'verb'."
        }
      }
    }
    arguments 26 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 abd57ba6811db4a0.

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

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.tools 9 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.

1 more sit on this domain. All of them.