Publifye service estate
Every service Publifye runs,
and how to call it.
Publifye AS is a Norwegian publishing house in Oslo — org.nr 826 774 622, publishing since 2016, a registered ISBN publisher. It publishes Bibles and books, builds the software it publishes them with, and runs the infrastructure churches and ministries use to reach readers.
This page is the operator index of that estate: every service the company actually runs, its hostname and its MCP endpoint — read live from the PubHub registry, never hand-written. publifye.org is the reader-facing half: what Publifye is, and what you can get.
Nearly everything here speaks MCP — the Model Context Protocol, how an AI assistant calls a tool instead of guessing. A tagged service exposes its tools at
https://<host>/mcp, JSON-RPC 2.0 over HTTP POST.
The whole estate as JSON · llms.txt
What Publifye does, and what you get
A page of hostnames is no use if you do not know what the company behind them does. Answers are kept in Lighthouse, so they are edited where the rest of the customer-facing copy lives — not in this page’s source.
What is Publifye?
A Norwegian company (Publifye AS, Oslo — org.nr 826 774 622) that makes Scripture accessible in every language, on every device.
It began in 2016 as TruthBeTold Ministry, publishing digital parallel Bibles, and incorporated as an aksjeselskap in February 2021. Today it publishes biblical resources and builds the software underneath them — the services listed on this page.
What is this page, and how is it different from publifye.org?
publifye.org answers what Publifye is and what you can get. It is the place to start if you want a Bible, an app, or a book.
publifye.pro — this page — is the other half: what actually runs, where, and how to call it. Every row is read live from the PubHub service registry, so nothing here is hand-maintained and nothing here is aspirational. If it is listed, it is deployed.
What does "Open to you" versus "Behind SSO" mean?
Open to you — published to customers through Lighthouse, our sign-in and entitlement service. No account is needed to look.
Behind SSO — staff and machine surfaces. They are listed because their hostnames are already public in DNS and in certificate transparency logs, so withholding the list buys no secrecy. You will need a PubHub session or a service key to get past the door.
A card with no link has no web page at all: it answers over MCP or its API only.
What can I actually use today?
- Darash — a scripture research engine: 59 Bible texts, Hebrew and Greek lexicons, morphology for every word, 446,544 cross-references and 13 dictionaries. Used through an AI assistant, or self-hosted as a single binary that works offline.
- Junifye — write and publish a book with an AI assistant, side by side. Web reader, PDF, EPUB and print interior.
- Lexifye — dictionary authoring, one atomic tool per edit.
- Tringine — compose your own Bible edition from one to three translations, aligned verse for verse, typeset four ways.
- TruthBeTold Ministry — the Bible store: multilingual ePub Bibles, King James with Strong's, parallel editions.
Why does almost everything here speak MCP?
MCP — the Model Context Protocol — is how an AI assistant calls a tool instead of guessing.
Every service carrying the MCP tag exposes its data as tools your assistant can call directly from Claude, Cursor, or your own agent. For Scripture that is the whole point: the answer comes from the text, with the verse and the Strong's number attached, rather than from a model's memory of it.
The MCP endpoint of any service is its hostname plus /mcp.
What does it cost, and is anything free?
It varies by service, and each one states its own terms — follow the link on its card.
Some things are free by design: free Bibles for churches (up to 25 EPUB editions, no account and no cost), and a large part of the Junifye library is free to read in the browser.
Paid services are sold through Lighthouse. You sign in once, and your access follows you across every Publifye service.
Can I build on this?
Yes. The public services are meant to be called, not just visited — that is why this page lists hostnames and MCP endpoints rather than screenshots.
For anything beyond the published surface — a service key, a higher quota, a private edition, an integration — say what you are building at publifye.org/contact.
Open to you
Published to customers through Lighthouse. No account needed to look.
Multi-tenant Apple Books delivery. One book is delivered ONLY to its owner's Apple provider — every request is an isolated job with its own tmpfs directory, its own credential, and its own Transporter working directory. Exactly one Transporter runs at a time.
The World English Bible read aloud. Text from darash, voice from pubvoice, generated one chapter at a time on demand and served from local disk.
Darash — scripture research engine for AI assistants. 59 Bible texts, Hebrew & Greek lexicons, cross-references, store & install.
Junifye — the writing and publishing tool: you and your AI, writing joined, side by side. Bible-PDF authoring via atomic MCP tools plus a browser editor. AI never touches JSON or LaTeX: all chapter + dict editing flows through schema-validated block/span primitives that round-trip the canonical JSON schema. Tectonic renders the assembled book to PDF.
Dictionary authoring via atomic MCP tools. Dict -> Entry -> Definition: top-level dictionary contains lemma entries; each entry holds one or more definitions with part-of-speech, examples, and optional metadata. Dragonfly-backed, schema-validated.
The Publifye fleet blog at blog.publifye.com — one public post/changelog surface for every Lighthouse-registered app. AI drafts, a human approves, and RSS, the per-app JSON feed and the Lighthouse account hub are downstream projections of that one authoring act.
Corporate site for Publifye AS — publifye.com, aedit-editable copy
Custom Bible builder — compose editions from darash and typeset four deliverables per build: a print-ready PDF, screen-reading PDFs (light + dark) and an EPUB3. The third engine (engine → aengine → tringine).
TruthBeTold Ministry — digital Bible store. Multilingual ePub Bibles (KJV + Strong's, parallel translations) sold via Lighthouse, delivered as ePub.
Behind SSO
Staff and machine surfaces. They are listed because their hostnames are already public in DNS and in certificate transparency logs — hiding the list buys no secrecy, and costs this page its purpose. You will need a PubHub session or a service key to get past the door.
Fleet-wide append-only audit trail — who did what to which record, across every Publifye service, retained exactly 365 days. Disk-authoritative day partitions with derived Redis rollups; no delete-by-id, no delete-by-filter, no clear tool. Reads are restricted to admin and are themselves audited.
Turns a YouTube URL into a structured junifye book: yt-dlp captions → ISAC proofread + chapterization → junifye chapters, fully automated
Binary distribution service with auto-update support for desktop tools and services
One gated publishing pipeline for every outbound social network. Draft once, a human admin approves the whole fan-out, and per-network adapters deliver to Telegram, Facebook, X, LinkedIn and Dev.to. Registered destinations, per-(network,destination) never-repost fingerprints, SETNX publish locks, permanent history, SSO admin UI + MCP.
Source-grounded lookup, search and name resolution over Brønnøysundregistrene's Enhetsregisteret with key financials from Regnskapsregisteret on explicit request, served as customer (OAuth 2.1) and fleet (PubHub S2S) MCP
Church Bible access system - registration-gated Bible distribution at resources.publifye.org
Web UI for managing Claude Code CLI sessions remotely with SSE streaming, session management, and cron scheduling
Explicitly opted-in service release coordination with durable decisions and Traefik file routing.
Norges Bank exchange rate service - daily sync of 38 currencies against NOK, plus a World Bank buying-power index per country, with MCP tools for conversion, rate lookup and local pricing
Plug and play Bible research. One binary, simple setup — connect to Claude, Codex, or any MCP-compatible tool and start studying. Strong's Hebrew/Greek with Abbott-Smith, BDB and LSJ lexicons. Morphological parsing (31,167 verses). 446,544 cross-references. 13 dictionaries, each with a provenance record: Thayer's Greek-English Lexicon (Harper & Brothers 1889 Corrected Edition, transcribed from the page images), ISBE, Bullinger, Fausset, Easton, Smith, Hitchcock, Nave's, Torrey, Hawker, Wilson's, ATS and Webster's. Semantic search, Hebrew pictographs, gematria, etymology trees. ELS Torah Code Discovery across 304,805 Koren Torah letters. 59 translations, 36 languages. 94 tools. Available for macOS, Linux, and Windows. ~205MB, works offline. CLI, HTTP API, and MCP server.
Docker Swarm infrastructure management with streaming log collector, pattern-based dedup, and MCP tools for AI-assisted operations
Development Guidelines Service with Web UI and MCP API - provides coding standards, best practices, and architectural guidance
The fleet's in-between for files: an ephemeral share lane that hands a human a short-lived link (memory only), and a permanent CDN lane that publishes immutable public assets to files.publifye.com on behalf of authenticated services and operators.
MCP flow orchestrator - event-driven workflow automation
Ebook publishing tracker for Gumroad with ISBN management, S3 integration, and LLM-powered tag generation
MCP control plane that provisions, operates, and rolls out sellable Hermes (iris) agents. Mints scoped keys via pubhub, meters spend via isac, and deploys agent stacks through docker-service (dockr) over S2S MCP. Includes a guided post-purchase Telegram onboarding wizard.
The brain of the fleet bot-trap. Every leaf service runs the ahoneypot library, harvests cheap bot signals at its door and reports them here in coalesced batches; this service scores them into an enforcement ledger the leaves sync and apply locally. Identity classifies (verdict, never a block); only request rate and exploit probing earn an l1/l2 tier. Implements the ahoneypot/wire contract. Spec: index/specifications/honeypot-service-spec
Unified LLM access for OpenAI, Google Gemini, Anthropic Claude, DeepSeek, and xAI Grok, with optional OpenRouter routing
ISBN pool registry — journal-first durable store for all Publifye ISBNs with assignment quality gate (pubcontacts-verified authors), legal-deposit tracking, MCP + SSO admin UI
The authenticated remote door to jack: Lighthouse OAuth in front of the host's own `jack stdio`, admin-only, read-only, confined to ~/repos. Spec: index/specifications/jackgate-service-spec
Norwegian legal corpus research with persistent reviewed metadata.
Publifye Public SSO — Customer authentication service
Internal LinkedIn post pipeline with a hard per-post approve gate. Draft via MCP or UI, Jørn approves, the service schedules US-Central prime-time publishing to the LinkedIn Posts API. Registered tag vocabulary, full permanent history, SSO admin UI + MCP.
E2E test orchestrator for all Publifye UI services — embeds Playwright JS tests, runs headless Chromium, live dashboard with SSE progress
Marco Polo for Publifye's wares: how our products and pages travel to the world's marketplaces and search engines, and whether they are found. Google Merchant API v1 and Search Console first; built so Bing, Apple and other surfaces can follow. Spec: index/specifications/google-service-spec
Book metadata service with 19,961 curated books and hybrid search optimization
The NB2026 Norwegian Bible translation harness, as a service. Owns the FACTS (darash Hebrew/Greek, Strong's, morphology, cross-refs, Norwegian cribs) and ISAC model proposals, writes one record per verse with an open verdict block that an AI judge fills and `seal` validates against the facts. Exposes the whole pipeline over MCP so an AI operator can drive it, plus an SSO web UI where humans read verses live and flag any rendering for redo.
Congregation outreach management - MCP-driven
Campaign orchestrator - email campaigns to segmented audiences via MCP
PubChat — two-way conversational chat widget. Multi-tenant, embeddable on any website via script tag. (Counterpart to pubmsg, the one-way notification gateway.)
QA checklist management service for tracking testing and release verification
City database and tagging service — GeoNames import, tag tracking, next-untagged API
Master customer register for Publifye ecosystem services
AI-guided web crawl orchestrator — takes URL + prompt + schema, returns structured JSON
Visual MJML template editor with AI-powered MJML generation and Data Puller Builder for email creation
Documentation service with versioned pages, MCP API, and web interface
Central authentication service for all Publifye services with SSO and API key management
Transactional-documents authority for the Publifye ecosystem: per-store branded receipts and invoices, event-driven (payment_paid), multi-line-item with tax/totals, multi-currency, capability-URL PDFs rendered via pubrender. Invoices request payment via Stripe link (pubpay) or bank transfer with a KID reference.
Web storefront for Publifye ebook licensing platform
Hosted resource cards with public previews and versioned admin publishing.
Public-facing website for Publifye's biblical content and services
Centralized logging service with full-text search, filtering, and export capabilities
Unified email operations: IMAP inbox reading, SMTP replies, SES campaigns
AI memory and context persistence service for maintaining conversation history
Real-time messaging service for inter-service and user communication with web UI
Payment gateway for the Publifye ecosystem: single Stripe integration, buyable/product registry, transaction ledger, receipts, and verified payment events. Entitlement-blind — consumers (lighthouse) interpret products into access via pubhub.
Shared HTML-to-image rendering service for the Publifye ecosystem using headless Chrome
Web search service with Serper.dev, ISAC-powered term generation, and Redis result caching
Central analytics platform for all Publifye services
Task management service with hierarchical tasks, comments, and user assignment
Text-to-speech service for the Publifye ecosystem using sherpa-onnx with LLM preprocessing via isac
Backup service for Redis databases with S3 storage and restore capabilities
Web content fetcher — Chrome rendering to clean Markdown for the Publifye ecosystem
Work hour tracking for the Publifye team. Log hours (work, vacation, sickness), enforce 72-hour logging window, late-entry approval flow with email escalation.
Central registry for deployment recipes and installation records
Official website for the Recipaie specification - AI-readable deployment recipes and execution proofs
Book licensing API with credit system and Stripe integration
A multi-book picture-book platform by Publifye AS. Ships with The Watermark — For Children; grows with more AI-authored picture books.
Book subject taxonomy — resolves BISAC and Thema codes to their official headings, crosswalks between schemes, records each book's subjects once for every consumer, and emits compliant EPUB3 dc:subject metadata. Owns the fact nothing else owned: what a subject code MEANS.
Tripletex accounting bridge for automated bilagsfoering via MCP
Multi-tenant CV hosting. Holds a person's CV as JSON Resume, keeps language editions in parity, renders a typeset PDF via tectonic, and serves it under owner-controlled visibility. MCP-first: every capability is a tool, the web UI is the seeing surface.