io.github.theYahia/megaplan-mcp

MCPcommunity
v1.0.0io.github.theYahiaUnknownUpdated 3mo agonpmGitHub

MCP server for Megaplan — tasks, deals management via API v3.

MCP server for Megaplan project management — tasks, deals, projects, employees, comments via API v3. 8 tools + 2 MCP prompts. Token OR Password-grant auth. Stdio + Streamable HTTP transports. If you used v1.x, the v2.0.0 release introduces a few breaking changes: HTTP transport env var renamed: → . Removed separate codepath: v1 had a hand-rolled triggered by . v2 uses 's which auto-routes via…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
3mo agoLast update
Package
Authorio.github.theYahia
LicenseUnknown
Version1.0.0
Sourcemcp-registry
npm@theyahia/megaplan-mcp
GitHubtheYahia/megaplan-mcp
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
—npm provenance (Sigstore)+0/5
→ Publish from GitHub Actions with the --provenance flag
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface8 tools · none privileged
Security scan✓ Cleanv3.0.0 · 20d ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

MCP server for Megaplan project management — tasks, deals, projects, employees, comments via API v3. 8 tools + 2 MCP prompts. Token OR Password-grant auth. Stdio + Streamable HTTP transports. If you used v1.x, the v2.0.0 release introduces a few breaking changes: HTTP transport env var renamed: → . Removed separate codepath: v1 had a hand-rolled triggered by . v2 uses 's which auto-routes via flag OR env. Same CLI flag, different implementation (now with session management, endpoint, CORS,…

Keywords
mcp