Dvalincode vs Maskbreak
A side-by-side look at the Dvalincode and Maskbreak MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Dvalincode for security work as a local process; choose Maskbreak for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Dvalincode when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
Choose Maskbreak when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
MASKBREAK_API_KEY, SENTINEL_BASE_URL. - You want tools like
lookup_ip, service_status.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 49/100 · Fair | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | MASKBREAK_API_KEYSENTINEL_BASE_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 117 | 2 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View Dvalincode | View Maskbreak |
Tools & capabilities
Dvalincode tools
No tool names declared yet. Check the project README from the listing page.
Maskbreak tools 2
lookup_ipPublic IPv4/IPv6 lookup: `known`, `allow` / `review` / `block`, risk score, and nullable signal/network metadata. Public-feed coverage is limited to cloud hosting and Tor.service_statusMaskbreak API health, uptime, and latency
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.
Dvalincode
{
"mcpServers": {
"dvalincode": {
"command": "npx",
"args": [
"-y",
"dvalincode"
]
}
}
}
Maskbreak
{
"mcpServers": {
"maskbreak": {
"command": "npx",
"args": [
"-y",
"@sentinelsup/mcp"
],
"env": {
"MASKBREAK_API_KEY": "YOUR_MASKBREAK_API_KEY_HERE",
"SENTINEL_BASE_URL": "YOUR_SENTINEL_BASE_URL_HERE"
}
}
}
}
Frequently asked questions
Dvalincode is categorized under Security and uses a local stdio subprocess. Maskbreak belongs to Security and uses a local stdio subprocess. Pick Dvalincode for security work and Maskbreak for security.
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.
Dvalincode has no declared pricing — check the project's own site. Maskbreak 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 dvalincode and maskbreak as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Dvalincode has a quality signal of 49/100 (Fair) with 2 views, 0 installs and 117 GitHub stars. Maskbreak has 56/100 (Good) with 1 views, 0 installs and 2 GitHub stars.