Planify
Planify is an MCP server published by planifyapps.com, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.
Does Planify support the current MCP specification (2026-07-28)?
Not yet confirmed. Planify is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is Planify a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for Planify (as of 2026-08-20).
How do I connect to Planify?
Planify is available via the package npm:@planifyapps/mcp, the official MCP Registry under com.planifyapps/planify, the source repository at https://github.com/gsrathoreniks/planifyweb. Authentication: unknown. Transports: stdio.
Does Planify support MCP revision 2025-11-25?
Yes. Planify supports MCP revision 2025-11-25 (checked 2026-08-20).
Does Planify support MCP revision 2026-07-28?
No. Planify was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were Planify's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
Schedule and publish social posts to Twitter, Instagram, LinkedIn, Pinterest, Bluesky and more.
Which MCP spec revisions does Planify support?
Planify has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source | |
| MCP 2026-07-28 | Not supported | Source |
How widely adopted is Planify?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
Repository and package signals for Planify
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
The repository this server declares no longer resolves. That is a measurement, not
a failed lookup: https://github.com/gsrathoreniks/planifyweb returned 404 when checked.
Package (npm) as of
- Latest version
0.4.0- Last published
- First published
- Releases
- 3
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 2
- Unpacked size
- 47 KB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record for com.planifyapps/planify at version 0.2.0 - lists package npm:@planifyapps/mcp and repository https://github.com/gsrathoreniks/planifyweb - accessed
- npm registry metadata for @planifyapps/mcp at published version 0.2.0, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed