Skip to main content
Glama
molpass

numerology

by molpass
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

mcp-numerology

이름과 생년월일을 받아 수비학 핵심 수(라이프패스·표현수·소울어지·성격수·생일수·성숙수)와 마스터/카르마 넘버를 계산하는 MCP 서버. 구조화 텍스트 + 요약 카드 PNG를 반환한다.

구조·네이밍·PNG·설치 규약은 STANDARD.md를 따른다. mcp-qr skeleton 복제본.

계산 방식 (결정론적, 외부 의존 0)

표준 피타고라스(Pythagorean) 방식으로 직접 구현했다(같은 입력 → 같은 출력).

발주서가 지정한 numerology-npm은 npm에 존재하지 않고(404), 대체 패키지들도 요구 수를 깔끔히 못 채워, PM 결정에 따라 자체 구현으로 진행했다. 의존성 0, 전 과정 수기 검증 가능.

  • 글자값: A=1…I=9 반복. Y, W는 항상 자음으로 처리(컨텍스트 변형 미적용).

  • 모음: A, E, I, O, U.

  • 마스터 넘버(11/22/33): 환원하지 않고 보존.

  • 카르마 부채(13/14/16/19): 환원 마지막 두 자리 단계가 해당 값이면 표기.

  • Life Path: 월·일·연을 각각 환원 → 합산 → 환원.

수

산출

라이프패스 (Life Path)

생년월일

표현수 (Expression)

이름 전체 글자합

소울어지 (Soul Urge)

이름의 모음합

성격수 (Personality)

이름의 자음합

생일수 (Birthday)

태어난 날(日)

성숙수 (Maturity)

라이프패스 + 표현수

Related MCP server: mcp-astrology

도구

get_numerology

파라미터

타입

필수

설명

fullName

string

✅

이름. 라틴 알파벳 기준 — 한글 이름은 로마자로 표기 (예: 홍길동 → Hong Gildong)

birthDate

string YYYY-MM-DD

✅

생년월일

한글 이름 처리: 이름 기반 수(표현수/소울어지/성격수)는 라틴 알파벳 글자값으로 계산한다. 입력에 라틴 알파벳이 없으면(예: 순수 한글) 도구가 로마자 표기를 요청하는 에러를 반환한다.

출력 (둘 다 반환):

  1. 구조화 텍스트 — 각 수 + 마스터/카르마 여부 + 의미 키워드 + Life Path 환원 과정

  2. 요약 카드 PNG (1080×640, 핵심 수 6개)

예제 출력: examples/numerology_example.png (John Lennon · 1940-10-09 → Life Path 6).

설치

git clone https://github.com/molpass/mcp-numerology.git
cd mcp-numerology
npm install && npm run build

예제 카드를 직접 생성해 보려면:

npm run example   # examples/numerology_example.png 재생성

폰트: 한글 라벨을 위해 한글 가능 폰트가 필요하다. Windows는 Malgun Gothic 기본 탑재라 추가 설치 불필요. Linux는 Nanum/Noto CJK 권장.

MCP 등록 (서버명 numerology)

{
  "mcpServers": {
    "numerology": {
      "command": "node",
      "args": ["/abs/path/mcp-numerology/dist/index.js"]
    }
  }
}

/abs/path는 클론한 실제 절대경로로 바꾼다. Windows 예: "args": ["C:/Users/<you>/mcp-numerology/dist/index.js"]

스킬

페어링 스킬: skill/numerology.skill.md.

About / 제작

Hermes Agent용 MCP — molpass의 바이브 코딩(vibe coding) 프로젝트.

  • 아이디어·방향: molpass (이정훈) · https://zeolinex.com

  • 기획: Claude (Chat)

  • 개발: Claude Code

자가 호스팅 Hermes Agent에 도구로 붙여 쓰는 MCP 서버입니다.

같은 모음:

License

MIT

Available Tools

1 tool
get_numerologyGet Numerology ReportA

이름(라틴 알파벳)과 생년월일을 받아 수비학 핵심 수(라이프패스·표현수·소울어지·성격수·생일수·성숙수)와 마스터/카르마 넘버를 계산한다. 구조화 텍스트와 요약 카드 PNG를 반환한다. 피타고라스 방식, 결정론적.

ParametersJSON Schema
NameRequiredDescriptionDefault
fullNameYes이름. 이름 기반 수는 라틴 알파벳 기준 — 한글은 로마자로 표기 (예: 홍길동 → Hong Gildong)
birthDateYes생년월일 (YYYY-MM-DD)

TDQS

A4.5/5.0
Behavior4/5

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

Since no annotations are provided, the description carries the full burden. It discloses that the tool returns both structured text and a PNG image, and states it is deterministic. It does not explicitly state it is read-only, but for a get/calculator tool it is implied. Additional context like side effects or rate limits is not needed for this type of tool.

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

Conciseness5/5

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

The description is two efficient sentences in Korean. Every piece of information is useful: inputs, calculation details, output format, and methodology. No unnecessary words or repetitions.

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

Completeness5/5

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

Given the tool has no output schema, the description adequately explains the return values (structured text and PNG). It covers all necessary aspects: input requirements, calculation scope, and output form. For a simple numerology calculator, this is complete.

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

Parameters4/5

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

Schema description coverage is 100% with each parameter having a description. The tool description adds value by clarifying that the name must be in Latin alphabet and provides an example (Hong Gildong), which goes beyond the schema's description. This helps the agent properly format the input.

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 clearly states the tool takes a name (Latin alphabet) and birthdate, calculates specific numerology core numbers including master/karma numbers, and returns structured text and a summary PNG. It specifies the Pythagorean method and deterministic nature, leaving no ambiguity about what the tool does.

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?

No explicit when-to-use or alternatives are mentioned, but with no sibling tools, this is less critical. The description provides clear input format guidance (Latin alphabet for name, date format) and specifies the method (Pythagorean), which helps the agent decide if this is the right numerology tool.

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. 1 tool updatev1.0.0
    • First observedget_numerology
Deploy Server
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

TDQS

A4.4/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so no possibility of ambiguity. The tool's purpose is clearly defined.

Naming Consistency5/5

With a single tool, naming is trivially consistent. The name 'get_numerology' follows a clear verb_noun pattern.

Tool Count2/5

One tool for a domain like numerology feels insufficient; many standard operations (e.g., separate tools for different number types) are missing, making the surface too thin.

Completeness4/5

The tool comprehensively calculates all core numerology numbers (life path, expression, etc.) and returns both text and image. Minor gaps might include alternative systems or detailed interpretations, but the core functionality is well-covered.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • mcp-astrology

    molpass
    A
    license
    A
    quality
    C
    maintenance
    Receives birth information and returns Western astrology natal charts including planetary positions, houses, ASC/MC text, and a chart PNG image.
    1
    MIT

  • mcp-ziwei

    molpass
    A
    license
    A
    quality
    C
    maintenance
    Calculates and returns a Ziwei Doushu (Purple Star Astrology) chart based on birth date, time, and gender. Returns both structured text of the 12 palaces and a PNG image of the chart.
    1
    MIT

  • mcp-qimen

    molpass
    A
    license
    Not graded
    quality
    D
    maintenance
    Evaluates Qimen Dunjia divination for a given date and time, returning structured text and a 9-palace PNG chart.
    MIT