A side-by-side look at the Dogg World Check and AI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Dogg World Check for developer tools work over a hosted endpoint; choose AI for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Dogg World Check when
You need dedicated capabilities in the Developer Tools domain.
No tool names declared yet. Check the project README from the listing page.
AI tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Dogg World Check is categorized under Developer Tools and uses a remote HTTP/SSE transport. AI belongs to Developer Tools and uses a local stdio subprocess. Pick Dogg World Check for developer tools work and AI for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Dogg World Check has no declared pricing — check the project's own site. AI has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add dogg-world-check and contentrain-ai as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Dogg World Check has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. AI has 53/100 (Good) with 3 views, 0 installs and 6 GitHub stars.