African Market OS - MVR API
Related Servers
Alternatives to African Market OS - MVR API
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to read local business data and request database mutations, while requiring human approval before updates or deletions are executed. It provides read-only tools, approval workflows, and audit logging to prevent autonomous destructive changes.-
- AlicenseAqualityBmaintenanceEnables AI assistants and agents to perform read-only lookups of dated on-record facts about agents, wallets, and endpoints, including evidence levels and history, so they can assess what is known before paying or relying on them.41,092 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to obtain structured, source-backed real-world evidence with provenance, freshness, conflicts, support levels, coverage, unresolved dependencies, and reusable integrity-checked receipts, including French company verification and beta import assessment.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables agents to read and report, and to carry human-authored updates into systems of record after human consent, while structurally preventing autonomous writes of commitments like owners, due dates, or statuses.MIT
- AlicenseAqualityBmaintenanceEnables customer-success teams and AI hosts to inspect account evidence, assess onboarding readiness, assemble unsent bilingual follow-up drafts, and prepare traceable technical handoffs through scoped MCP tools. It preserves source references and distinguishes recorded failures, missing evidence, and possible explanations for human review.8MIT
- AlicenseBqualityBmaintenanceEnables AI agents to conduct local, auditable opportunity discovery by collecting public discussions, tracing claims to exact quotes and source provenance, testing claims with counterevidence, and exporting deterministic evidence packs.471MIT
TDQS
Scored across 5 tools
Each tool serves a distinct step in the MVR pipeline: preflight, entity resolution, evidence checking, context compilation, and routing to scoring. There is no overlap; each has a clear trigger and purpose.
All tools share the mvr_ prefix and follow a verb_noun pattern (first_call, entity_resolve, evidence_completeness, context_compile, decision_check). The naming is uniform and predictable.
With exactly 5 tools, the server is well-scoped for a pre-scoring governance pipeline. Each tool is necessary and the count fits the intended workflow without redundancy.
The toolkit covers the full pre-scoring lifecycle from initial preflight through entity resolution, evidence validation, context synthesis, and decision routing. The only gap is the actual scoring itself, which is intentionally externalized to licensed MVR scoring, so the surface is complete for its stated purpose.