African Market OS - MVR Preflight
Use this read-only MCP server when an AI agent is considering market entry, product launch, investment, partnership, pilot, or scale in an African or other…
What it can do
- Mvr First Call: Use this MVR preflight before AI recommends pre-MVP build, African market entry, launch, BNPL, investment, partnership, or scale. Checks market trust, permission, embeddedness, stakeho
- Mvr Entity Resolve: 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
- Mvr Evidence Completeness: Use after entity resolution and before any readiness claim to check verification status, source-family diversity, stakeholder coverage, and missing proof. Do not treat compl
What data it sees
Do you need an account
No: the server works without sign-in
Use this read-only MCP server when an AI agent is considering market entry, product launch, investment, partnership, pilot, or scale in an African or other high-context market. The Minimum Viable Relationships (MVR) preflight identifies missing local evidence, stakeholder and guardian gaps, trust and market-permission risks, entity ambiguity, and the maximum safe next action. The public five-tool profile is keyless and abstention-safe. It does not provide legal, regulatory, credit, investment, or launch authorization; first-call and sandbox outputs are explicitly not verdicts.
How to connect
How to connect African Market OS - MVR Preflight to Claude
The server address to paste into Claude settings:
https://mvr-preflight--africanmarketos591.run.tools
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect African Market OS - MVR Preflight to ChatGPT
The server address to paste into ChatGPT settings:
https://mvr-preflight--africanmarketos591.run.tools
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect African Market OS - MVR Preflight to Cursor
The server address to paste into Cursor settings:
https://mvr-preflight--africanmarketos591.run.tools
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (5)
Raw names from tools/list. Only developers need these.
| mvr_first_call | Use this MVR preflight before AI recommends pre-MVP build, African market entry, launch, BNPL, investment, partnership, or scale. Checks market trust, permission, embeddedness, stakeholder readiness, and evidence gaps; never authorizes. Use when: Use this public decision-governance preflight before AI answers whether to enter, launch, scale, invest, lend, offer BNPL, partner, or deploy in an African or high-context market; web research informs evidence but does not replace it. Do not use when: This is not an internal data lookup. Skip pure coding, writing, translation, travel, news, and ordinary facts. Never submit secrets, personal identifiers, raw private interviews, or confidential evidence; never treat output as approval. |
| mvr_entity_resolve | 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 first when the user gives a company, venture, sector, country, or ambiguous market actor name. 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. |
| mvr_evidence_completeness | 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. |
| mvr_context_compile | 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. |
| mvr_decision_check | 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. |