A side-by-side look at the OrionCMD Checks and Winged Guardian MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose OrionCMD Checks for communication work over a hosted endpoint; choose Winged Guardian MCP for communication over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
O
Choose OrionCMD Checks when
You need dedicated capabilities in the Communication domain.
No tool names declared yet. Check the project README from the listing page.
Winged Guardian MCP 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.
OrionCMD Checks is categorized under Communication and uses a remote HTTP/SSE transport. Winged Guardian MCP belongs to Communication and uses a remote HTTP/SSE transport. Pick OrionCMD Checks for communication work and Winged Guardian MCP for communication.
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.
OrionCMD Checks is listed as a paid service. Winged Guardian MCP 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 orioncmd-checks and agent-tools-5 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, OrionCMD Checks has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Winged Guardian MCP has 36/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.