In-depth architectural comparison of the Bright Security and Vorim MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Bright Security
Security · Remote HTTP/SSE
Quality: 52/100 (Good) | Auth: No auth required
Vorim MCP Server
Security · Local stdio
Quality: 60/100 (Good) | Auth: API Key required
Verdict Summary: Choose Bright Security if you need specialized Security tools running via a hosted cloud SSE transport. Choose Vorim MCP Server if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Bright Security when:
You need dedicated capabilities in the Security domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
List all projects accessible to your API key. Use this to find project IDs needed for other operations.
runDiscovery
Discover API endpoints using crawling (`crawlerUrls`) or API definitions (`fileId` from `uploadApiDefinition`). Before running, check if the project already has entrypoints with `listEntrypoints`. For private/local targets, specify a connected repeater via `repeaters`.
getDiscoveryStatus
Get the current status of a discovery run.
listDiscoveries
List discovery history for a project. View past discovery runs or monitor ongoing endpoint discovery.
uploadApiDefinition
Upload an API definition file (OpenAPI/Swagger) by URL or content. Returns a file ID to reference in discovery runs.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Bright Security is categorized under Security and uses a remote streaming HTTP/SSE transport. In contrast, Vorim MCP Server belongs to Security using local stdio subprocess. Select Bright Security when you need capabilities focused on security and Vorim MCP Server when you require tools for security.
List discovered API endpoints/URLs for a project. Use this to select entrypoints for scans or evaluate attack surface coverage. Supports filtering by HTTP method, status, and text search.
getEntrypoint
Get detailed information about a specific entrypoint by ID, including headers, body, and configuration.
addEntrypoint
Add a new entrypoint to a project. Entrypoints define HTTP requests (method, URL, headers, body) that can be used for security scanning.
editEntrypoint
Update an existing entrypoint. Modify the HTTP request definition, authentication, or repeater settings.
runScan
Start a security scan against selected entrypoints. Supports targeting specific entrypoints by ID or by status (e.g., `new`, `changed`, `vulnerable`). Configure which tests to run or use a scan template. For private/local targets, specify a connected repeater.
getScanStatus
Get the current status of a running scan.
listScans
List scan history for a project. View past scan results or check the status of multiple ongoing scans.
+8 more tools listed on main page
Vorim MCP Server Tools (19)
vorim_ping
Check API health and connectivity
vorim_register_agent
Register a new agent with Ed25519 cryptographic identity
vorim_register_ephemeral
Register a `did:key` ephemeral agent with TTL
vorim_get_agent
Get agent details by ID
vorim_list_agents
List all agents with pagination and filtering
vorim_update_agent
Update agent metadata (name, description, status)
vorim_revoke_agent
Permanently revoke an agent
vorim_check_permission
Check if agent has a permission scope (sub-5ms)
vorim_grant_permission
Grant a permission with optional expiry and rate limits