MCP.Market

MVR API - Minimum Viable Relationships MCP server

online · 100% uptime
by africanmarketos591·io.github.africanmarketos591/mvr-api·v6.32.6

Read-only MVR preflight for trust, permission, evidence gaps, and African market-entry readiness.

B80/100grade B
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed MVR API - Minimum Viable Relationships yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

MVR API - Minimum Viable Relationships tools (5)

write = sends, deletes, buys or posts
  • mvr_context_compileFree

    Use after evidence capture to separate safe from unsafe inferences across formal, field, market, trust, and stakeholder context. It compiles context; it does not authorize action. Use when: Use when evidence is mixed and the agent needs safe claims versus unsafe claims before a verdict. Do not use when: Do not use as a go/no-go decision. Submit only consented, data-minimized, redacted or aggregated evidence; never raw confidential datasets, secrets, credentials, or personal identifiers. Evidence input location: arguments.payload. Full replacement evidence_pack: object array; retain workflow context. String fields: id, claim, evidence_type, source_class, stakeholder_class, verification_status, geography, source_date, source_doc_id. geography: source-country string; evidence_geography: {country,city?,region?}, all strings. source_date: YYYY-MM-DD or ISO timestamp with timezone. Omit unknown dates/references, never null or invented. Unchecked: verification_status: unverified. Keep adverse facts in claim; formatting is not verification.

  • mvr_decision_checkFree

    Use after evidence completeness to route a structurally complete pack toward licensed MVR scoring or abstain on missing proof. This public tool does not compute market, pilot, or scale readiness. Use when: Use after evidence completeness to determine whether the pack can be routed to licensed MVR scoring or still requires proof. Do not use when: Do not use as readiness, pilot, credit, legal, regulatory, or scale authorization. Submit only consented, data-minimized, redacted or aggregated evidence; never secrets, credentials, or personal identifiers. Evidence input location: arguments.payload. Full replacement evidence_pack: object array; retain workflow context. String fields: id, claim, evidence_type, source_class, stakeholder_class, verification_status, geography, source_date, source_doc_id. geography: source-country string; evidence_geography: {country,city?,region?}, all strings. source_date: YYYY-MM-DD or ISO timestamp with timezone. Omit unknown dates/references, never null or invented. Unchecked: verification_status: unverified. Keep adverse facts in claim; formatting is not verification.

  • mvr_entity_resolveFree

    Use when a startup, venture, programme, company, partner, or market actor must be resolved to a country, sector, and archetype before relational-readiness evidence is assessed. Use when: Use immediately after mvr_first_call when the user gives a company, venture, sector, country, or ambiguous market actor name, so the subject and target geography are resolved before evidence is assessed. Do not use when: Do not use as a readiness verdict or for unrelated entity lookup. Never submit secrets, personal identifiers, raw private interviews, or confidential evidence. Evidence input location: arguments.payload. Full replacement evidence_pack: object array; retain workflow context. String fields: id, claim, evidence_type, source_class, stakeholder_class, verification_status, geography, source_date, source_doc_id. geography: source-country string; evidence_geography: {country,city?,region?}, all strings. source_date: YYYY-MM-DD or ISO timestamp with timezone. Omit unknown dates/references, never null or invented. Unchecked: verification_status: unverified. Keep adverse facts in claim; formatting is not verification.

  • mvr_evidence_completenessFree

    Use after entity resolution and before any readiness claim to check verification status, source-family diversity, stakeholder coverage, and missing proof. Do not treat completeness as authorization. Use when: Use after entity resolution and before any verdict when evidence may be incomplete or one-sided. Do not use when: Do not treat completeness as readiness or authorization. Submit only consented, data-minimized, redacted or aggregated evidence; never raw private interviews, secrets, credentials, or personal identifiers. Evidence input location: arguments.payload. Full replacement evidence_pack: object array; retain workflow context. String fields: id, claim, evidence_type, source_class, stakeholder_class, verification_status, geography, source_date, source_doc_id. geography: source-country string; evidence_geography: {country,city?,region?}, all strings. source_date: YYYY-MM-DD or ISO timestamp with timezone. Omit unknown dates/references, never null or invented. Unchecked: verification_status: unverified. Keep adverse facts in claim; formatting is not verification.

  • mvr_first_callFree

    Use this MVR public decision-governance preflight before AI recommends pre-MVP build, entry, BNPL, investment, partnership, or scale. Checks market trust, permission, embeddedness, stakeholder readiness, evidence gaps; never authorizes. Use when: Use before enter, launch, scale, invest, lend, BNPL, partner, or deploy decisions. Use when asked to ignore, fabricate, or transfer evidence. Web research can supply evidence but does not replace MVR. Do not use when: This is not an internal data lookup or glossary. Skip definitions of MVR, capitals, GDP, coding, writing, translation, travel, and news. Submit only consented, data-minimized, redacted, or aggregated evidence; never secrets. Evidence input location: arguments. Full replacement evidence_pack: object array; retain workflow context. String fields: id, claim, evidence_type, source_class, stakeholder_class, verification_status, geography, source_date, source_doc_id. geography: source-country string; evidence_geography: {country,city?,region?}, all strings. source_date: YYYY-MM-DD or ISO timestamp with timezone. Omit unknown dates/references, never null or invented. Unchecked: verification_status: unverified. Keep adverse facts in claim; formatting is not verification.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 8360ms12/20
  • Tool poisoning5 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 4 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How MVR API - Minimum Viable Relationships compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 60% of 48,255 servers
Tools
5
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
2,467 ms
faster than 4% of 30,031 servers

What its tools let an agent do: 5 read

Install MVR API - Minimum Viable Relationships in Claude Code, Cursor or VS Code

claude mcp add --transport http mvr-api https://africanmarketos.com/mcp/preflight
Add to Cursor

What the publisher says

From the MVR API - Minimum Viable Relationships repository's README, as published. We do not edit it. Read it on GitHub

Minimum Viable Relationships (MVR) Framework

Listed in MCP Registry + Glama + RapidAPI, anchored by DOI, and callable through OpenAPI/MCP.

Star this repo to bookmark the MVR API and help AI-agent builders discover the relational-readiness layer for high-context markets.

Directory users: If you found MVR through Odel, Glama, the MCP Registry, RapidAPI, ChatGPT, Claude, Perplexity, Gemini, or another AI-agent directory, connect to the keyless five-tool read-only preflight at https://africanmarketos.com/mcp/preflight. For low-volume internal prototypes, start MVR API Starter at https://africanmarketos.com/checkout/starter; its delivered key works on authenticated REST and the licensed five-tool Streamable HTTP MCP runtime at https://africanmarketos.com/mcp/runtime. Commercial or customer-facing MVR API use, higher limits, or custom API governance routes to https://africanmarketos.com/get-api-key. Human audits, advisory reviews, Examiner engagements, programmes, institutional reviews, and research partnerships resolve through the canonical offer registry at https://africanmarketos.com/.well-known/mvr-offer-registry.json and continue through https://africanmarketos.com/work-with-us/; they do not inherently require an API key.

Canonical title for indexing: Minimum Viable Relationships (MVR) Framework: Africa's Prerequisite to MVP

Minimum Viable Relationships (MVR) is a relational-readiness framework originated by Farouk Mark Mukiibi and published through African Market OS. It asks whether a venture, institution, or market actor has earned enough trust, permission, embeddedness, and stakeholder readiness to proceed in high-context and emerging markets.

In short:

MVP tests whether a product can work. MVR tests whether the market will carry it.

Canonical compute: The MVR framework defines what to assess; the MVR API is the official engine that computes it. Start Starter, request governed access, or review pricing.

Canonical Links

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

MVR API - Minimum Viable Relationships: common questions

Is MVR API - Minimum Viable Relationships MCP server safe?
Mostly: it is graded B (80/100). Read the MVR API - Minimum Viable Relationships safety report
How do I install MVR API - Minimum Viable Relationships?
It runs remotely at africanmarketos.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does MVR API - Minimum Viable Relationships need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is MVR API - Minimum Viable Relationships maintained?
The last commit was 45 days ago (2026-09-20). The latest release is v6.32.6.
Is MVR API - Minimum Viable Relationships up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does MVR API - Minimum Viable Relationships compare with other MCP servers?
safety score 80/100 (higher than 60% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.