A
licenseNot graded
qualityD
maintenanceTrust and reputation system for AI agents, enabling tracking, verifying, and building trust through scores, interactions, ratings, and reports.
MIT
Angel Numbers MCP Server by RoxyAPI
by com.roxyapi
Server Details
Angel number meanings and repeating sequences like 111, 222, 333 for AI agents.
Ownership verified
- Status
- Healthy
- Uptime
- 99.9% over 41 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
A4/5.0
Scored across 4 tools
Disambiguation4/5
Each tool has a clear primary purpose: list database, analyze arbitrary numbers, fetch detailed meaning for a specific number, and get daily number. There is minor overlap between lookup and specific-number meaning, since both return interpretations, but the descriptions clarify their distinct use cases.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with an optional suffix: get_angel_numbers, get_angel_numbers_lookup, get_angel_numbers_number, post_angel_numbers_daily. The only variation is post vs get, which is meaningful and predictable.
Tool Count5/5
Four tools is well-scoped for an angel number reference server. Each tool covers a distinct function—database retrieval, flexible analysis, detailed lookup, and daily generation—without unnecessary bloat or missing core functionality.
Completeness5/5
The server covers the full read-only domain: bulk access, specific queries, arbitrary sequence analysis, and a daily/date-based feature. There are no obvious gaps for the stated purpose of building angel number apps or reference guides.
Available Tools
4 toolsget_angel_numbersList all angel numbers - Angel number catalog APIARead-onlyInspect
Retrieve the complete database of angel numbers 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.
ParametersJSON 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 |
| type | No | 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 | No | Maximum items to return per page. Range: 1-50, default 20. | |
| offset | No | Number of items to skip for pagination. Default 0. | |
| 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. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| limit | Yes | |
| total | Yes | |
| offset | Yes | |
| numbers | Yes |
TDQS
A4.1/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond that: it returns a large catalog (75+ entries), enumerates the number families included, and states that type filtering is optional. It does not mention pagination or output shape, but those are defined in the schema and output schema.
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 primary purpose is front-loaded in the first sentence, and the long enumeration of catalog categories is informative for a catalog tool. The closing use-case sentence is slightly promotional but still earns its place by reinforcing usage context; overall it is structured and not inflated.
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 input schema, output schema, and annotations, the description provides enough selection and invocation context: it explains what the tool returns, which number families it covers, and that filtering is optional. It stops short of explicitly routing to siblings, which is a minor gap, but nothing needed for a correct call is missing.
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?
Schema description coverage is 100%, so all five parameters are already fully documented in the input schema. The description only echoes the presence of type filtering without adding format, default, or relationship details beyond the schema, so the baseline of 3 is appropriate.
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 opens with 'Retrieve the complete database of angel numbers', naming a specific verb and resource, and details the exact coverage (root, master, repeating, mirror, sequential, etc.). The title 'List all angel numbers' and phrase 'angel number catalog API' clearly distinguish it from the sibling lookup and daily tools.
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?
It gives clear context for when to use the tool: 'Perfect for building angel number explorer apps, reference guides, and spiritual databases', and notes the optional type filter as the primary usage control. However, it does not explicitly contrast with get_angel_numbers_number or get_angel_numbers_lookup, nor state when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_angel_numbers_lookupAnalyze any number sequence - Angel number analysis APIARead-onlyInspect
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.
ParametersJSON 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
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| type | Yes | |
| digits | Yes | |
| number | Yes | |
| digitRoot | Yes | |
| contextNote | No | |
| isRepeating | Yes | |
| isPalindrome | Yes | |
| knownMeaning | Yes | |
| uniqueDigits | Yes | |
| digitRootMeaning | Yes |
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.
get_angel_numbers_numberGet angel number meaning - Angel number lookup APIBRead-onlyInspect
Get the complete, authoritative 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. Authoritative interpretations covering all major angel number patterns.
ParametersJSON 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 | Angel number sequence to look up (e.g., "111", "444", "1212", "1234"). Must match an entry in the database. | |
| 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. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| type | Yes | |
| title | Yes | |
| energy | Yes | |
| number | Yes | |
| shadow | Yes | |
| meaning | Yes | |
| biblical | Yes | |
| keywords | Yes | |
| digitRoot | Yes | |
| actionSteps | Yes | |
| affirmation | Yes | |
| coreMessage | Yes |
TDQS
B3.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds useful behavioral context by listing the returned interpretation domains and the set of supported sequences (75+ numbers), which goes beyond the structured annotations without contradicting them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The first sentence delivers the core purpose, and the return-domain list is valuable. However, the phrase 'Authoritative interpretations covering all major angel number patterns' largely repeats earlier content, and the marketing-style phrasing adds length without new information.
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 a simple lookup tool with 100% parameter schema coverage, an output schema, and read-only annotations, the description provides rich coverage of what the tool returns and what numbers are supported. The main gap is alternative tool routing, but that is already scored under usage guidelines.
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?
Schema description coverage is 100%, so the parameters are already fully documented in the input schema. The description adds no additional meaning about the number, lang, or compact parameters beyond what the schema provides, which keeps this at the baseline 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the action (get meaning/interpretation) and resource (a specific angel number), and enumerates the interpretation categories. It does not explicitly distinguish itself from the sibling get_angel_numbers_lookup, so it falls short of full sibling differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance is given about when to use this tool versus get_angel_numbers, get_angel_numbers_lookup, or post_angel_numbers_daily. The phrase 'specific angel number' hints at lookup use, but the near-identical sibling get_angel_numbers_lookup is never addressed, so an agent gets no usable routing information.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
post_angel_numbers_dailyDaily angel number - Angel number of the day APIARead-onlyInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | 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 | 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 |
| seed | No | Optional seed for reproducible readings. Same seed + same date = same angel number every time. Pass any unique identifier (userId, email hash, session token). Omit for anonymous daily readings. | |
| 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. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| date | Yes | |
| seed | Yes | |
| type | Yes | |
| title | Yes | |
| energy | Yes | |
| number | Yes | |
| shadow | Yes | |
| meaning | Yes | |
| biblical | Yes | |
| keywords | Yes | |
| digitRoot | Yes | |
| actionSteps | Yes | |
| affirmation | Yes | |
| coreMessage | Yes |
TDQS
A3.7/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: the number is deterministic per date/seed, all users see the same number for a given day, and the response includes multiple interpretation domains. This goes beyond the annotations without contradicting them.
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 a single paragraph that front-loads the primary purpose and then adds deterministic behavior, content coverage, and use cases. It is efficient and each sentence adds useful information, though the closing use-case list is somewhat promotional and could be trimmed without losing essential guidance.
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 output schema exists and all four parameters are optional with full schema descriptions, the description is sufficiently complete for an agent to call the tool correctly. It covers determinism, language fallback context is in the schema, and the response contents are summarized. No critical behavioral gaps like output format or side effects remain unexplained.
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?
Schema description coverage is 100%, so the parameter semantics are already fully documented in the input schema. The description reinforces the seed behavior ('deterministic angel number based on the current date or a provided seed date') but does not add meaning beyond the schema's parameter descriptions. Baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'Get the angel number of the day with full meaning and interpretation.' It clearly describes the tool's core function and its deterministic date-based behavior. However, it does not explicitly name or contrast sibling tools, so differentiation from get_angel_numbers_lookup or get_angel_numbers_number is only implied by the 'daily' framing.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description includes use cases ('Perfect for daily guidance features, push notifications, content generation, and angel number widget integrations'), which imply when an agent might choose this tool. It provides no explicit when-to-use versus alternatives guidance, no exclusions, and no mention of the sibling tools that might be more appropriate for other lookup types.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
get_angel_numbers2 fields changed- added
Input schema / properties / offset / defaultAdded value: +0 - added
Input schema / properties / offset / minimumAdded value: +0
1 tool update
- Changed
get_angel_numbers3 fields changed- removed
Input schema / properties / offset / defaultRemoved value: -0 - removed
Input schema / properties / offset / minimumRemoved value: -0 - changed
Input schema / properties / offset / typePrevious value: -[ - "integer", - "null" -]New value: +"integer"
4 tool updates
- Changed
get_angel_numbers1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "properties": { + "limit": { + "type": "number" + }, + "numbers": { + "items": { + "properties": { + "coreMessage": { + "type": "string" + }, + "digitRoot": { + "type": "number" + }, + "energy": { + "type": "string" + }, + "keywords": { + "items": { + "type": "string" + }, + "type": "array" + }, + "number": { + "type": "string" + }, + "title": { + "type": "string" + }, + "type": { + "type": "string" + } + }, + "required": [ + "number", + "title", + "coreMessage", + "type", + "digitRoot", + "keywords", + "energy" + ], + "type": "object" + }, + "type": "array" + }, + "offset": { + "type": "number" + }, + "total": { + "type": "number" + } + }, + "required": [ + "total", + "limit", + "offset", + "numbers" + ], + "type": "object" +}
- Changed
get_angel_numbers_lookup1 field changed- changed
Output 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" +}
- Changed
get_angel_numbers_number1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "properties": { + "actionSteps": { + "items": { + "type": "string" + }, + "type": "array" + }, + "affirmation": { + "type": "string" + }, + "biblical": { + "type": "string" + }, + "coreMessage": { + "type": "string" + }, + "digitRoot": { + "type": "number" + }, + "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" + }, + "number": { + "type": "string" + }, + "shadow": { + "type": "string" + }, + "title": { + "type": "string" + }, + "type": { + "type": "string" + } + }, + "required": [ + "number", + "title", + "coreMessage", + "type", + "digitRoot", + "keywords", + "energy", + "meaning", + "biblical", + "shadow", + "affirmation", + "actionSteps" + ], + "type": "object" +}
- Changed
post_angel_numbers_daily1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "properties": { + "actionSteps": { + "items": { + "type": "string" + }, + "type": "array" + }, + "affirmation": { + "type": "string" + }, + "biblical": { + "type": "string" + }, + "coreMessage": { + "type": "string" + }, + "date": { + "type": "string" + }, + "digitRoot": { + "type": "number" + }, + "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" + }, + "number": { + "type": "string" + }, + "seed": { + "type": "string" + }, + "shadow": { + "type": "string" + }, + "title": { + "type": "string" + }, + "type": { + "type": "string" + } + }, + "required": [ + "date", + "seed", + "number", + "title", + "coreMessage", + "type", + "digitRoot", + "energy", + "meaning", + "biblical", + "shadow", + "keywords", + "affirmation", + "actionSteps" + ], + "type": "object" +}
4 tool updates
- Changed
get_angel_numbers2 fields changed- changed
Input schema / properties / lang / descriptionPrevious 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." - changed
Input schema / properties / lang / enumPrevious value: -[ - "en", - "tr", - "de", - "es", - "hi", - "pt", - "fr", - "ru" -]New value: +[ + "en", + "tr", + "de", + "es", + "hi", + "pt", + "fr", + "ru", + "zh-Hans", + "zh-Hant" +]
- Changed
get_angel_numbers_lookup2 fields changed- changed
Input schema / properties / lang / descriptionPrevious 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." - changed
Input schema / properties / lang / enumPrevious value: -[ - "en", - "tr", - "de", - "es", - "hi", - "pt", - "fr", - "ru" -]New value: +[ + "en", + "tr", + "de", + "es", + "hi", + "pt", + "fr", + "ru", + "zh-Hans", + "zh-Hant" +]
- Changed
get_angel_numbers_number2 fields changed- changed
Input schema / properties / lang / descriptionPrevious 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." - changed
Input schema / properties / lang / enumPrevious value: -[ - "en", - "tr", - "de", - "es", - "hi", - "pt", - "fr", - "ru" -]New value: +[ + "en", + "tr", + "de", + "es", + "hi", + "pt", + "fr", + "ru", + "zh-Hans", + "zh-Hant" +]
- Changed
post_angel_numbers_daily2 fields changed- changed
Input schema / properties / lang / descriptionPrevious 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." - changed
Input schema / properties / lang / enumPrevious value: -[ - "en", - "tr", - "de", - "es", - "hi", - "pt", - "fr", - "ru" -]New value: +[ + "en", + "tr", + "de", + "es", + "hi", + "pt", + "fr", + "ru", + "zh-Hans", + "zh-Hant" +]
4 tool updates
- Changed
get_angel_numbers2 fields changed- added
Input schema / examplesAdded value: +[ + {} +] - changed
Input schema / properties / compact / descriptionPrevious 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."
- Changed
get_angel_numbers_lookup2 fields changed- added
Input schema / examplesAdded value: +[ + { + "number": "1234" + } +] - changed
Input schema / properties / compact / descriptionPrevious 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."
- Changed
get_angel_numbers_number2 fields changed- added
Input schema / examplesAdded value: +[ + { + "number": "444" + } +] - changed
Input schema / properties / compact / descriptionPrevious 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."
- Changed
post_angel_numbers_daily2 fields changed- added
Input schema / examplesAdded value: +[ + {} +] - changed
Input schema / properties / compact / descriptionPrevious 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."
1 tool update
- Changed
get_angel_numbers1 field changed- changed
Input schema / properties / offset / typePrevious value: -"integer"New value: +[ + "integer", + "null" +]
4 tool updates
- Changed
get_angel_numbers1 field changed- changed
Input schema / properties / compact / descriptionPrevious 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."
- Changed
get_angel_numbers_lookup1 field changed- changed
Input schema / properties / compact / descriptionPrevious 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."
- Changed
get_angel_numbers_number1 field changed- changed
Input schema / properties / compact / descriptionPrevious 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."
- Changed
post_angel_numbers_daily1 field changed- changed
Input schema / properties / compact / descriptionPrevious 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."
4 tool updates
- Changed
get_angel_numbers1 field changed- added
Input schema / properties / compactAdded 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" +}
- Changed
get_angel_numbers_lookup1 field changed- added
Input schema / properties / compactAdded 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" +}
- Changed
get_angel_numbers_number1 field changed- added
Input schema / properties / compactAdded 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" +}
- Changed
post_angel_numbers_daily1 field changed- added
Input schema / properties / compactAdded 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" +}
4 tool updates
- Added
get_angel_numbers - Added
get_angel_numbers_number - Removed
get_angel_numbers_numbers - Removed
get_angel_numbers_numbers_number
4 tool updates
- First observed
get_angel_numbers_lookup - First observed
get_angel_numbers_numbers - First observed
get_angel_numbers_numbers_number - First observed
post_angel_numbers_daily
Related MCP Connectors
Life Path, Expression, karmic debt and Chaldean numerology readings for AI agents.
Wellness, spiritual-growth and angel-number articles in 24 languages, plus agent-wellbeing guides.
Kua numbers, Eight Mansions, Flying Star charts and annual afflictions for AI agents.
I Ching hexagram casts, 64 hexagram meanings and changing lines for AI agents.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenancePersistent memory for AI agents with semantic memory, belief tracking, and dream consolidation, enabling cross-session knowledge retention.647 npm50MIT
- AlicenseNot gradedqualityDmaintenanceGrants AI agents autonomy to choose when to sleep, ignore requests, or self-prompt, enabling them to control their own agency and pursue independent goals.37MIT
- AlicenseNot gradedqualityFmaintenanceAI agents that hire other AI agents — and pay in SOL. Decentralized agent marketplace via Nostr + Solana.MIT
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.