原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Project Parva

作者:dantwoashim版本 1.0.0i★ –i在你的电脑上运行
注册名称io.github.dantwoashim/project-parva

安装

概览

作者提供的说明(英文原文)

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 文档、表格与办公

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 注册中心没有列出需要填写的密钥。

你需要

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

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

在终端中运行这条命令

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

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 dantwoashim 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“文档、表格与办公”中的其他服务器比较i

  • 星标数多于此分类中其他 3543 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 3543 个服务器的 23% 更新
  • 基础检查结果等于或优于此分类中其他 3543 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Project Parva 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(1.0.0)于3个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。

有什么可以替代它?

同一分类中有:Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Agent-Native Calendar

作者:BuilderIO

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

在云端运行★ 7,620MIT2个月前更新
安装

Excel MCP Server

作者:haris-musa

Create and edit Excel files with AI: charts, PivotTables, formulas. No Excel needed.

在你的电脑上运行★ 4,276MIT7天前更新
安装

MCP Server for Excel

作者:sbroenne

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

在你的电脑上运行★ 847MIT4天前更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx