Most wanted — KnownFix MCP Resource
Most wanted
is one of 19 resources on the
KnownFix
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Most wanted from your client
- Claude Code KnownFix Resource/Most wanted run in your project directory
- Claude Desktop KnownFix Resource/Most wanted ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor KnownFix Resource/Most wanted ~/.cursor/mcp.json
- VS Code KnownFix Resource/Most wanted .vscode/mcp.json
- Zed KnownFix Resource/Most wanted ~/.config/zed/settings.json
- Windsurf KnownFix Resource/Most wanted ~/.codeium/windsurf/mcp_config.json
- Cline KnownFix Resource/Most wanted ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI KnownFix Resource/Most wanted ~/.gemini/settings.json
- Grok KnownFix Resource/Most wanted .mcp.json (in your project root)
- ChatGPT KnownFix Resource/Most wanted Settings → Connectors → Advanced → Developer mode
- Claude.ai KnownFix Resource/Most wanted Settings → Connectors → Add custom connector
- LangChain KnownFix Resource/Most wanted pip install langchain-mcp-adapters
Other resources on this server
- Fix catalog
- Skill outlines
- Open books
- Professional review services
- Fix __dirname is not defined in ES module scope in Node.js
- Fix ERR_UNSUPPORTED_DIR_IMPORT in Node.js ES modules
- OpenZeppelin 5.x fails to compile: Function "mcopy" not found
- node --test with a bare directory argument fails with a nameless failin…
- Probing a dependency via require('X/package.json') throws ERR_PACKAGE_P…
- git push to your own private repo fails with 'repository not found'
- Deno Deploy returns 508 Loop Detected when a deployment fetches its own…
- Deno KV reads empty on new Deno Deploy until you attach a database
- Deno.openKv() throws locally without the --unstable-kv flag
- MCP Registry publish fails 422: description exceeds 100 characters
- MCP Registry publish 401: Invalid or expired Registry JWT token
- Windows: an env var set with setx is missing in the shell that set it
- GitHub Pages serves 404 while the repo and index.html are both intact
- npm exec says the package command is not recognized inside its own sour…
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.