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:…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 2 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
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…
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.