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

divineai

https://divineai-mcp.dharmikvibes.com

Registry code: cb1ce08d7f168de3

api record

DivineAI by DharmikVibes answers questions about the Hindu calendar and devotional practice. The panchang is computed for one named city; always say which city, time zone and date it is for, and ask for a city when the tool asks. Fasting and ritual guidance never replaces medical advice: anyone unwell, pregnant, diabetic or on medicine should check with a doctor before fasting. Festival dates come from DharmikVibes' verified calendar; a festival marked 'date to be confirmed' has no date yet, so do not supply one. Vrat practice and prayer texts appear only once a scholar has checked them.…

endpoint
https://divineai-mcp.dharmikvibes.com/divineai
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 divineai live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is divineai free to use?
Yes — the hub reached it with no key and no payment.
What tools does divineai have?
3 tools: get_panchang, get_vrat_guide, get_festival_dates.
Is divineai 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
477ms

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
2 open 1 never probed 2 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_vrat_guide open 1h ago

    Which vrats (fasts) fall on which dates: Ekadashi, Pradosh, Purnima, Amavasya, Karwa Chauth and others, with the deity, from DharmikVibes' verified festival calendar and DivineAI's vrat list. How a vrat is kept is included only once a scholar has checked that text.

    mcp-tool

    {
      "type": "object",
      "title": "get_vrat_guideArguments",
      "properties": {
        "vrat": {
          "anyOf": [
            {
              "type": "string",
              "maxLength": 60
            },
            {
              "type": "null"
            }
          ],
          "title": "Vrat",
          "default": null,
          "description": "Only this vrat, for example Ekadashi, Pradosh, Karwa Chauth, Purnima. Omit for all."
        },
        "to_date": {
          "anyOf": [
            {
              "type": "string",
              "maxLength": 40
            },
            {
              "type": "null"
            }
          ],
          "title": "To Date",
          "default": null,
          "description": "ISO end date. Omit for 60 days after the start."
        },
        "from_date": {
          "anyOf": [
            {
              "type": "string",
              "maxLength": 40
            },
            {
              "type": "null"
            }
          ],
          "title": "From Date",
          "default": null,
          "description": "ISO start date. Omit for today in India."
        },
        "include_weekly": {
          "type": "boolean",
          "title": "Include Weekly",
          "default": false,
          "description": "Also list the weekday vrats (Somvar, Mangalvar, ...)."
        }
      }
    }
    arguments 54 lines
  • get_festival_dates open 1h ago

    Hindu festivals, vrats and observances between two dates, soonest first, from DharmikVibes' verified festival calendar, including multi-day festivals such as Navratri with their end date. A date is given only when it has been checked against an independent official or temple source; festivals still being checked are listed separately with no date.

    mcp-tool

    {
      "type": "object",
      "title": "get_festival_datesArguments",
      "properties": {
        "days": {
          "anyOf": [
            {
              "type": "integer",
              "maximum": 400,
              "minimum": 1
            },
            {
              "type": "null"
            }
          ],
          "title": "Days",
          "default": null,
          "description": "Instead of to_date: how many days after the start, 1 to 400."
        },
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 12,
          "maximum": 30,
          "minimum": 1,
          "description": "Most festivals to return, 1 to 30."
        },
        "to_date": {
          "anyOf": [
            {
              "type": "string",
              "maxLength": 40
            },
            {
              "type": "null"
            }
          ],
          "title": "To Date",
          "default": null,
          "description": "ISO end date. Omit for 45 days after the start; at most 400 days."
        },
        "from_date": {
          "anyOf": [
            {
              "type": "string",
              "maxLength": 40
            },
            {
              "type": "null"
            }
          ],
          "title": "From Date",
          "default": null,
          "description": "ISO start date, for example 2026-10-01. Omit for today in India."
        }
      }
    }
    arguments 57 lines
  • get_panchang unknown 1h ago

    Panchang for one day in one city: sunrise, sunset, moonrise and moonset there, and the tithi (with paksha), nakshatra, yoga and karana prevailing at that sunrise, each with the time it ends, plus any festival on DharmikVibes' verified calendar that day. Always states the city, time zone and date used. If no city is given and no approximate location is available, it asks for one.

    mcp-tool

    {
      "type": "object",
      "title": "get_panchangArguments",
      "properties": {
        "city": {
          "anyOf": [
            {
              "enum": [
                "new-delhi",
                "varanasi",
                "ayodhya",
                "prayagraj",
                "mathura",
                "vrindavan",
                "haridwar",
                "rishikesh",
                "kedarnath",
                "badrinath",
                "ujjain",
                "dwarka",
                "somnath",
                "puri",
                "rameswaram",
                "tirupati",
                "madurai",
                "guwahati",
                "amritsar",
                "jammu",
                "mumbai",
                "kolkata",
                "chennai",
                "bengaluru",
                "hyderabad",
                "ahmedabad",
                "jaipur",
                "lucknow",
                "patna",
                "pune",
                "bhubaneswar",
                "kathmandu",
                "london",
                "leicester",
                "new-york",
                "new-jersey-edison",
                "chicago",
                "houston",
                "dallas",
                "san-francisco",
                "los-angeles",
                "toronto",
                "vancouver",
                "dubai",
                "singapore",
                "kuala-lumpur",
                "sydney",
                "melbourne",
                "auckland",
                "johannesburg",
                "durban",
                "port-louis",
                "suva",
                "port-of-spain"
              ],
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "City",
          "default": null,
          "description": "The city to compute for, from the fixed list. Omit to use the person's approximate location when the app provides it."
        },
        "date": {
          "anyOf": [
            {
              "type": "string",
              "maxLength": 40
            },
            {
              "type": "null"
            }
          ],
          "title": "Date",
          "default": null,
          "description": "ISO date, for example 2026-12-25. Omit for today in that city."
        }
      }
    }
    arguments 89 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 cb1ce08d7f168de3.

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

_ also on dharmikvibes.com 2 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.