Veroq MCP Server
veroq-mcp
npm
v2.1.0
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
The verified intelligence layer for AI agents — 62 MCP tools, multi-agent swarm, enterprise safety
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 5 = 95. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 0
Tools 52
Each tool and what it can reach — statically extracted from the published source.
veroq_crawlingests untrusted inputveroq_web_searchingests untrusted inputveroq_alertsno sensitive capabilityveroq_analystsno sensitive capabilityveroq_askno sensitive capabilityveroq_briefno sensitive capabilityveroq_candlesno sensitive capabilityveroq_commoditiesno sensitive capabilityveroq_compareno sensitive capabilityveroq_congressno sensitive capability
Show 42 more tools ↓
veroq_contradictionsno sensitive capabilityveroq_cryptono sensitive capabilityveroq_crypto_chartno sensitive capabilityveroq_defino sensitive capabilityveroq_defi_protocolno sensitive capabilityveroq_diffno sensitive capabilityveroq_earningsno sensitive capabilityveroq_economyno sensitive capabilityveroq_economy_indicatorno sensitive capabilityveroq_entitiesno sensitive capabilityveroq_eventsno sensitive capabilityveroq_extractno sensitive capabilityveroq_feedno sensitive capabilityveroq_filingsno sensitive capabilityveroq_forecastno sensitive capabilityveroq_forexno sensitive capabilityveroq_fullno sensitive capabilityveroq_generate_reportno sensitive capabilityveroq_get_reportno sensitive capabilityveroq_insiderno sensitive capabilityveroq_institutionsno sensitive capabilityveroq_ipo_calendarno sensitive capabilityveroq_market_moversno sensitive capabilityveroq_market_summaryno sensitive capabilityveroq_portfolio_feedno sensitive capabilityveroq_researchno sensitive capabilityveroq_run_agentno sensitive capabilityveroq_screenerno sensitive capabilityveroq_screener_presetsno sensitive capabilityveroq_searchno sensitive capabilityveroq_search_suggestno sensitive capabilityveroq_sectorsno sensitive capabilityveroq_social_sentimentno sensitive capabilityveroq_social_trendingno sensitive capabilityveroq_technicalsno sensitive capabilityveroq_ticker_analysisno sensitive capabilityveroq_ticker_newsno sensitive capabilityveroq_ticker_priceno sensitive capabilityveroq_ticker_scoreno sensitive capabilityveroq_timelineno sensitive capabilityveroq_trendingno sensitive capabilityveroq_verifyno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (52 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v2.1.0 latest |
A 95/100 | 0 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan veroq-mcp --onlineMore in AI & Agents
Authenticated MCP transport with HTTP Signatures for AAuth agents
Local-first MCP server for parallel AI coding agents to claim file ownership before edits, preventing stomping on each other in the same worktree.
Agent-agnostic intercommunication system — sessions, messaging, channels, shared state, and real-time events
MCP server for AI agent task communication and delegation with diagnostic lifecycle visibility
Programmatic add/link/unlink for MCP servers across 23 AI coding agents (Claude Code, Claude Desktop, Cursor, VS Code, Codex, Gemini CLI, Zed, Cline, OpenCode, Goose, Kiro, Windsurf, and more). Functional API with dry-run support.
MCP server layer exposing agent-mesh orchestrator as an MCP agent