QVeris Agent Toolkit vs Toolmesh
A side-by-side look at the QVeris Agent Toolkit and Toolmesh MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose QVeris Agent Toolkit for aggregators work over a hosted endpoint; choose Toolmesh 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 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.
Choose Toolmesh when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: other.
- You have the keys it needs:
TOOLMESH_AUTH_PASSWORD, TOOLMESH_API_KEY, TOOLMESH_AUTH_USER, TOOLMESH_AUTH_PLAN, TOOLMESH_AUTH_ROLES, TOOLMESH_BCRYPT_MAX_CONCURRENT.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 61/100 · Good | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | API key required | other |
| Pricing | Freemium | Free |
| Required env vars | QVERIS_API_KEY | TOOLMESH_AUTH_PASSWORDTOOLMESH_API_KEYTOOLMESH_AUTH_USERTOOLMESH_AUTH_PLANTOOLMESH_AUTH_ROLESTOOLMESH_BCRYPT_MAX_CONCURRENT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 263 | 6 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View QVeris Agent Toolkit | View Toolmesh |
Tools & capabilities
QVeris Agent Toolkit tools
No tool names declared yet. Check the project README from the listing page.
Toolmesh 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.
QVeris Agent Toolkit
{
"mcpServers": {
"mcp-202": {
"url": "https://img.shields.io/npm/v/@qverisai/mcp?label=mcp"
}
}
}
Toolmesh
{
"mcpServers": {
"toolmesh": {
"url": "http://localhost:8123/mcp"
}
}
}
Frequently asked questions
QVeris Agent Toolkit is categorized under Aggregators and uses a remote HTTP/SSE transport. Toolmesh belongs to Aggregators and uses a remote HTTP/SSE transport. Pick QVeris Agent Toolkit for aggregators work and Toolmesh 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.
QVeris Agent Toolkit is listed as freemium — a free tier with paid plans. Auth: api key required. Toolmesh is listed as free. Auth: other. 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 mcp-202 and toolmesh as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, QVeris Agent Toolkit has a quality signal of 61/100 (Good) with 0 views, 0 installs and 263 GitHub stars. Toolmesh has 43/100 (Fair) with 3 views, 0 installs and 6 GitHub stars.