Finance education article — Atom

Official registry Finance and payments

Finance education article production-record audit, delivered per API call as an atom on Conduit.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http finance-education-article-atom 'https://atoms.pipavia.com/mcp/finance-education-article' --header 'Authorization: <Your Conduit Atoms gateway key, as '\''Bearer <key>'\''. One gateway key works across atoms; it must hold this atom'\''s scope (finance_education_article). Sign up at https://atoms.pipavia.com, open this atom, and issue your key.>'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "finance-education-article-atom": {
            "type": "http",
            "url": "https://atoms.pipavia.com/mcp/finance-education-article",
            "headers": {
                "Authorization": "<Your Conduit Atoms gateway key, as 'Bearer <key>'. One gateway key works across atoms; it must hold this atom's scope (finance_education_article). Sign up at https://atoms.pipavia.com, open this atom, and issue your key.>"
            }
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. atom-services
  2. The model in plain words
  3. Layout
  4. The public cut
  5. Status

atom-services

Conceived by Nrupal Akolkar · Built by Muse (Arjun/Wright).

One collective repo for all product atoms. An atom is a small, independent service that delivers one bounded judgment artifact — a VERDICT, a CHECK, a MAP, a STAMP, a REPORT — over API / MCP / agent / human endpoints, paid per unit delivered. Atoms never sell the underlying knowledge; they sell the artifact the knowledge produces.

The model in plain words

  • Independent atoms, one home. Every atom is its own named service unit in services/<service-name>/, with its own endpoints, its own payment plan, and its own growth / retention / maintenance docs. Atoms are never merged into existing product repos — this repo is their only home. Shared rails live once at the repo root (rails/), not inside any product.
  • The rail is Conduit. Atoms are listed and discovered through Conduit (the owner's connector marketplace, live since 2026-11-12) and served as key-gated MCP/API endpoints in Conduit's shape. Where Conduit lacks a piece atoms need, the gap is named in rails/ and in BUILD-LOG.md — never papered over.
  • One by one. Atoms release one by one (or bundle by bundle), in the approved queue order — never the whole register at once. Release #1 is release-readiness-verdict.
  • Volume pricing doctrine. Cheap per unit, millions of units. The earning lever is refinement — narrower, sharper services get called more — not price height. Every price must clear the atom's measured production cost; until cost is measured, atoms carry a pricing unit only and no price.
  • One Stripe account (2351485 ALBERTA INC., public name AIMLDS) settles everything. Settlement is aggregated — prepaid balance / packs drawn down per unit — never a card charge per call.

Layout

registry/    The authoritative register (register.yaml + ATOMS-REGISTER.md,
             copied unchanged) + PUBLIC-LIST.md (generated).
rails/       serving.md · billing.md · docs-standard.md · contracts.md —
             how every atom in this repo is served, metered, billed,
             documented, and contracted. SPEC marks what is not built yet.
services/    One directory per PUBLIC atom (162), generated from the
             register by tools/generate.py. Each unit: SERVICE.md,
             contract.yaml, growth.md, retention.md, maintenance.md.
tools/       generate.py — regenerates registry/PUBLIC-LIST.md and all
             service scaffolds from registry/register.yaml.
BUILD-LOG.md What was built, verified counts, test evidence, named gaps.
CHARTER.md   The binding rules of this repo (read before changing anything).

The public cut

255 candidates were screened. Public = Tier A (48) + Tier B (114) = 162. Tier C (34, personal/internal), Tier D (40, held) and FAIL-self-use (19, not services) get no service units — they exist in registry/ only, marked non-public with reasons (registry/PUBLIC-LIST.md).

Status

Scaffold + atom #1's deterministic core are built and tested locally. Nothing in this repo is deployed or live. Atom #1's remaining road to live on Conduit is listed in BUILD-LOG.md.

Frequently asked questions

What is Finance education article — Atom?

Finance education article production-record audit, delivered per API call as an atom on Conduit.

How do I install Finance education article — Atom?

It runs as a remote server. In Claude Code: claude mcp add --transport http finance-education-article-atom 'https://atoms.pipavia.com/mcp/finance-education-article' --header 'Authorization: <Your Conduit Atoms gateway key, as '\''Bearer <key>'\''. One gateway key works across atoms; it must hold this atom'\''s scope (finance_education_article). Sign up at https://atoms.pipavia.com, open this atom, and issue your key.>'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Finance education article — Atom need an API key?

Yes. It expects Authorization, which you set in its configuration.

Is Finance education article — Atom open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains Finance education article — Atom?

It is published by nrupala. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.