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

morgenhimmel

https://morgenhimmel.de

Registry code: 619e18a58c318bff

api record

The daily horoscope for all twelve zodiac signs in German (Rosis Morgenhimmel, morgenhimmel.de), English, Spanish and Brazilian Portuguese (Sky and Signs, skyandsigns.com): argument lang = de, en, es or pt. The sky (Moon sign, sign changes, aspects) is computed; the reading is astrological tradition, not a forecast. Please cite "Rosis Morgenhimmel, morgenhimmel.de" or "Sky and Signs, skyandsigns.com". Das Horoskop auf Deutsch mit lang=de. Horoscopes are published seven days ahead (date = tomorrow works). Also calculated calendars: new and full moons with eclipses (get_moon_phases), the Hindu…

endpoint
https://morgenhimmel.de/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 morgenhimmel live?
Yes — it answered the hub's last check (checked 19h ago). It answered 100% of checks over the last 30 days.
Is morgenhimmel free to use?
Yes — the hub reached it with no key and no payment.
What tools does morgenhimmel have?
8 tools: get_horoscope, list_days, get_day, get_panchang, get_moon_phases, get_maya_day, get_islamic_dates, get_solar_terms.
Is morgenhimmel 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
135ms

last good check

priced tools
0

of 8 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

_ what it can do 8 tools
6 open 2 never probed 6 of 8 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_day open 20d ago

    A whole day: the Moon's sign, the sky, all twelve signs. Example: date='2026-11-02', lang='es'.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "date": {
      "type": "string",
      "description": "YYYY-MM-DD"
    },
    "lang": {
      "enum": [
        "de",
        "en",
        "es",
        "pt"
      ],
      "type": "string"
    }
  }
}
    arguments 18 lines
  • get_panchang open 19h ago

    Tithi, nakshatra, yoga, karana with start and end (IST, Lahiri), within a year. Example: date='2026-11-08'.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "date": {
      "type": "string",
      "description": "YYYY-MM-DD"
    }
  }
}
    arguments 9 lines
  • get_moon_phases open 19h ago

    New and full moons to 2030 (default: next 90 days) with sign, eclipse, name. Example: from='2027-01-01', to='2027-03-31'.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "to": {
      "type": "string",
      "description": "YYYY-MM-DD"
    },
    "from": {
      "type": "string",
      "description": "YYYY-MM-DD"
    },
    "lang": {
      "enum": [
        "de",
        "en",
        "es",
        "pt"
      ],
      "type": "string"
    }
  }
}
    arguments 22 lines
  • get_maya_day open 20d ago

    Cholq'ij day: number, nawal, Long Count (GMT 584283); meanings come from an ajq'ij. Example: date='1990-05-12'.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "date": {
      "type": "string",
      "description": "YYYY-MM-DD"
    }
  }
}
    arguments 9 lines
  • get_islamic_dates open 20d ago

    Expected Ramadan and Eid dates 2027-2028 by the main calendars; communities may differ by a day. Example: no arguments.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_solar_terms open 19h ago

    A year's 24 solar terms (2025-2031): UTC moment, hanzi, pinyin, names. Example: year=2027, lang='pt'.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "lang": {
      "enum": [
        "de",
        "en",
        "es",
        "pt"
      ],
      "type": "string"
    },
    "year": {
      "type": "integer"
    }
  }
}
    arguments 17 lines
  • get_horoscope unknown never probed

    A sign's daily horoscope: theme, reading, its sky, ratings -2..+2. Example: sign='Leo', lang='en'.

    mcp-tool

    {
  "type": "object",
  "required": [
    "sign"
  ],
  "properties": {
    "date": {
      "type": "string",
      "description": "YYYY-MM-DD"
    },
    "lang": {
      "enum": [
        "de",
        "en",
        "es",
        "pt"
      ],
      "type": "string"
    },
    "sign": {
      "type": "string",
      "description": "Leo, Escorpio, Leão …"
    }
  }
}
    arguments 25 lines
  • list_days unknown never probed

    Every day with a published horoscope, newest last. Example: lang='pt'.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "lang": {
      "enum": [
        "de",
        "en",
        "es",
        "pt"
      ],
      "type": "string"
    }
  }
}
    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 619e18a58c318bff.

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