@aidemd-mcp/server

MCPattested
v0.10.4TetsuKod.aiMITUpdated todaynpmGitHub

MCP server that teaches any agent the AIDE methodology through tool descriptions and progressive disclosure tooling

Works in
ClaudeCursorCopilotGemini

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.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
131Downloads/wk
4GitHub stars
todayLast update
Package
AuthorTetsuKod.ai
LicenseMIT
Version0.10.4
Sourcenpm+mcp-registry
npm@aidemd-mcp/server
GitHubaidemd-mcp/server
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ 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>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 9b21a7b
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface10 tools · none privileged
Security scan✓ Cleanv0.11.1 · todayHow well does this scan work?
EvalsNone
IndexedOct 11, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

10 tools · none privileged
Statically extracted from the published packagev0.11.1 · 5h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

aide_discoverNo description published

This tool published no description. Forge does not invent one.

aide_readRead an .aide spec file with full context. Returns the file content, its classified type (intent/research/plan/todo), related specs in the same directory, and links found in the content (relative paths, inline references, URLs). Use this after aide_discover to drill into a specific spec.

Read an .aide spec file with full context. Returns the file content, its classified type (intent/research/plan/todo), related specs in the same directory, and links found in the content (relative paths, inline references, URLs). Use this after aide_discover to drill into a specific spec.

No input schema was published for this tool.

aide_scaffoldNo description published

This tool published no description. Forge does not invent one.

aide_cleanupNo description published

This tool published no description. Forge does not invent one.

aide_validateHealth check for .aide spec files in the project. Detects orphaned specs (in folders with no orchestrator), missing specs (orchestrators with 3+ helper imports but no .aide), naming conflicts (.aide + intent.aide in same folder), broken links, orphaned research (research.aide without intent spec),…

Health check for .aide spec files in the project. Detects orphaned specs (in folders with no orchestrator), missing specs (orchestrators with 3+ helper imports but no .aide), naming conflicts (.aide + intent.aide in same folder), broken links, orphaned research (research.aide without intent spec),…

No input schema was published for this tool.

aide_upgradeNo description published

This tool published no description. Forge does not invent one.

aide_infoNo description published

This tool published no description. Forge does not invent one.

aide_brainNo description published

This tool published no description. Forge does not invent one.

aide_initNo description published

This tool published no description. Forge does not invent one.

aide_inspectReturn JSDoc, signature, and kind for a named symbol without opening the full file — Tier 2 progressive disclosure for code. When an agent knows a function name from an import list or orchestrator file, call inspect to learn what the symbol does, what it accepts, and what it returns, based on its c…

Return JSDoc, signature, and kind for a named symbol without opening the full file — Tier 2 progressive disclosure for code. When an agent knows a function name from an import list or orchestrator file, call inspect to learn what the symbol does, what it accepts, and what it returns, based on its c…

No input schema was published for this tool.

3 of 10 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server that teaches any agent the AIDE methodology through tool descriptions and progressive disclosure tooling

Keywords
mcpaideprogressive-disclosureai-agentsspec-documents
Alternatives
Comparing tool surfaces…

Tools exposed

10 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-11 — observed resolution, not a publisher declaration.

60 packages resolved · 6 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

45 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+33 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in documents & pdfs