Vexor vs SCRIPTMASTERLABS — Pr… — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Vexor vs SCRIPTMASTERLABS — Provider Trust
In-depth architectural comparison of the Vexor and SCRIPTMASTERLABS — Provider Trust 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
Vexor
Developer Tools · Local stdio
Quality: 61/100 (Good) | Auth: API Key required
SCRIPTMASTERLABS — Provider Trust
Developer Tools · Remote HTTP/SSE
Quality: 76/100 (Great) | Auth: No auth required
Verdict Summary: Choose Vexor if you need specialized Developer Tools tools running via a local process. Choose SCRIPTMASTERLABS — Provider Trust if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Vexor when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: VEXOR_API_KEY, VEXOR_CONFIG_JSON.
Primary tools included: Configurable embedding providers (OpenAI, Gemini, Voyage, local models), AST-aware code chunking for improved indexing, Optional reranking of search results.
A semantic search engine for files and code — find files by describing what they do, not their names. Local reusable indexes, configurable embedding providers (OpenAI, Gemini, Voyage, any OpenAI-compatible API, or fully offline local models), AST-aware code chunking, optional reranking. uvx vexor mcp or pip install vexor.
Read-only Universal Trust Passport MCP for verifying public provider evidence across MCP, A2A, API and x402: runtime reachability, payment metadata, settlement evidence and trust signals.
Tools & Capabilities Breakdown
Vexor Tools (6)
Configurable embedding providers (OpenAI, Gemini, Voyage, local models)
AST-aware code chunking for improved indexing
Optional reranking of search results
Reusable local indexes with auto-indexing on first search
Exposes CLI, Python API, and MCP stdio server
Supports in-memory search without cache
SCRIPTMASTERLABS — Provider Trust Tools (10)
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).
Vexor is categorized under Developer Tools and uses a local stdio subprocess. In contrast, SCRIPTMASTERLABS — Provider Trust belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Vexor when you need capabilities focused on developer tools and SCRIPTMASTERLABS — Provider Trust when you require tools for developer tools.
Search the live SCRIPTMASTERLABS SqueezeOS capability inventory. This tool does not purchase, sign, settle, or execute paid capabilities.
recommend_capability
Return the best matching live SqueezeOS capabilities for a natural-language need, including current endpoint and payment metadata without authorizing spend.
inspect_capability
Inspect one live SqueezeOS capability by sml_id and return current metadata and optional liveness evidence.
compare_capabilities
Compare two to five live capabilities using current metadata without fabricating a composite score.
verify_provider_trust
Run the free read-only SML Universal Trust Passport against a public HTTPS provider URL. It observes live A2A, MCP, ERC-8004, runtime, and payment-metadata evidence; it never forwards credentials, signs, spends, settles, or executes the provider capability.
capability_manifest
Return the current SqueezeOS machine capability manifest derived from the running service.
x402_contract
Read the public SqueezeOS x402 discovery contract. This tool only reports payment terms and never signs, submits, or settles a payment.
x402_readiness
Read the live SqueezeOS x402 readiness surface. No payment is initiated.
x402_evidence
Read public settlement evidence recorded by the canonical SqueezeOS rail. A challenge or signature is not treated as settlement proof.
system_status
Read the live SqueezeOS status endpoint without synthesizing health claims.