Vexar-MCP
Security, schema and token-cost checks for MCP servers and AI agent tools. Static analysis that never runs your code, with policy gates for CI, SARIF, and a deliberate 'n/a' when a scan could not read your files.
Description supplied by the publisher; it is a claim, not verified evidence.
- Name
- github:RANJITHROSAN17/Vexar-MCP
- Listed in
- GitHub
- Publisher
- @ranjithrosan17
- Published
- 2026-10-26
- License
- MIT
- Evidence
- Listed only, not analyzed yet
Source: https://github.com/ranjithrosan17/vexar-mcp
What a full analysis of Vexar-MCP checks
Not checked yet. About 60 tools are analyzed every hour; each check links to its source when it runs:
- Publisher identity: not checked yet
- Repository ownership: not checked yet
- Organization verification: not checked yet
- Artifact provenance: not checked yet
- Source availability: not checked yet
- Version evidence: not checked yet
- Known vulnerabilities: not checked yet
- Install scripts: not checked yet
- Maintenance: not checked yet
- License: not checked yet
Before you install it
- Open the repository and confirm the account is the one you expect: look-alike names are common.
- Read what it asks for: files, accounts, network access and credentials it needs.
- Prefer a version from a verified publisher when one exists.