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

unified-reading

https://unifiedreading.com

Registry code: 633f56b933c6f16c

api record

Unified Reading combines numerology, Western astrology and the Chinese zodiac into one reflective reading. Use calculate_birth_date_profile for date-only facts; send people to the website form for a personal reading and never collect their name, birth time or place here.

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

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

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

  • get_unified_reading_options open 1h ago

    List what Unified Reading offers (free sample, free preview, paid full reading), its price, and the pages a person should open. Collects no personal data.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "option": {
      "enum": [
        "all",
        "sample",
        "preview",
        "fullReading"
      ],
      "type": "string",
      "default": "all",
      "description": "Return only one option, or all of them."
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
  • get_chinese_zodiac_year unknown 1h ago

    Look up a Chinese zodiac year: its animal, stem element, yin-yang, and the Lunar New Year dates it starts and ends on. Use it to explain why a January or February birthday belongs to the previous animal. Needs no personal data.

    mcp-tool

    {
  "type": "object",
  "required": [
    "year"
  ],
  "properties": {
    "year": {
      "type": "integer",
      "maximum": 2044,
      "minimum": 1924,
      "description": "The zodiac year, the one that starts at that calendar year's Lunar New Year."
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • calculate_birth_date_profile unknown 1h ago

    Calculate the Life Path number, Western Sun sign and Chinese zodiac animal for a birth date, with links to the matching Unified Reading library guides. Only the date is needed; never send names, birth times or places. Nothing is stored. Moon, rising, houses and the full combined reading need the website form.

    mcp-tool

    {
  "type": "object",
  "required": [
    "date"
  ],
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Birth date as YYYY-MM-DD (1900 or later, not in the future)."
    }
  },
  "additionalProperties": false
}
    arguments 14 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 633f56b933c6f16c.

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