InvoiceGen

io.github.everyai-comv1.0.0Updated Oct 1, 2026

Freelancer invoices with totals, tax, due dates. Free.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP endpoint for generating freelancer invoices with totals, tax, and due dates.

What it does: InvoiceGen is a hosted MCP server that lets an assistant produce freelancer invoices, including line-item totals, tax, and due dates. The registry description presents it as free to use. No tool list is published in the manifest, so the exact tool names and parameters are not documented here.
When to use it: Worth considering when an assistant needs to draft or assemble simple freelance invoices with tax and payment deadlines as part of a billing or bookkeeping workflow. Because the tool surface is undocumented, check the endpoint's own documentation before relying on it.
Requirements: A remote Streamable HTTP endpoint at No authentication, environment variables, or headers are declared, and no local package or runtime is needed. Network access to the endpoint is required.

Before you install

The endpoint is remote and declares no authentication, so anything sent to it leaves the user's machine and may not be access-controlled. Invoice content typically includes client names, amounts, and tax details; avoid sending sensitive business or personal data until the provider's handling is clear. No payment or write actions are described in the supplied material.

Installation

In SourceWeft

Open InvoiceGen in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "invoice-gen": {
      "type": "http",
      "url": "https://invoice-gen.magicteams.ai/mcp"
    }
  }
}

README

Sahadeva

[CI]

A clean-room, Cloudflare-native research build for a transparent South Indian AI Jyotish workspace.

Run locally

The Cloudflare Vite plugin serves the React application and Worker API together. POST /api/chart is deterministic. POST /api/interpret uses the configured Workers AI binding.

AI narration

Narration uses only Cloudflare's native AI binding and Cloudflare-hosted @cf/... models. The default is @cf/zai-org/glm-5.3-flash; AI_MODEL selects it in wrangler.jsonc, and non-@cf/ model names are rejected in favor of that safe default. No AI Gateway, third-party API, or provider token participates in this path. GET /api/ai/status exposes only non-secret readiness metadata, and successful narration identifies the Cloudflare model while keeping calculated evidence immutable.

The consultation surface adds deterministic topic judgments, house exploration, natal Panchanga, convention comparison, Prashna, timing fusion, rectification, and depth endpoints. Topic judgments share one evidence-ledger engine across web, MCP, reports, and the Expo mobile client. Opt-in snapshots store versioned ledgers and a hashed follow-up secret—not names, places, or raw birth input—and calibration remains descriptive rather than predictive.

Connect through MCP

After deployment, compatible clients can connect to:

The Streamable HTTP endpoint exposes a high-signal catalog led by a comprehensive first-reading dossier. The returned profile reference lets later consultations answer focused questions from the verified natal context without repeating the dossier. It also supports chart reports, Prashna, timing, separate North Indian Ashtakoota and South Indian ten-Porutham compatibility, Panchanga, Muhurta and visual reports. Specialist tools remain directly callable and are documented through an MCP resource. Chart calculation does not require a language model. Public calls are rate-limited; optional scoped Bearer keys provide metering and vault integration. See MCP integration examples.

Clients can call assess_prediction_readiness before interpretation to distinguish implemented calculation from reviewed rules and calibrated prediction. Lal Kitab currently provides source-linked structural inspection. All of its material is retained, including sensitive topics and remedies; reviewed claims can later use graduated caution-led disclosure, while unreviewed personalized output remains withheld. See Prediction quality and MCP gap audit.

The source-only analyze_lal_kitab workflow now converts natal placements to Lal Kitab fixed houses and returns locators for all relevant planet-house sections without publishing their unreviewed claims. The complete integration inventory is in Lal Kitab integration map.

The web chart surfaces the same fixed-house map, source locators, retained-sensitive-material caution, and an independent calculation-quality audit. MCP clients can use the lal_kitab_consultation prompt or compose the equivalent tools from the published workflow resource.

For evidence-first use across AI clients, the MCP now publishes sahadeva://prediction-quality and the evidence_first_prediction prompt. Reviewed-rule search, rights-aware passage discovery, separate-tradition comparison, per-claim auditing, versioned outcome capture and conservative validation reporting are available as typed tools. These improve traceability and abstention; they do not guarantee prediction accuracy or convert unreviewed traditions into validated knowledge.

The primary consultation also supports a compact cross-tradition whole-person profile and consent-aware remedy selection. Its security contract is published at sahadeva://security; production profile references are keyed opaque identifiers, restricted knowledge remains server-side, and retrieved text is explicitly untrusted data. See MCP AI orchestration and security.

Workers AI has a limited daily free allocation. Sahadeva therefore describes hosted narration as optional and allowance-backed, not unlimited free inference.

Verify

Current status

The product interface and computation pipeline are functional. The Moon, Panchanga transitions, and Lahiri convention have high-precision reference fixtures; the application remains a research preview until independent Lagna, solar-event, complete-strength, and practitioner certification gates are satisfied. See RESEARCH_AND_ARCHITECTURE.md for the calculation boundary, topology, and validation gates.

Clean-room boundary

No third-party astrology engine is bundled. Repository research informed the capability map and test strategy only. Production algorithms must be derived from documented specifications and independently validated.

Continuous integration

Pushes and pull requests run the verify pipeline on Flare Actions (flare.yml): typecheck, unit tests, migration and secret checks, audit, build, bundle budget, Playwright e2e, and the Expo mobile verify. Run completions email all registered users.

License

MIT — see LICENSE.

Source: README.md at commit a7d5243

Tools

Tool metadata has not been indexed yet.

Version history

v1.0.0LatestOct 1, 2026