Shipswiftcomponents MCP vs Scopeblind Gateway
A side-by-side look at the Shipswiftcomponents MCP and Scopeblind Gateway MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Shipswiftcomponents MCP for security work over a hosted endpoint; choose Scopeblind Gateway 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 Shipswiftcomponents MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
search_swiftui_component, generate_component_patch, validate_dependency_policy.
Choose Scopeblind Gateway when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
INTERNAL_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 48/100 · Fair | 53/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 | None listed | INTERNAL_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 11 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Shipswiftcomponents MCP | View Scopeblind Gateway |
Tools & capabilities
Shipswiftcomponents MCP tools 4
search_swiftui_componentgenerate_component_patchvalidate_dependency_policyexport_component_receipt
Scopeblind Gateway 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.
Shipswiftcomponents MCP
{
"mcpServers": {
"shipswiftcomponents-mcp": {
"url": "https://shipswiftcomponents.clauxel.com/mcp"
}
}
}
Scopeblind Gateway
{
"mcpServers": {
"tomjwxf-scopeblind-gateway": {
"command": "npx",
"args": [
"-y",
"@scopeblind/passport"
],
"env": {
"INTERNAL_API_KEY": "YOUR_INTERNAL_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Shipswiftcomponents MCP is categorized under Security and uses a remote HTTP/SSE transport. Scopeblind Gateway belongs to Security and uses a local stdio subprocess. Pick Shipswiftcomponents MCP for security work and Scopeblind Gateway 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.
Shipswiftcomponents MCP has no declared pricing — check the project's own site. Scopeblind Gateway 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 shipswiftcomponents-mcp and tomjwxf-scopeblind-gateway as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Shipswiftcomponents MCP has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Scopeblind Gateway has 53/100 (Good) with 4 views, 0 installs and 11 GitHub stars.