Publishwith.ai vs Scopeblind Gateway
A side-by-side look at the Publishwith.ai and Scopeblind Gateway MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
P
Publishwith.aiSecurityPublish AI reports as managed native links with versions, access control, revocation, and audit.37FairAuth: not declaredVerdict: choose Publishwith.ai for security work; 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?
PChoose Publishwith.ai when
- You need dedicated capabilities in the Security domain.
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 | P Publishwith.ai | |
|---|---|---|
| Category | Security | Security |
| Quality signal | 37/100 · Fair | 52/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | 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 | — | 10 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Publishwith.ai | View Scopeblind Gateway |
Tools & capabilities
Publishwith.ai tools
No tool names declared yet. Check the project README from the listing page.
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.
Publishwith.ai
No confirmed install command for Publishwith.ai yet — follow the setup steps linked from its listing page rather than a guessed package name.
Scopeblind Gateway
{
"mcpServers": {
"tomjwxf-scopeblind-gateway": {
"command": "npx",
"args": [
"-y",
"@scopeblind/passport"
],
"env": {
"INTERNAL_API_KEY": "YOUR_INTERNAL_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Publishwith.ai is categorized under Security and uses an install path we have not confirmed yet. Scopeblind Gateway belongs to Security and uses a local stdio subprocess. Pick Publishwith.ai 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. Publishwith.ai has no confirmed install command yet — follow its own setup instructions.
Publishwith.ai 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 publishwith-ai and tomjwxf-scopeblind-gateway as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Publishwith.ai has a quality signal of 37/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Scopeblind Gateway has 52/100 (Good) with 2 views, 0 installs and 10 GitHub stars.