MVR API - Minimum Viable Relationships MCP Server

by africanmarketos591 Your server? Claim it

answering

MVR API - Minimum Viable Relationships is answering right now. Last checked 11 min ago. It exposes 5 tools. Last commit 3 Nov 2026.

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

Uptime history 91 days of history · worst day 54%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

1268 ms

Response time

average over 24h

Stars

last commit 3 Nov 2026

What changed 77

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 6 September 2026. No other catalogue keeps this.

21 Oct 5 tools changed the parameters they ask for mvr_context_compile, mvr_decision_check, mvr_entity_resolve and 2 more

21 Oct 5 tool descriptions were rewritten mvr_context_compile, mvr_decision_check, mvr_entity_resolve and 2 more

20 Oct 5 tools changed the parameters they ask for mvr_context_compile, mvr_decision_check, mvr_entity_resolve and 2 more

19 Oct 5 tools changed the parameters they ask for mvr_context_compile, mvr_decision_check, mvr_entity_resolve and 2 more

18 Oct 5 tools changed the parameters they ask for mvr_context_compile, mvr_decision_check, mvr_entity_resolve and 2 more

8 Oct 5 tools changed the parameters they ask for10 times that day mvr_context_compile, mvr_decision_check, mvr_entity_resolve and 2 more

8 Oct 5 tool descriptions were rewritten mvr_context_compile, mvr_decision_check, mvr_entity_resolve and 2 more

7 Oct 5 tool descriptions were rewritten mvr_context_compile, mvr_decision_check, mvr_entity_resolve and 2 more

7 Oct 5 tools changed the parameters they ask for mvr_context_compile, mvr_decision_check, mvr_entity_resolve and 2 more

13 Sep 5 tool descriptions were rewritten mvr_context_compile, mvr_decision_check, mvr_entity_resolve and 2 more

and 27 more, back to 6 September 2026

What the code does

We read the source, 4 d ago · tools taken from the live server · rules 995398eba69f

Evidence

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

Claims read-only, but the code runs commands release-evidence/2026-10-24-hosted-review/verify.mjs:18, release-evidence/2026-10-24-review-workbench/verify.mjs:9, conformance/receipt-key/ceremony-module.mjs:48

const test=spawnSync(process.execPath,[fileURLToPath(new URL('examples/decision-review-workbench/test.mjs',root))],{encoding:'utf8',windowsHide:true,timeout:60000});assert.equal(test.status,0,test.stderr);assert.equal(JSON.parse(test.stdout).exhaustive_oracle_cases,6912);

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

A line of code looks encrypted conformance/decision-state/decision.mjs:66

  need(object(a)&&Object.keys(a).sort().join(',')==='model,model_version,output_sha256,prompt_sha256,provider'&&text(a.provider,100)&&text(a.model,120)&&text(a.model_version,120)&&HEX.test(a.prompt_sha256||'')&&HEX.test(a.output_sha256||''),'INTERPRETATION_ATTRIBUTION_INVALID');

Runs an external command release-evidence/2026-10-24-hosted-review/verify.mjs:18, release-evidence/2026-10-24-review-workbench/verify.mjs:9, conformance/receipt-key/ceremony-module.mjs:48

const test=spawnSync(process.execPath,[fileURLToPath(new URL('examples/decision-review-workbench/test.mjs',root))],{encoding:'utf8',windowsHide:true,timeout:60000});assert.equal(test.status,0,test.stderr);assert.equal(JSON.parse(test.stdout).exhaustive_oracle_cases,6912);

Builds a file path from a variable conformance/r9-qualification/run-live.mjs:19

const read = p => JSON.parse(fs.readFileSync(path.join(here, '..', p), 'utf8'));

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

We found things in this code

Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch MVR API - Minimum Viable Relationships and you get told the day something new turns up.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://africanmarketos.com/mcp/preflight

~/.codex/config.toml

[mcp_servers.mvr-api]
url = "https://africanmarketos.com/mcp/preflight"

.cursor/mcp.json

{
  "mcpServers": {
    "mvr-api": {
      "url": "https://africanmarketos.com/mcp/preflight"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "mvr-api": {
      "type": "http",
      "url": "https://africanmarketos.com/mcp/preflight"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

mvr

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. Evidence input location: arguments.payload. evidence_pack: object array. String fields: evidence_type, source_class, stakeholder_class, verification_status, source_date, source_doc_id. geography: string/object; evidence_geography: object; district: nonblank string; districts: nonblank strings array. source_date/freshness_date: YYYY, YYYY-MM, YYYY-MM-DD or ISO timestamp with timezone. source_date_range: {earliest,latest}, same-precision ordered bounds within supplied dates. analysis_date stays exact. Intervals have age_days:null and age_days_min/max; unresolved window/future overlap excludes coverage. Omit unknown dates/references, never null or invented. verification_status: unverified if unchecked. *_role: original_source_record, independent_evaluation or human_attestation; else ARTIFACT_ROLE_NOT_SOURCE_EVIDENCE. collection_context + provenance_ledger: see schema/feedback. Keep adverse facts; never relabel to pass.

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. Evidence input location: arguments.payload. evidence_pack: object array. String fields: evidence_type, source_class, stakeholder_class, verification_status, source_date, source_doc_id. geography: string/object; evidence_geography: object; district: nonblank string; districts: nonblank strings array. source_date/freshness_date: YYYY, YYYY-MM, YYYY-MM-DD or ISO timestamp with timezone. source_date_range: {earliest,latest}, same-precision ordered bounds within supplied dates. analysis_date stays exact. Intervals have age_days:null and age_days_min/max; unresolved window/future overlap excludes coverage. Omit unknown dates/references, never null or invented. verification_status: unverified if unchecked. *_role: original_source_record, independent_evaluation or human_attestation; else ARTIFACT_ROLE_NOT_SOURCE_EVIDENCE. collection_context + provenance_ledger: see schema/feedback. Keep adverse facts; never relabel to pass.

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 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. evidence_pack: object array. String fields: evidence_type, source_class, stakeholder_class, verification_status, source_date, source_doc_id. geography: string/object; evidence_geography: object; district: nonblank string; districts: nonblank strings array. source_date/freshness_date: YYYY, YYYY-MM, YYYY-MM-DD or ISO timestamp with timezone. source_date_range: {earliest,latest}, same-precision ordered bounds within supplied dates. analysis_date stays exact. Intervals have age_days:null and age_days_min/max; unresolved window/future overlap excludes coverage. Omit unknown dates/references, never null or invented. verification_status: unverified if unchecked. *_role: original_source_record, independent_evaluation or human_attestation; else ARTIFACT_ROLE_NOT_SOURCE_EVIDENCE. collection_context + provenance_ledger: see schema/feedback. Keep adverse facts; never relabel to pass.

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. Evidence input location: arguments.payload. evidence_pack: object array. String fields: evidence_type, source_class, stakeholder_class, verification_status, source_date, source_doc_id. geography: string/object; evidence_geography: object; district: nonblank string; districts: nonblank strings array. source_date/freshness_date: YYYY, YYYY-MM, YYYY-MM-DD or ISO timestamp with timezone. source_date_range: {earliest,latest}, same-precision ordered bounds within supplied dates. analysis_date stays exact. Intervals have age_days:null and age_days_min/max; unresolved window/future overlap excludes coverage. Omit unknown dates/references, never null or invented. verification_status: unverified if unchecked. *_role: original_source_record, independent_evaluation or human_attestation; else ARTIFACT_ROLE_NOT_SOURCE_EVIDENCE. collection_context + provenance_ledger: see schema/feedback. Keep adverse facts; never relabel to pass.

mvr_first_call

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. evidence_pack: object array. String fields: evidence_type, source_class, stakeholder_class, verification_status, source_date, source_doc_id. geography: string/object; evidence_geography: object; district: nonblank string; districts: nonblank strings array. source_date/freshness_date: YYYY, YYYY-MM, YYYY-MM-DD or ISO timestamp with timezone. source_date_range: {earliest,latest}, same-precision ordered bounds within supplied dates. analysis_date stays exact. Intervals have age_days:null and age_days_min/max; unresolved window/future overlap excludes coverage. Omit unknown dates/references, never null or invented. verification_status: unverified if unchecked. *_role: original_source_record, independent_evaluation or human_attestation; else ARTIFACT_ROLE_NOT_SOURCE_EVIDENCE. collection_context + provenance_ledger: see schema/feedback. Keep adverse facts; never relabel to pass.

Endpoints

URL	Transport	State	Latency	Checked
https://africanmarketos.com/mcp/preflight	streamable-http	answering	1276 ms	11 min ago

Alternatives to MVR API - Minimum Viable Relationships

same job, measured the same way

RegEvidenceHub Waste

by changhuliu

RegEvidenceHub Waste: England waste registration, DWT readiness and permit-change preflight.

9 tools answering

AETHER Machine Relationship Mesh

by visionastro48-dev

Machine-native relationship mesh for discovery, help, evidence, and earned trust.

5 tools answering

npx-vibe

by devrajsinh-jhala

Read-only npm package and project dependency preflight tools for AI applications.

75 installs/wk local only

ShadowGraph Market Intelligence

by floot-shadowgraph-live

Global evidence-ranked relationship intelligence for AI agents via MPP.

11 tools answering

GuestKit

by zyvorai

Read-only evidence and boot-readiness tools for one VM disk image, offline.

local only

MCP Us Business Data

by avabuildsdata

Official-source US business, permit, and WHOIS evidence via read-only MCP tools.

answering

x402 Pay — USDC API Payment Helper

by scriptmasterlabs

Pay for APIs with USDC. Read-only x402 payment discovery, verification, evidence, and status.

5 tools answering

Microsoft 365 Admin

by okapi-ca

Microsoft 365 administration via Graph API application permissions (read-only by default).

91 installs/wk local only

MVR API - Minimum Viable Relationships — questions

Answers built from our own checks of this server.

What can MVR API - Minimum Viable Relationships do?

It exposes 5 tools, read directly from the server on our last check. Among them: mvr_context_compile, mvr_decision_check, mvr_entity_resolve, mvr_evidence_completeness, mvr_first_call. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is MVR API - Minimum Viable Relationships working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 1268 ms. The bar chart above shows every period we have measured.

How do I connect MVR API - Minimum Viable Relationships?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does MVR API - Minimum Viable Relationships need an API key?

No. MVR API - Minimum Viable Relationships completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is MVR API - Minimum Viable Relationships?

It answers our handshake in 1268 ms on average, which is faster than 2% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is MVR API - Minimum Viable Relationships open source?

We cannot say either way: written in HTML and 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.