mcp server
Project Parva
Read-only Nepali date, calendar, festival, Panchanga, and temporal verification tools.
Description as published by the maintainer. Source
- version 1.0.0
- active
active — Most recent push to the repository was 2026-08-05.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 26 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-05 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 3 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-08-05 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | AGPL-3.0 | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-08-05 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
io.github.BetterDB-inc/monitor
— last commit 2026-08-06, shares redis
BetterDB MCP server - Valkey observability for Claude Code and other MCP clients
-
CalendarMCP
— last commit 2026-06-07, shares calendar
Hosted Google Calendar MCP server for AI agents. No self-hosting or Google Cloud setup.
-
app.reassign/reassign
— last commit 2026-07-25, shares calendar
Reassign: a circular 24-hour calendar and time-tracking copilot with ADHD-friendly scheduling.
-
com.local-mcp/local-mcp
— last commit 2026-08-06, shares calendar
Let ChatGPT, Claude & Cursor use your Mac: email, calendar, iMessage, Teams, files. Local, free.
-
io.github.AIWerk/mcp-server-cal
— last commit 2026-06-22, shares calendar
Cal.com scheduling MCP server: manage bookings, event types, and availability.
-
Google Workspace MCP Server
— last commit 2026-08-04, shares calendar
Google Workspace as 39 curated MCP tools: Gmail, Calendar, Drive, Sheets, Docs, and Tasks.
-
io.github.elagerway/magpipe
— last commit 2026-06-06, shares calendar
Manage AI voice agents, calls, SMS, contacts, and phone numbers via Magpipe.
-
com.beacio/mcp
— last commit 2026-07-30, shares react, sdk
MCP server for Web Bluetooth on iOS Safari: scaffolding, UUID lookup, extension detection.
-
io.elaan/mcp
— last commit 2026-08-05, shares react, sdk
Create Elaan notification types, templates and brands, trigger sends, and debug delivery.
-
Airweave Search
— last commit 2026-06-05, shares api, sdk
MCP server for searching Airweave collections with natural language queries.
These share tags the maintainers applied themselves, such as redis, calendar, react, sdk. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: api, bikram-sambat, bs-ad-conversion, calendar, calendar-api, fastapi, fiscal-year, nepal, nepali-calendar, openapi, panchanga, python, react, redis, sdk.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab