_ registry / mcp streamable-http · checked 31m ago

roxy-angel-numbers

https://roxyapi.com

Registry code: c6ca5bd2973230bd

api record

Vedic kundli, panchang, dashas, nakshatras and KP charts for AI agents, one API key.

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

endpoint
https://roxyapi.com/mcp/angel-numbers
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 roxy-angel-numbers live?
Yes — it answered the hub's last check (checked 31m ago). It answered 99% of checks over the last 30 days.
Is roxy-angel-numbers free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does roxy-angel-numbers have?
4 tools: post_angel_numbers_daily, get_angel_numbers, get_angel_numbers_lookup, get_angel_numbers_number.
Is roxy-angel-numbers 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%

90 days 99%· all time 99%

latency
168ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 503 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • look up an angel number meaning
  • get the angel number of the day
  • list angel numbers
takes → gives
text → data
tools
4 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 4 tools
4 auth-required 4 of 4 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.

  • post_angel_numbers_daily reads auth-required never probed

    Get the angel number of the day with full meaning and interpretation. Returns a deterministic angel number based on the current date (or a provided seed date), ensuring all users see the same number for any given day. Includes complete spiritual, love, career, money, and twin flame interpretations plus a biblical perspective and a shadow reading. Perfect for daily guidance features, push notifications, content generation, and angel number widget integrations.

    mcp-tool

    {
      "type": "object",
      "examples": [
        {}
      ],
      "properties": {
        "date": {
          "type": "string",
          "format": "date",
          "example": "2026-03-06",
          "description": "Date for the reading in YYYY-MM-DD format. Defaults to today (UTC). Useful for viewing past daily readings or pre-generating future ones."
        },
        "lang": {
          "enum": [
            "en",
            "tr",
            "de",
            "es",
            "hi",
            "pt",
            "fr",
            "ru",
            "zh-Hans",
            "zh-Hant"
          ],
          "type": "string",
          "default": "en",
          "example": "en",
          "description": "Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English."
        },
        "seed": {
          "type": "string",
          "example": "user123",
          "description": "Optional seed for reproducible readings. Same seed + same date = same angel number every time. Pass any unique identifier (userId, email hash, session token) to give each user their own angel number for the day. Without a seed every caller receives the same shared angel number of the day."
        },
        "compact": {
          "type": "boolean",
          "default": false,
          "description": "Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {\"__cols\":[names],\"__rows\":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens."
        }
      }
    }
    arguments 42 lines
  • get_angel_numbers reads auth-required 14h ago

    Retrieve the angel number catalog with summary information. Returns 75+ angel numbers covering root digits (0-9), master numbers (11, 22, 33), double digits (44-99), triple repeating (111-999), quad repeating (1111-9999), the mirror families (X0X like 101-909, X1X, four-digit mirrors like 1212-2121), palindromes (1221, 1331), compound sequences (911, 1122), and sequential numbers (123, 1234). Supports optional type filtering. Perfect for building angel number explorer apps, reference guides, and spiritual databases.

    mcp-tool

    {
      "type": "object",
      "examples": [
        {}
      ],
      "properties": {
        "lang": {
          "enum": [
            "en",
            "tr",
            "de",
            "es",
            "hi",
            "pt",
            "fr",
            "ru",
            "zh-Hans",
            "zh-Hant"
          ],
          "type": "string",
          "default": "en",
          "example": "en",
          "description": "Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English."
        },
        "type": {
          "enum": [
            "repeating",
            "sequential",
            "mirror",
            "master",
            "root",
            "compound"
          ],
          "type": "string",
          "example": "repeating",
          "description": "Filter results by angel number pattern type. \"repeating\" returns numbers like 111, 444, 7777. \"sequential\" returns patterns like 1234. \"mirror\" returns palindrome or alternating patterns like 1212, 717. \"master\" returns 11, 22, 33. \"root\" returns single digits 0-9. \"compound\" returns mixed sequences with no pure pattern like 911, 1122."
        },
        "limit": {
          "type": "integer",
          "default": 20,
          "example": 20,
          "maximum": 50,
          "minimum": 1,
          "description": "Maximum items to return per page. Range: 1-50, default 20."
        },
        "offset": {
          "type": "integer",
          "default": 0,
          "example": 0,
          "minimum": 0,
          "description": "Number of items to skip for pagination. Default 0."
        },
        "compact": {
          "type": "boolean",
          "default": false,
          "description": "Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {\"__cols\":[names],\"__rows\":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens."
        }
      }
    }
    arguments 59 lines
  • get_angel_numbers_lookup reads auth-required 14h ago

    Smart angel number analysis that works for ANY number sequence, not just known angel numbers. Automatically classifies the pattern type (repeating, sequential, mirror, master, root, compound), calculates the numerology digit root, checks the database for a known meaning, and provides the foundational digit root interpretation (with full spiritual, love, career, money, and twin flame guidance) as a fallback. An optional context parameter adds a note tailored to where the number was seen. Perfect for synchronicity tracking apps where users enter arbitrary number sequences they encounter.

    mcp-tool

    {
      "type": "object",
      "examples": [
        {
          "number": "1234"
        }
      ],
      "required": [
        "number"
      ],
      "properties": {
        "lang": {
          "enum": [
            "en",
            "tr",
            "de",
            "es",
            "hi",
            "pt",
            "fr",
            "ru",
            "zh-Hans",
            "zh-Hant"
          ],
          "type": "string",
          "default": "en",
          "example": "en",
          "description": "Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English."
        },
        "number": {
          "type": "string",
          "example": "1234",
          "pattern": "^\\d{1,8}$",
          "description": "Number sequence to analyze (1-8 digits). Can be any number the user has encountered: clock times (1111), addresses (717), receipts (888), license plates (4444), or any repeating pattern."
        },
        "compact": {
          "type": "boolean",
          "default": false,
          "description": "Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {\"__cols\":[names],\"__rows\":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens."
        },
        "context": {
          "enum": [
            "clock",
            "receipt",
            "license-plate",
            "phone",
            "address",
            "price"
          ],
          "type": "string",
          "example": "clock",
          "description": "Where the number was seen. When supplied, the response adds a contextNote tailoring the reading to the sighting: clock (a glanced time), receipt (a purchase), license-plate (in transit), phone (a call or notification), address (a home or place), price (a total or amount)."
        }
      }
    }
    arguments 55 lines
  • get_angel_numbers_number reads auth-required 14h ago

    Get the full meaning and interpretation for a specific angel number. Returns detailed spiritual, love, career, money, and twin flame interpretations, plus a biblical perspective and a shadow reading, along with keywords, affirmation, and actionable steps. Covers 75+ angel numbers including 111, 222, 333, 444, 555, 666, 777, 888, 999, 1111, 1212, 1234, and more, across every major angel number pattern.

    mcp-tool

    {
      "type": "object",
      "examples": [
        {
          "number": "444"
        }
      ],
      "required": [
        "number"
      ],
      "properties": {
        "lang": {
          "enum": [
            "en",
            "tr",
            "de",
            "es",
            "hi",
            "pt",
            "fr",
            "ru",
            "zh-Hans",
            "zh-Hant"
          ],
          "type": "string",
          "default": "en",
          "example": "en",
          "description": "Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English."
        },
        "number": {
          "type": "string",
          "example": "444",
          "description": "Angel number sequence to look up (e.g., \"111\", \"444\", \"1212\", \"1234\"). Must match an entry in the database."
        },
        "compact": {
          "type": "boolean",
          "default": false,
          "description": "Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {\"__cols\":[names],\"__rows\":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens."
        }
      }
    }
    arguments 41 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 c6ca5bd2973230bd.

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

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.