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

shiritori-omikuji-dev

https://shiritori.omikuji.dev

Registry code: 6788e2b230ef67b9

api record

Japanese shiritori (しりとり) helper with a dictionary of about 90,000 common nouns. Use check_move to verify a move (does the next word start with the previous word's last kana, does it end in ん, was it used before, is it in the dictionary). Use suggest_next to pick your own reply (pass the words already used in exclude), and check_word to get a word's reading and last kana. Prefer words in hiragana/katakana when the reading of kanji is ambiguous.

endpoint
https://shiritori.omikuji.dev/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 shiritori-omikuji-dev live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is shiritori-omikuji-dev free to use?
Yes — the hub reached it with no key and no payment.
What tools does shiritori-omikuji-dev have?
3 tools: check_move, suggest_next, check_word.
Is shiritori-omikuji-dev 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
1,006ms

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.

  • check_move unknown never probed

    Check whether the next word correctly follows the previous word in shiritori: it must start with the previous word's last kana, it loses if it ends in ん or was already used. Also tells whether each word is in the dictionary and what the next word must start with.

    mcp-tool

    {
  "type": "object",
  "required": [
    "previous",
    "next"
  ],
  "properties": {
    "next": {
      "type": "string",
      "description": "The word just said."
    },
    "used": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 1000,
      "description": "Words already used in this game."
    },
    "previous": {
      "type": "string",
      "description": "The previous word (kana is safest; kanji is looked up in the dictionary)."
    },
    "loose_dakuten": {
      "type": "boolean",
      "default": false,
      "description": "House rule: allow ば→は/ぱ style dakuten variants."
    }
  },
  "additionalProperties": false
}
    arguments 31 lines
  • suggest_next unknown 1h ago

    Pick random words that can follow the previous word (or start with a given kana), excluding words already used and, by default, words ending in ん. pool "everyday" (default) uses hand-picked everyday words, "common" adds common dictionary words, "all" uses the whole dictionary.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "pool": {
      "enum": [
        "everyday",
        "common",
        "all"
      ],
      "type": "string",
      "default": "everyday"
    },
    "after": {
      "type": "string",
      "description": "The previous word."
    },
    "count": {
      "type": "integer",
      "default": 5,
      "maximum": 30,
      "minimum": 1
    },
    "genre": {
      "enum": [
        "food",
        "animal",
        "plant",
        "nature",
        "body",
        "goods",
        "vehicle",
        "place",
        "world",
        "people",
        "play",
        "word"
      ],
      "type": "string",
      "description": "Theme for 食べ物しりとり etc. (everyday words only)."
    },
    "allow_n": {
      "type": "boolean",
      "default": false,
      "description": "Include words ending in ん (they lose)."
    },
    "exclude": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 1000,
      "description": "Words already used in this game."
    },
    "start_char": {
      "type": "string",
      "description": "Or: one kana to start with, e.g. \"り\"."
    },
    "loose_dakuten": {
      "type": "boolean",
      "default": false
    }
  },
  "additionalProperties": false
}
    arguments 64 lines
  • check_word unknown 1h ago

    Look up a word: is it in the dictionary, its reading, its first and last kana under shiritori rules (ー and small kana handled), whether it ends in ん, and which kana the next word must start with.

    mcp-tool

    {
  "type": "object",
  "required": [
    "word"
  ],
  "properties": {
    "word": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 12 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 6788e2b230ef67b9.

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