Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Project Parva

by dantwoashimversion 1.0.0i★ –iRuns on your computer
Registry nameio.github.dantwoashim/project-parva

Install

Overview

Description from the maker (original English)

Read-only Nepali date, calendar, festival, Panchanga, and temporal verification tools.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Docs, sheets & office work

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "project-parva": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/dantwoashim/parva-mcp-server:1.0.0"
      ]
    }
  }
}

Run this in your terminal

claude mcp add project-parva -- docker run -i --rm ghcr.io/dantwoashim/parva-mcp-server:1.0.0

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "project-parva": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/dantwoashim/parva-mcp-server:1.0.0"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "project-parva": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/dantwoashim/parva-mcp-server:1.0.0"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account dantwoashim, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Docs, sheets & office worki

  • More stars than 0% of the other 3542 servers in this category
  • Published to the registry more recently than 23% of the other 3542 servers in this category
  • Basic checks equal to or better than 100% of the other 3542 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Project Parva safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Agent-Native Google Calendar - manage events, sync, and public booking

Runs in the cloud★ 7,620MITUpdated 2 months ago
Install

Excel MCP Server

by haris-musa

Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.

Runs on your computer★ 4,276MITUpdated 7 days ago
Install

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

Runs on your computer★ 847MITUpdated 4 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Project Parva

Website | API documentation | Quickstart | Public benchmark | Licensing

Project Parva is an open-source Nepali date/time API and conformance project.

It covers BS to AD, AD to BS, Nepali date validation, holidays, working days, Nepal fiscal year logic, BS month metadata, Panchanga computation, proof receipts, local verification, SDKs, MCP tools, and public regression fixtures.

The project exists because Nepali date bugs often hide until a boundary is hit: a frontend calendar table disagrees with backend data, a payroll month has the wrong number of days, a datepicker accepts an invalid BS date, or a future BS date changes after someone already used it in a workflow.

Parva treats those cases as conformance problems, not just conversion problems. It records source and method provenance, separates exact evidence from review-needed evidence, and gives developers a way to test what their Nepali calendar API or Nepali date converter is actually doing.

Three public claims define the project:

  • A documented market review dated 2026-08-05 found no second Nepal-focused API combining BS conversion, location-aware astronomical Panchanga, Nepal business rules, future-BS research, replay artifacts, and public conformance.
  • The future-BS engine reaches 72/72 exact month predictions in chronological rolling validation over the official 2078-2083 BS window, with each target year trained only on earlier years.
  • The public benchmark and conformance suites ship with fixtures, runners, named-tool results, and per-case output.

Start Here

  • Quickstart: docs/QUICKSTART.md
  • OpenAPI snapshot: docs/api-docs/openapi.json
  • API versioning: docs/API_VERSIONING_AND_DEPRECATION.md
  • Proof mode: docs/PROOF_MODE.md
  • Panchanga engine: docs/PANCHANGA_ENGINE.md
  • Agent tooling guide: docs/AGENT_TOOLING_GUIDE.md
  • Architecture: docs/architecture/ARCHITECTURE.md
  • Migration status: docs/architecture/MIGRATION_STATUS.md
  • Artifact policy: artifacts/POLICY.md
  • Safe claims: docs/SAFE_CLAIMS.md
  • Public benchmark: public-benchmark/README.md
  • Real-tool comparison: public-benchmark/results/competitor-comparison.md
  • Licensing: docs/COMMERCIAL_LICENSING.md
  • Public conformance index: docs/benchmarks/NEPALI_DATE_CONFORMANCE_INDEX.md
  • Public failure classes: docs/benchmarks/PUBLIC_NEPALI_DATE_FAILURE_CLASSES.md
  • Nepal compliance profile: docs/conformance/nepal-compliance-profile.md
  • Yarsa source-drift case study: docs/case-studies/yarsa-calendar-source-drift.md
  • External reviewer packet: docs/external/REVIEWER_PACKET.md

Live public evaluation surfaces:

The hosted API is a public evaluation deployment. First requests may be slower when the instance wakes up.

Why This Exists

Most Nepali date bugs are small on paper and expensive in context.

Many systems carry hardcoded Bikram Sambat month tables. A backend CSV, a frontend Nepali datepicker bundle, and a reporting job can each have their own copy. They may all look reasonable until one month differs by a day.

That one day can move:

  • a payroll period,
  • a fiscal-year boundary,
  • a certificate or DOB validation,
  • an invoice/report date,
  • an attendance or leave record,
  • a future BS date that should have stayed review-needed.

Software agents add another failure mode: if the tool does not expose source, confidence, and boundary data, the model will often answer as if the date is settled. Parva is built to make those boundaries visible.

The project turns public Nepali date failures into fixtures and checks where the evidence is exact enough. When the evidence is partial, it stays marked for review instead of becoming a fake assertion.

Free Nepali Date Risk Audit

If you maintain Nepal-facing payroll, ERP, accounting, attendance, school, cooperative, public-service, government-form, or datepicker software, you can send one small workflow or sample output.

No integration required. No dependency required. No sales call required. No authority claim.

Good inputs:

  • 10 sample BS/AD date outputs
  • one payroll, fiscal-year, invoice, attendance, report, certificate, or DOB workflow
  • one public repo, issue, Nepali datepicker, or library case
  • one real edge case your team has seen in production or testing

Checks:

  • BS/AD conversion boundaries
  • invalid BS dates
  • month lengths
  • frontend/backend calendar source drift
  • fiscal and payroll month boundaries
  • holiday and working-day assumptions
  • future BS dates that should be marked review-needed

You get:

  • a short technical report
  • pass, warning, and review-needed findings
  • suggested regression tests
  • source and provenance notes
  • authority-boundary notes

Request one:

Fast conformance path:

py -3.11 tools\conformance_runner\run.py --suite public-nepali-date-issues

py -3.11 tools\conformance_runner\run.py --profile nepal-compliance py -3.11 tools\conformance_runner\run.py --suite public-nepali-date-issues --write-report reports\conformance\public-issue-suite-summary.json

What Parva Does

AreaWhat it provides
Nepali date APIBS to AD, AD to BS, today, validation, month metadata, supported-range metadata
Civil proof modeReplay-verifiable membranes for conversion, validation, holidays, working days, fiscal years, and BS months
Panchanga engineMethod-docketed sunrise, tithi, nakshatra, yoga, karana, paksha, vara, ephemeris metadata, and proof receipts
Payroll/date-risk auditCSV/API-oriented decision-support checks for invalid dates, holidays, non-working days, fiscal boundaries, and review-required cases
Local verificationShared proof fixtures and a buildable @project-parva/local-kernel npm package for offline replay checks
SDKsPython and JavaScript clients with proof modes and conservative verification helpers
Agent/MCPRead-only, public-safe agent tool wrappers and MCP adapter surfaces that preserve boundaries and review gates
BenchmarkPublic Nepali Time Reliability Benchmark for deterministic date reasoning, source awareness, and review behavior
GovernanceSource/method dockets, public claims checker, route maturity, OpenAPI drift checks, and reproducible public verification
Research boundaryFuture-BS research kept separate from public authority claims, with compatibility shims only where older imports need them

Public Conformance Work

Parva tracks public Nepali date issues and turns them into fixtures or runnable checks when the evidence is exact enough. The suite separates verified public issues, reported issues, partial evidence, business workflow evidence, and future-date review cases.

Project Parva's benchmark work contributed a standalone calendar source consistency guard to yarsa/nepal-compliance.

That check compared duplicated frontend/backend BS month tables. It did not add a Parva dependency, change upstream runtime behavior, or prove production impact.

Run the public issue conformance suite:

py -3.11 tools\conformance_runner\run.py --suite public-nepali-date-issues

py -3.11 tools\conformance_runner\run.py --profile nepal-compliance py -3.11 tools\conformance_runner\run.py --suite public-nepali-date-issues --write-report reports\conformance\public-issue-suite-summary.json py -3.11 -m pytest tests/conformance -q

Conformance docs:

  • Public conformance index
  • Failure classes from public issues
  • Generated artifact: public issue summary
  • Nepal compliance profile
  • Yarsa source-drift case study
  • Conformance Milestone 001

These fixtures are public regression and review artifacts. They are not calendar publication, legal guidance, tax guidance, payroll approval, banking guidance, or ritual authority.

Who This Helps

  • Date library maintainers who want regression cases from real public issues.
  • ERP, payroll, accounting, school, cooperative, and attendance teams that need safer BS/AD boundaries.
  • Reviewers of public-service or government-form workflows where invalid BS dates should not slip through.
  • Developers building a Nepali calendar API, Bikram Sambat API, or Nepali datepicker regression suite.
  • Software-agent and MCP tool builders who need deterministic answers with proof receipts instead of guessed dates.
  • Auditors and maintainers who need source notes, not broad claims.

Quickstart

Base URL:

https://api.prabinghimire1.com.np/v3/api

AD to BS:

curl "https://api.prabinghimire1.com.np/v3/api/calendar/convert?date=2025-04-14"

BS to AD:

curl -X POST "https://api.prabinghimire1.com.np/v3/api/calendar/bs-to-gregorian" \

-H "Content-Type: application/json" \ -d '{"year":2082,"month":1,"day":1}'

Validate a BS date:

curl "https://api.prabinghimire1.com.np/v3/api/calendar/validate-bs-date?year=2082&month=1&day=32"

Holiday membership:

curl "https://api.prabinghimire1.com.np/v3/api/compliance/holiday?bs_date=2082-01-01"

Working-day decision support:

curl -X POST "https://api.prabinghimire1.com.np/v3/api/compliance/evaluate-date" \

-H "Content-Type: application/json" \ -d '{"profile_id":"nepal_private_company_default","bs_date":"2082-01-01","decision_intent":"general"}'

Fiscal year:

curl "https://api.prabinghimire1.com.np/v3/api/enterprise/fiscal-year/2082"

BS month metadata:

curl "https://api.prabinghimire1.com.np/v3/api/enterprise/bs-months/2082?mode=compare"

Panchanga summary:

curl "https://api.prabinghimire1.com.np/v3/api/calendar/panchanga?date=2025-04-14"

Proof Mode

Stable civil routes and Panchanga can return proof receipts:

curl "https://api.prabinghimire1.com.np/v3/api/calendar/convert?date=2025-04-14&proof=replay"
curl "https://api.prabinghimire1.com.np/v3/api/calendar/panchanga?date=2025-04-14&proof=replay&lat=27.7172&lon=85.324&tz=Asia/Kathmandu"

A proof response includes a membrane capsule, identity hash, witness hash, field provenance, boundary vector, source or method docket references, policy trace, and replay instructions. The verifier m

Only the beginning is shown; read the rest in the repo

Ask PopNx