Vedha JSON MCP
Related Servers
Alternatives to Vedha JSON MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables read-only inspection of ad-bid recommendations, scenario analysis, and explanation of threshold decisions using synthetic fixtures, without requiring live ad accounts or credentials.-
- FlicenseAqualityBmaintenanceEnables local, read-only viewing of brokerage accounts, holdings, and transactions using fixture data without real credentials.3-
- AlicenseNot gradedqualityBmaintenanceEnables local, read-only checks of financial disclosure claims against fixed research snapshots, including cutoff queries, operating metric scope, cash-bridge arithmetic, claim tracing, and replayable evidence packets.MIT
- AlicenseNot gradedqualityBmaintenanceEnables users to rehearse venue visits, compare operational changes, and draft factual visitor briefs through four read-only tools over Streamable HTTP, with a browser workbench for inspecting requests and responses.MIT
- AlicenseNot gradedqualityBmaintenanceProvides read-only search and context-pack creation over a local source library, letting AI assistants retrieve relevant excerpts and audit cited quotations.20MIT
- AlicenseNot gradedqualityBmaintenanceEnables local static analysis of deployed AI model artifacts over MCP, exposing audit, diff, capabilities, and rule-explanation tools without uploading model bytes.199 npm2Apache 2.0
TDQS
Scored across 5 tools
Each tool targets a distinct operation: listing scope, reading a canvas, diagnosing a single canvas, composing a cross-canvas review, and explaining prior results. The descriptions reinforce boundaries, especially between vedha_get_diagnosis and vedha_get_atlas_review.
All tools follow a clear vedha_<verb>_<noun> pattern, with vedha_get_* for resource retrieval and vedha_list_* for enumerating contexts. The naming is uniform and predictable.
Five tools is well-scoped for this server's read-only, explanation-oriented purpose. Each tool covers a distinct aspect of the domain without redundancy or unnecessary bulk.
The tool surface covers the full workflow: scoping, single-canvas reading, single-canvas diagnosis, cross-canvas review, and audit of prior answers. There are no obvious dead ends or significant missing operations for the stated domain.