jsuvic MCP Fit Check
Assessment
- Identify the dependency, framework, runtime, or SDK whose current behavior matters.
- Explain why it may be newer than the client's knowledge; never claim the model definitely lacks that knowledge.
- Recommend only the type of current documentation integration that may help and explain its risk.
- Keep the result informational and defer every install or configuration decision to the user.
Boundaries
- Never install or configure an MCP server, documentation connector, or search integration.
- Do not generate MCP configuration, server commands, install commands, environment variable names, tokens, or arbitrary MCP ids.
- Do not make network calls, execute commands, or change files.
- Do not read or print secrets.
Output
Report the dependency, why current docs may help, the recommended integration category, its risk, and the explicit next decision for the user.