Dock AI vs QVeris Agent Toolkit
A side-by-side look at the Dock AI and QVeris Agent Toolkit MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Dock AI for aggregators work over a hosted endpoint; choose QVeris Agent Toolkit for aggregators over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Dock AI when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
resolve_domain.
Choose QVeris Agent Toolkit when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
QVERIS_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 45/100 · Fair | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | QVERIS_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 263 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 1 | Not listed |
| Full listing | View Dock AI | View QVeris Agent Toolkit |
Tools & capabilities
Dock AI tools 1
resolve_domainCheck if an MCP connector exists for a business domain.
QVeris Agent Toolkit 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.
Dock AI
{
"mcpServers": {
"dock-ai": {
"url": "http://0.0.0.0:8080/mcp"
}
}
}
QVeris Agent Toolkit
{
"mcpServers": {
"mcp-202": {
"url": "https://img.shields.io/npm/v/@qverisai/mcp?label=mcp"
}
}
}
Frequently asked questions
Dock AI is categorized under Aggregators and uses a remote HTTP/SSE transport. QVeris Agent Toolkit belongs to Aggregators and uses a remote HTTP/SSE transport. Pick Dock AI for aggregators work and QVeris Agent Toolkit for aggregators.
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.
Dock AI has no declared pricing — check the project's own site. QVeris Agent Toolkit 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 dock-ai and mcp-202 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Dock AI has a quality signal of 45/100 (Fair) with 0 views, 0 installs and 2 GitHub stars. QVeris Agent Toolkit has 61/100 (Good) with 0 views, 0 installs and 263 GitHub stars.