io.github.mohamedgb00714/autoplans-mcp

MCPcommunity
v0.1.2io.github.mohamedgb00714UnknownUpdated 7mo agonpmGitHub

AI-powered project planning tools for Autoplans.dev with 14+ MCP tools

This repo contains everything needed to publish your Autoplans.dev MCP server to the official registry: 1. - MCP Registry manifest using latest 2025-10-17 schema 2. - npm package configuration 3. - stdio wrapper that proxies to your HTTP API 4. - Original manifest (kept for reference) Your server runs as HTTP at , but the MCP Registry expects stdio-based packages. Our wrapper solves this by:…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
7mo agoLast update
Package
Authorio.github.mohamedgb00714
LicenseUnknown
Version0.1.2
Sourcemcp-registry
npmautoplans-mcp
GitHubmohamedgb00714/autoplans-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—
Dependencies14 resolved · 1 with advisories
Tool surface—
Security scan⚠ Warnings (0)v0.1.2 · 20d ago
DEP@modelcontextprotocol/sdk@0.5.0GHSA-8r9q-7v3j-jr4g, GHSA-w48q-cv73-mx4w
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

This repo contains everything needed to publish your Autoplans.dev MCP server to the official registry: 1. ** - MCP Registry manifest using latest 2025-10-17 schema 2. - npm package configuration 3. - stdio wrapper that proxies to your HTTP API 4. - Original manifest (kept for reference) Your server runs as HTTP at , but the MCP Registry expects stdio-based packages. Our wrapper solves this by: Publishing an npm package that provides stdio transport Proxying MCP stdio calls to your HTTP API…

Keywords
mcp