Oldweb Diagnostics vs Deliveriq MCP
A side-by-side look at the Oldweb Diagnostics and Deliveriq MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
O
Oldweb DiagnosticsCommunicationPublic DNS, HTTPS and deployment checks, plus offline email header and delivery-log tracing.36FairAuth: no auth requiredVerdict: choose Oldweb Diagnostics for communication work; choose Deliveriq MCP for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
OChoose Oldweb Diagnostics when
- You need dedicated capabilities in the Communication domain.
- Its auth model fits you: No auth required.
Choose Deliveriq MCP when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
DELIVERIQ_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | O Oldweb Diagnostics | |
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 36/100 · Fair | 41/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | Freemium |
| Required env vars | None listed | DELIVERIQ_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Oldweb Diagnostics | View Deliveriq MCP |
Tools & capabilities
Oldweb Diagnostics tools
No tool names declared yet. Check the project README from the listing page.
Deliveriq 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.
Oldweb Diagnostics
No confirmed install command for Oldweb Diagnostics yet — follow the setup steps linked from its listing page rather than a guessed package name.
Deliveriq MCP
{
"mcpServers": {
"deliveriq-mcp": {
"command": "npx",
"args": [
"-y",
"@deliveriq/mcp"
],
"env": {
"DELIVERIQ_API_KEY": "YOUR_DELIVERIQ_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Oldweb Diagnostics is categorized under Communication and uses an install path we have not confirmed yet. Deliveriq MCP belongs to Communication and uses a local stdio subprocess. Pick Oldweb Diagnostics for communication work and Deliveriq 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. Oldweb Diagnostics has no confirmed install command yet — follow its own setup instructions.
Oldweb Diagnostics is listed as free. Auth: no auth required. Deliveriq MCP is listed as freemium — a free tier with paid plans. Auth: api key required. 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 oldweb-diagnostics and deliveriq-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Oldweb Diagnostics has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Deliveriq MCP has 41/100 (Fair) with 2 views, 0 installs and 1 GitHub stars.