_ registry / mcp streamable-http · checked 2h ago

kasahorow

https://nabanya.kasahorow.com

Registry code: 6da3f8e7fd8b2511

api record

Bilingual dictionary lookup and translation validation for kasahorow Fellows.

from a public catalogue that lists it, not from the operator

endpoint
https://nabanya.kasahorow.com/mcp
protocol
streamable-http ·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 kasahorow live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is kasahorow free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does kasahorow have?
2 tools: validate_translation, lookup_word.
Is kasahorow 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.4%

90 days 99.6%· all time 99.6%

latency
1,172ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 496 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • look up a word in a bilingual dictionary
  • validate a translation
takes → gives
text → 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

_ what it can do 2 tools
1 auth-required 1 never probed 1 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.

  • lookup_word reads auth-required 15h ago

    Look up a word in the kasahorow dictionary (WOAKA). fl = your language, tl = the language of the word. Returns definitions with parts of speech.

    mcp-tool

    {
      "type": "object",
      "required": [
        "word",
        "fl",
        "tl"
      ],
      "properties": {
        "fl": {
          "type": "string",
          "description": "Your language, ISO code (e.g. 'en')."
        },
        "tl": {
          "type": "string",
          "description": "The word's language, ISO code (e.g. 'ak', 'sw')."
        },
        "word": {
          "type": "string",
          "description": "The word or short phrase to look up."
        }
      }
    }
    arguments 22 lines
  • validate_translation reads unknown never probed

    Validate a translation with nabanya, the Connection Validator: it confirms your words transmit their feelings in the reader's language. It never rewrites your words. This is a PAID reading (N1 $15, N2 $10, N3 $5, N4 $3): the reply gives you the payment link and your report link. When the payment clears, the reading is prepared and sent to your report link and email.

    mcp-tool

    {
      "type": "object",
      "required": [
        "source",
        "writer",
        "reader"
      ],
      "properties": {
        "reader": {
          "type": "string",
          "description": "The reader's language, ISO code (e.g. 'sw')."
        },
        "source": {
          "type": "string",
          "description": "Your original writing. For N4, the single word instead."
        },
        "writer": {
          "type": "string",
          "description": "The writer's language, ISO code (e.g. 'en')."
        },
        "product": {
          "enum": [
            "N1",
            "N2",
            "N3",
            "N4"
          ],
          "type": "string",
          "description": "Which reading. N1 ($15) validates a finished pair and needs a translation. N4 ($3) validates ONE word: put the word in `source` and leave `translation` empty. Defaults to N1."
        },
        "translation": {
          "type": "string",
          "description": "The translation to validate. N1 only."
        }
      }
    }
    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 6da3f8e7fd8b2511.

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