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

insightbazi

https://www.insightbazi.com

Registry code: 135a70ff1a316bed

api record

BaZi (Four Pillars) calculation from birth date, time, and location via public remote MCP.

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

endpoint
https://www.insightbazi.com/api/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 insightbazi live?
Yes — it answered the hub's last check (checked 12h ago). It answered 100% of checks over the last 30 days.
Is insightbazi free to use?
Yes — the hub reached it with no key and no payment.
What tools does insightbazi have?
1 tool: calculate_bazi_chart.
Is insightbazi 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
532ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 2 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 1 tools
1 never probed 0 of 1 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.

  • calculate_bazi_chart unknown 12h ago

    Calculates a BaZi (Four Pillars of Destiny, 八字, 四柱推命, Saju) chart from a birth date, time and place with the InsightBaZi engine, and shows it as a chart card. Use it when the user asks for a BaZi chart, or for their Four Pillars, Day Master, Ten Gods, element balance or 10-year luck pillars to be worked out from a birth date. It applies true solar time from the birthplace longitude and historical daylight-saving rules, changes the Day Pillar at 23:00, the year at Lichun and months at solar terms. The chart card is the user-facing result. After a chart-only request, briefly confirm it is ready; do not duplicate its chart, tables or element breakdown. Interpret the structured result only if requested, or provide a text chart if explicitly requested.

    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 10-year luck pillars, whose direction depends on it."
        },
        "language": {
          "enum": [
            "en",
            "zh",
            "zh-hant",
            "ja",
            "ko",
            "th",
            "id",
            "es",
            "pt",
            "fr"
          ],
          "type": "string",
          "default": "en",
          "description": "Language for chart labels. Use the closest match to the user's language; use en when none matches."
        },
        "timezone": {
          "type": "string",
          "description": "IANA time zone of the birthplace, for example Asia/Bangkok or America/New_York."
        },
        "longitude": {
          "type": "number",
          "maximum": 180,
          "minimum": -180,
          "description": "Longitude of the birth city in decimal degrees, east positive, used only for the true-solar-time correction. Give the city's longitude when the birth city is known; never the user's current location."
        },
        "birth_date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Birth date in the Gregorian calendar, YYYY-MM-DD."
        },
        "birth_time": {
          "type": "string",
          "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
          "description": "Clock time on the birth record, 24-hour HH:MM, exactly as recorded (do not adjust for daylight saving). Omit when the user does not know it."
        },
        "birthplace": {
          "type": "string",
          "maxLength": 120,
          "description": "Birth city as the user gave it, shown on the card. This is the place of birth, never the user's current location."
        }
      }
    }
    arguments 60 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 135a70ff1a316bed.

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

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.