HubVibe Site Audits vs Depwire
A side-by-side look at the HubVibe Site Audits and Depwire MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose HubVibe Site Audits for developer tools work over a hosted endpoint; choose Depwire for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose HubVibe Site Audits when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
HUBVIBE_WALLET_KEY, HUBVIBE_API_KEY.
Choose Depwire when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 37/100 · Fair | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | HUBVIBE_WALLET_KEYHUBVIBE_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 64 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View HubVibe Site Audits | View Depwire |
Tools & capabilities
HubVibe Site Audits tools
No tool names declared yet. Check the project README from the listing page.
Depwire 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.
HubVibe Site Audits
{
"mcpServers": {
"hubvibe-site-audits": {
"url": "https://hubvibe-io.com/mcp"
}
}
}
Depwire
{
"mcpServers": {
"depwire-depwire": {
"command": "npx",
"args": [
"-y",
"depwire-cli"
]
}
}
}
Frequently asked questions
HubVibe Site Audits is categorized under Developer Tools and uses a remote HTTP/SSE transport. Depwire belongs to Developer Tools and uses a local stdio subprocess. Pick HubVibe Site Audits for developer tools work and Depwire 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.
HubVibe Site Audits has no declared pricing — check the project's own site. Depwire is listed as free. Auth: no auth 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 hubvibe-site-audits and depwire-depwire as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, HubVibe Site Audits has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Depwire has 61/100 (Good) with 4 views, 0 installs and 64 GitHub stars.