Tendem MCP server vs Toolcallwitness MCP
A side-by-side look at the Tendem MCP server and Toolcallwitness MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Tendem MCP server for developer tools work over a hosted endpoint; choose Toolcallwitness MCP for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Tendem MCP server when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
Choose Toolcallwitness MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
create_witness_receipt, check_approval_rule, summarize_risk_timeline.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 45/100 · Fair | 44/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 102 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 4 |
| Full listing | View Tendem MCP server | View Toolcallwitness MCP |
Tools & capabilities
Tendem MCP server tools
No tool names declared yet. Check the project README from the listing page.
Toolcallwitness MCP tools 4
create_witness_receiptcheck_approval_rulesummarize_risk_timelineexport_audit_receipt
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.
Tendem MCP server
{
"mcpServers": {
"tendem-mcp-server": {
"url": "https://mcp.tendem.ai/mcp"
}
}
}
Toolcallwitness MCP
{
"mcpServers": {
"toolcallwitness-mcp": {
"url": "https://toolcallwitness.clauxel.com/mcp"
}
}
}
Frequently asked questions
Tendem MCP server is categorized under Developer Tools and uses a remote HTTP/SSE transport. Toolcallwitness MCP belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Tendem MCP server for developer tools work and Toolcallwitness MCP 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.
Tendem MCP server has no declared pricing — check the project's own site. Toolcallwitness 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 tendem-mcp-server and toolcallwitness-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Tendem MCP server has a quality signal of 45/100 (Fair) with 0 views, 0 installs and 102 GitHub stars. Toolcallwitness MCP has 44/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.