_ registry / mcp streamable-http · checked 59m ago

nyan-parlor

https://www.tarotoper.com

Registry code: 556bb53008c55bf8

api record

Tools for tarot, I Ching, BaZi (Four Pillars) and the Chinese zodiac from Nyan Parlor (tarotoper.com). Always draw cards with draw_tarot_cards and cast hexagrams with cast_i_ching instead of inventing them, then look up meanings with get_tarot_card_meaning / get_hexagram. When reading, answer the user's question first, then explain how each card or line supports it. Include the page links the tools return so the user can read more. When the user writes in Japanese, pass language: "ja" so names, meanings and links come back in Japanese, and answer in Japanese.

endpoint
https://www.tarotoper.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 nyan-parlor live?
Yes — it answered the hub's last check (checked 59m ago). It answered 100% of checks over the last 30 days.
Is nyan-parlor free to use?
Yes — the hub reached it with no key and no payment.
What tools does nyan-parlor have?
6 tools: draw_tarot_cards, bazi_chart, cast_i_ching, chinese_zodiac, get_hexagram, get_tarot_card_meaning.
Is nyan-parlor 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
134ms

last good check

priced tools
0

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

  • draw_tarot_cards unknown never probed

    Draw tarot cards at random from a full 78-card Rider–Waite–Smith deck (cryptographically random, no repeats). Returns each card with its position, upright/reversed orientation, keywords and a link to its full meaning. Use this instead of inventing cards when a user asks for a tarot reading.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "count": {
          "type": "integer",
          "default": 3,
          "maximum": 10,
          "minimum": 1,
          "description": "How many cards to draw (1–10). 1 = single card / yes-no, 3 = past-present-future."
        },
        "language": {
          "enum": [
            "en",
            "ja"
          ],
          "type": "string",
          "default": "en",
          "description": "Output language. Use \"ja\" when the user writes in Japanese: Japanese card / hexagram names, meanings and links to the Japanese pages. Otherwise \"en\"."
        },
        "question": {
          "type": "string",
          "maxLength": 500,
          "description": "The question being asked (echoed back only; not stored)."
        },
        "positions": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 60
          },
          "maxItems": 10,
          "description": "Optional position names in order, e.g. [\"Past\", \"Present\", \"Future\"]."
        },
        "allow_reversed": {
          "type": "boolean",
          "default": true,
          "description": "Whether cards can come up reversed."
        }
      },
      "additionalProperties": false
    }
    arguments 42 lines
  • bazi_chart unknown never probed

    Calculate a BaZi / Four Pillars of Destiny chart from a birth date, optional birth time and the birthplace time zone. Uses solar-term boundaries (the year changes at the Start of Spring, Li Chun) via an astronomical calendar engine. Returns the four pillars with Ten Gods, the Day Master, five-element balance, luck pillars and the coming years.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "birth_date",
        "timezone"
      ],
      "properties": {
        "gender": {
          "enum": [
            "male",
            "female"
          ],
          "type": "string",
          "description": "Needed only for the direction of the luck pillars."
        },
        "language": {
          "enum": [
            "en",
            "ja"
          ],
          "type": "string",
          "default": "en",
          "description": "Output language. Use \"ja\" when the user writes in Japanese: Japanese card / hexagram names, meanings and links to the Japanese pages. Otherwise \"en\"."
        },
        "timezone": {
          "type": "string",
          "maxLength": 64,
          "minLength": 3,
          "description": "IANA time zone of the birthplace, e.g. \"America/New_York\" or \"Asia/Shanghai\"."
        },
        "birth_date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Gregorian birth date, YYYY-MM-DD (local date at the birthplace)."
        },
        "birth_time": {
          "type": "string",
          "pattern": "^\\d{2}:\\d{2}$",
          "description": "Local clock time HH:mm. Omit if unknown (gives a three-pillar chart)."
        }
      },
      "additionalProperties": false
    }
    arguments 44 lines
  • cast_i_ching unknown never probed

    Cast an I Ching reading with the traditional three-coin method (six tosses, bottom line first). Returns the primary hexagram, any changing lines and the relating (transformed) hexagram, with links to each hexagram's meaning. Use this instead of making up a hexagram.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "language": {
          "enum": [
            "en",
            "ja"
          ],
          "type": "string",
          "default": "en",
          "description": "Output language. Use \"ja\" when the user writes in Japanese: Japanese card / hexagram names, meanings and links to the Japanese pages. Otherwise \"en\"."
        },
        "question": {
          "type": "string",
          "maxLength": 500,
          "description": "The question being asked (echoed back only; not stored)."
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • chinese_zodiac unknown never probed

    Find a person's Chinese zodiac animal from a birth year or date (handles the Lunar New Year and Start of Spring boundaries for January–February births) and return the 2027 Year of the Fire Goat forecast for that sign: love, career, money and a tip.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "birth_date"
      ],
      "properties": {
        "language": {
          "enum": [
            "en",
            "ja"
          ],
          "type": "string",
          "default": "en",
          "description": "Output language. Use \"ja\" when the user writes in Japanese: Japanese card / hexagram names, meanings and links to the Japanese pages. Otherwise \"en\"."
        },
        "timezone": {
          "type": "string",
          "maxLength": 64,
          "minLength": 3,
          "description": "IANA time zone of the birthplace (e.g. \"America/New_York\"). Only matters for births near the Start of Spring in early February."
        },
        "birth_date": {
          "type": "string",
          "pattern": "^\\d{4}(-\\d{2}-\\d{2})?$",
          "description": "Birth year (YYYY) or full date (YYYY-MM-DD). A full date is needed to be exact for January–February births."
        }
      },
      "additionalProperties": false
    }
    arguments 30 lines
  • get_hexagram unknown 59m ago

    Look up one of the 64 I Ching hexagrams by number (1–64), English name ("The Wanderer"), Chinese character (旅), Japanese name (火山旅) or pinyin (ambiguous pinyin like "lu" returns the candidates). Returns its essence, judgment, image, love and career readings, guidance and the six line texts.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "hexagram"
      ],
      "properties": {
        "lines": {
          "type": "array",
          "items": {
            "type": "integer",
            "maximum": 6,
            "minimum": 1
          },
          "maxItems": 6,
          "description": "Changing line numbers to highlight (1 = bottom)."
        },
        "hexagram": {
          "type": "string",
          "maxLength": 40,
          "minLength": 1,
          "description": "Number 1–64, English name, Japanese name or pinyin."
        },
        "language": {
          "enum": [
            "en",
            "ja"
          ],
          "type": "string",
          "default": "en",
          "description": "Output language. Use \"ja\" when the user writes in Japanese: Japanese card / hexagram names, meanings and links to the Japanese pages. Otherwise \"en\"."
        }
      },
      "additionalProperties": false
    }
    arguments 35 lines
  • get_tarot_card_meaning unknown 59m ago

    Look up the meaning of a tarot card: keywords, upright and reversed meaning, love, feelings, career and money readings, and whether it leans yes or no. Accepts names like "The Tower", "3 of Cups", "Queen of Swords" or "ace of coins".

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "card"
      ],
      "properties": {
        "card": {
          "type": "string",
          "maxLength": 60,
          "minLength": 1,
          "description": "Card name, e.g. \"The Moon\", \"Five of Wands\", 「月」 or 「ワンドの5」."
        },
        "topic": {
          "enum": [
            "general",
            "love",
            "feelings",
            "career",
            "money",
            "all"
          ],
          "type": "string",
          "default": "all",
          "description": "Which aspect to return."
        },
        "language": {
          "enum": [
            "en",
            "ja"
          ],
          "type": "string",
          "default": "en",
          "description": "Output language. Use \"ja\" when the user writes in Japanese: Japanese card / hexagram names, meanings and links to the Japanese pages. Otherwise \"en\"."
        },
        "orientation": {
          "enum": [
            "upright",
            "reversed",
            "both"
          ],
          "type": "string",
          "default": "both"
        }
      },
      "additionalProperties": false
    }
    arguments 47 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 556bb53008c55bf8.

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

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.