Angel Numbers MCP Server by RoxyAPI

Analyze any number sequence - Angel number analysis API

get_angel_numbers_lookup

Read-only

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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lang`	No	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.	en
`number`	Yes	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`	No	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`	No	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).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`type`	Yes
`digits`	Yes
`number`	Yes
`digitRoot`	Yes
`contextNote`	No
`isRepeating`	Yes
`isPalindrome`	Yes
`knownMeaning`	Yes
`uniqueDigits`	Yes
`digitRootMeaning`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "contextNote": {
+      "type": "string"
+    },
+    "digitRoot": {
+      "type": "number"
+    },
+    "digitRootMeaning": {
+      "properties": {
+        "affirmation": {
+          "type": "string"
+        },
+        "coreMessage": {
+          "type": "string"
+        },
+        "keywords": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "meaning": {
+          "properties": {
+            "career": {
+              "type": "string"
+            },
+            "love": {
+              "type": "string"
+            },
+            "money": {
+              "type": "string"
+            },
+            "spiritual": {
+              "type": "string"
+            },
+            "twinFlame": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "spiritual",
+            "love",
+            "career",
+            "money",
+            "twinFlame"
+          ],
+          "type": "object"
+        },
+        "number": {
+          "type": "string"
+        },
+        "title": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "number",
+        "title",
+        "coreMessage",
+        "meaning",
+        "keywords",
+        "affirmation"
+      ],
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "digits": {
+      "type": "number"
+    },
+    "isPalindrome": {
+      "type": "boolean"
+    },
+    "isRepeating": {
+      "type": "boolean"
+    },
+    "knownMeaning": {
+      "properties": {
+        "actionSteps": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "affirmation": {
+          "type": "string"
+        },
+        "biblical": {
+          "type": "string"
+        },
+        "coreMessage": {
+          "type": "string"
+        },
+        "energy": {
+          "type": "string"
+        },
+        "keywords": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "meaning": {
+          "properties": {
+            "career": {
+              "type": "string"
+            },
+            "love": {
+              "type": "string"
+            },
+            "money": {
+              "type": "string"
+            },
+            "spiritual": {
+              "type": "string"
+            },
+            "twinFlame": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "spiritual",
+            "love",
+            "career",
+            "money",
+            "twinFlame"
+          ],
+          "type": "object"
+        },
+        "shadow": {
+          "type": "string"
+        },
+        "title": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "title",
+        "coreMessage",
+        "energy",
+        "keywords",
+        "meaning",
+        "biblical",
+        "shadow",
+        "affirmation",
+        "actionSteps"
+      ],
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "number": {
+      "type": "string"
+    },
+    "type": {
+      "type": "string"
+    },
+    "uniqueDigits": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "number",
+    "type",
+    "digitRoot",
+    "digits",
+    "uniqueDigits",
+    "isPalindrome",
+    "isRepeating",
+    "knownMeaning",
+    "digitRootMeaning"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedAug 25, 2026

changedInput schema / properties / lang / description

Previous value: -"Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English."New value: +"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."

changedInput schema / properties / lang / enum

Previous value: -[
-  "en",
-  "tr",
-  "de",
-  "es",
-  "hi",
-  "pt",
-  "fr",
-  "ru"
-]New value: +[
+  "en",
+  "tr",
+  "de",
+  "es",
+  "hi",
+  "pt",
+  "fr",
+  "ru",
+  "zh-Hans",
+  "zh-Hant"
+]

Changed2 schema fields changedAug 17, 2026

addedInput schema / examples

Added value: +[
+  {
+    "number": "1234"
+  }
+]

changedInput schema / properties / compact / description

Previous value: -"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."New value: +"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."

Changed1 schema field changedJul 22, 2026

changedInput schema / properties / compact / description

Previous value: -"Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false."New value: +"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."

Changed1 schema field changedJul 22, 2026

addedInput schema / properties / compact

Added value: +{
+  "default": false,
+  "description": "Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false.",
+  "type": "boolean"
+}

First observedJul 8, 2026

TDQS

A4.1/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already mark the operation readOnly and non-destructive, and the description adds useful behavioral context: it classifies pattern type, calculates digit root, checks the database, and provides a fallback interpretation. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core capability, followed by a concise pipeline summary and a targeted use case. It is dense but not padded; minor trimming of the opening 'Smart' would improve it slightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich schema, output schema, and readOnly annotations, the description is nearly complete for correct invocation. It omits explicit sibling routing, but the 'not just known angel numbers' clarification provides enough guidance for an agent to distinguish it from get_angel_numbers and related tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All four parameters are fully described in the schema with types, enums, examples, and defaults, so the description carries little additional parameter burden. It adds only the contextNote behavior, which the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: analyze any number sequence, not just known angel numbers. It clearly differentiates the tool from sibling lookups by emphasizing support for arbitrary user-entered sequences rather than only canonical angel numbers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear use case: synchronicity tracking apps where users encounter arbitrary number sequences. It does not explicitly name sibling tools or state when to prefer them, but the 'ANY number sequence' framing strongly implies when this tool is the right choice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Angel Numbers MCP Server by RoxyAPI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?