mcp-schema-server

The server primarily communicates via standard I/O (StdioServerTransport), which limits external network attack surface. Input validation for tools is enforced using AJV against defined `inputSchema` in the manifest, a strong practice. However, error messages returned from handlers include the full `err.message`, which could potentially leak sensitive internal information if handlers are not careful about what they throw. Loading the `manifest.json` via `fs.readFileSync` could theoretically be a path traversal risk if the `manifestPath` input were user-controlled and not properly sanitized, though typical usage (e.g., `path.join(__dirname, "manifest.json")`) mitigates this.