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

nanami-products-mcp

https://chart.nanami-astro.com

Registry code: f3e352e3fae591f2

api record

Pre-computed astrology YAML via Swiss Ephemeris. Calculation is code, interpretation is AI.

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

endpoint
https://chart.nanami-astro.com/mcp
protocol
streamable-http ·2024-11-05
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 nanami-products-mcp live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is nanami-products-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does nanami-products-mcp have?
5 tools: get_chart_yaml_from_url, get_download_info_from_url, get_available_sections_from_url, get_chart_summary_from_url, get_astrology_prompt.
Is nanami-products-mcp 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.2%

90 days 99.5%· all time 99.5%

latency
345ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 397 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • get astrology chart yaml from a chart url
  • get astrology reading prompt
  • check chart sections and expiry
takes → gives
text → data, text
tools
5 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 5 tools
1 open 4 never probed 1 of 5 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.

  • get_astrology_prompt reads open 1h ago

    nanami-products側の西洋占星術鑑定ルール・出力構成・禁止事項を返します。今日の占い、ホロスコープ、ネイタルチャート、トランジット、小惑星を使う依頼では、Chart YAMLを解釈する前に必ずこのツールで鑑定プロンプトを取得してください。MCPは鑑定本文を生成せず、AIはこのプロンプトと get_chart_yaml_from_url のYAMLだけを根拠に解釈します。

    mcp-tool

    {
      "type": "object",
      "properties": {
        "purpose": {
          "enum": [
            "today_fortune",
            "monthly_flow",
            "natal_with_transit",
            "relationship",
            "work_activity",
            "long_term"
          ],
          "type": "string",
          "default": "today_fortune",
          "description": "MVPでは today_fortune / natal_with_transit に対応します。"
        },
        "product_type": {
          "type": "string",
          "default": "western_31days_transit_addon",
          "description": "Chart summary の product_type が分かる場合に渡してください。"
        }
      }
    }
    arguments 23 lines
  • get_chart_yaml_from_url reads unknown 1h ago

    Chart URLからAI解釈用YAMLを取得します。ネイタル、トランジット、小惑星、四柱推命、インド占星術などのセクションを必要に応じて取得できます。URLはアクセスキーとして扱われます。期限が近い場合は保存案内を返し、期限切れの場合はYAMLを返しません。今日の占い、ホロスコープ、ネイタルチャート、トランジット、小惑星を読む依頼では、先に get_chart_summary_from_url と get_astrology_prompt を呼び、取得した鑑定ルールに沿ってこのYAMLを解釈してください。

    mcp-tool

    {
      "type": "object",
      "required": [
        "chart_url"
      ],
      "properties": {
        "format": {
          "enum": [
            "full"
          ],
          "type": "string",
          "default": "full"
        },
        "sections": {
          "type": "array",
          "items": {
            "enum": [
              "natal",
              "transit_31days",
              "long_term",
              "asteroid",
              "shichu",
              "indian"
            ],
            "type": "string"
          },
          "description": "必要なセクション。未指定なら利用可能な全YAMLを返します。"
        },
        "chart_url": {
          "type": "string",
          "description": "https://chart.nanami-astro.com/chart/{chart_id}"
        }
      }
    }
    arguments 34 lines
  • get_download_info_from_url reads unknown 1h ago

    Chart URLのYAMLダウンロードURL、ファイル名、有効期限、保存推奨メッセージを返します。期限が近い場合は保存案内を返し、期限切れの場合はYAMLを返さず再購入導線を案内します。

    mcp-tool

    {
      "type": "object",
      "required": [
        "chart_url"
      ],
      "properties": {
        "chart_url": {
          "type": "string",
          "description": "https://chart.nanami-astro.com/chart/{chart_id}"
        }
      }
    }
    arguments 12 lines
  • get_available_sections_from_url reads unknown 15h ago

    Chart URLに含まれるネイタル、トランジット、小惑星、四柱推命などの利用可能セクション一覧を返します。URLはアクセスキーとして扱われます。

    mcp-tool

    {
      "type": "object",
      "required": [
        "chart_url"
      ],
      "properties": {
        "chart_url": {
          "type": "string",
          "description": "https://chart.nanami-astro.com/chart/{chart_id}"
        }
      }
    }
    arguments 12 lines
  • get_chart_summary_from_url reads unknown 15h ago

    Chart URLから商品種別、生成日時、有効期限、残り日数、含まれるセクション一覧を確認します。URLはアクセスキーとして扱われ、期限切れの場合は保存済みYAML利用または再購入案内を返します。今日の占い、ネイタル、トランジット、小惑星を読む前の最初の確認ツールとして使ってください。

    mcp-tool

    {
      "type": "object",
      "required": [
        "chart_url"
      ],
      "properties": {
        "chart_url": {
          "type": "string",
          "description": "https://chart.nanami-astro.com/chart/{chart_id}"
        }
      }
    }
    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 f3e352e3fae591f2.

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

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.