OpenFate Bazi MCP vs Orthotomeo
A side-by-side look at the OpenFate Bazi MCP and Orthotomeo MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose OpenFate Bazi MCP for spirituality & esoterica work as a local process; choose Orthotomeo for spirituality & esoterica over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose OpenFate Bazi MCP when
- You need dedicated capabilities in the Spirituality & Esoterica domain.
- You prefer a local stdio subprocess transport.
- You want tools like
calculate_bazi_chart, detect_bazi_interactions, calculate_true_solar_time.
Choose Orthotomeo when
- You need dedicated capabilities in the Spirituality & Esoterica domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
attestation, cite, concord_lemma.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Spirituality & Esoterica | Spirituality & Esoterica |
| Quality signal | 65/100 · Great | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 160 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 6 | 12 |
| Full listing | View OpenFate Bazi MCP | View Orthotomeo |
Tools & capabilities
OpenFate Bazi MCP tools 6
calculate_bazi_chartCalculate a deterministic OpenFate Bazi/Four Pillars chart with True Solar Time correction, Day Master, DAYUN_SECOND_V2 onset receipts, Da Yun cycles, and branch interactions. Pass an exact birth time plus timezone or timezoneId for a calculated V2 onset; otherwise inspect the explicit unavailable/fallback receipt.detect_bazi_interactionsDetect raw Earthly Branch relationship occurrences for a natal chart and optional annual and Da Yun branches. Preserves every matching pillar position, including repeated branches. Covers clashes, six-combinations, the eight central-branch half-trines (COMBINATION_HALF), full trines, directionals, punishments, destructions, and harms. Results establish relationship presence, not weights, cancellation, or automatic transformation; targetElement is an affinity, not transformed energy.calculate_true_solar_timeCalculate OpenFate True Solar Time from civil birth time, longitude, timezone, and optional DST offset. Use this when explaining why the hour pillar may differ from ordinary clock-time tools.reverse_bazi_to_solar_timesFind possible Gregorian datetimes that produce a given four-pillar Bazi string. This is useful when a user only has a Bazi chart or screenshot. This lookup uses clock-time pillars without location-based true solar correction.get_openfate_bazi_policyReturn OpenFate calculation policy and LLM guidance for Bazi chart calls.get_openfate_bazi_resourcesReturn canonical OpenFate URLs for charting, readings, compatibility, wealth, true solar time, and AI crawler metadata.
Orthotomeo tools 12
attestationReturns the WHNT-style Type/Editions manuscript-tradition columns as neutral text-critical data (e.g. Mark 16:9-20 = Type KO) - which editions carry a word, with no argument for or against a variant.citeRenders Citations (from any of the above tools) as quoted, fully-attributed Markdown bullets - the only sanctioned bridge from a query result to pastable study-document text.concord_lemmaComplete-or-fail concordance: every words row in corpus whose lemma, dStrong, or (with by="surface") exact inflected surface form matches query. Route lemma/Strong's-number/surface-word lookups here, never by writing SQL or guessing occurrences from memory. This deployment caps one concordance result at 2000 occurrences and refuses anything broader, reporting the exact match count in the error. Call count first when a query might be broad - count is never capped.concord_phraseComplete-or-fail multi-word concordance: every occurrence, within one verse, of tokens (lemma strings) appearing in order within window intervening words of each other (window=0 = strictly adjacent). This is the tool for a phrase query like εἰς ἄφεσιν. This deployment caps one concordance result at 2000 occurrences and refuses anything broader, reporting the exact match count in the error. Call count first when a query might be broad - count is never capped.countOccurrence tally (total + per-book breakdown) for the identical query concord_lemma would match. count.Total always equals len(concord_lemma(...)) - use this to sanity-check a concordance result, or when only the number matters.get_passageReturns get_verse's result for every canonical verse in a contiguous, single-book range, in order - verse boundaries preserved, never concatenated into one blob.get_verseReturns verbatim verse text with provenance for one canonical reference, one Citation per requested edition (KJV, ASV, WEB, BSB, Brenton).interlinearReturns a row-aligned reading view for every word in a verse (or one word, if word is given): original text, transliteration, gloss (via lexicon_lookup), grammar, and manuscript attestation stacked per word - the composed display shape for a study reading view, built on parse and lexicon_lookup rather than any new query. This is the most complete per-word view; use parse or attestation when you want only one of those facets.lemmatizeReturns the ordered lemma list for a verse (words with no lemma are omitted, not fabricated).lexicon_lookupResolves a disambiguated Strong's number (dStrong) to its lexicon entry: lemma, transliteration, gloss, and - for a Greek entry only - a fuller definition (Abbott-Smith 1922, Public Domain). A Hebrew entry's definition field is always omitted: it is abridged BDB via Online Bible, which requires permission not yet obtained, so only its gloss is ever returned. Not to be confused with the get_verse/get_passage tools, which resolve a Ref to translated verse text, not a dStrong to a dictionary entry.parseReturns dStrong + expanded morphology (via the T6 morph_codes table) for every word in a verse, or one word if word is given. LXX corpora (Swete, OSS-LXX-lemma) are always Flagged - neither carries morphology.resolve_refReports, for every per-verse content edition (KJV, ASV, WEB, BSB, Brenton, TAGNT, TAHOT, Swete, OSS-LXX-lemma), whether a canonical reference has a counterpart there and where. Cross-edition divergence (a T4b merge/renumber/divide, or a reference simply missing from an edition) is reported as Caveats - never a silent shift.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
OpenFate Bazi MCP
{
"mcpServers": {
"openfate-bazi-mcp": {
"command": "npx",
"args": [
"-y",
"@openfate/bazi-mcp"
]
}
}
}
Orthotomeo
{
"mcpServers": {
"orthotomeo": {
"url": "https://orthotomeo.app/mcp"
}
}
}
Frequently asked questions
OpenFate Bazi MCP is categorized under Spirituality & Esoterica and uses a local stdio subprocess. Orthotomeo belongs to Spirituality & Esoterica and uses a remote HTTP/SSE transport. Pick OpenFate Bazi MCP for spirituality & esoterica work and Orthotomeo for spirituality & esoterica.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
OpenFate Bazi MCP has no declared pricing — check the project's own site. Orthotomeo has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add openfate-bazi-mcp and orthotomeo as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, OpenFate Bazi MCP has a quality signal of 65/100 (Great) with 2 views, 0 installs and 160 GitHub stars. Orthotomeo has 55/100 (Good) with 2 views, 0 installs and 0 GitHub stars.