Is MVR API down?

pulsemcp/mvr-api · vv6.32.0

Also listed as glama/africanmarketos591/african-market-os---mvr-api, mcp-registry/io.github.africanmarketos591/mvr-api · primary listing: mcp-registry/io.github.africanmarketos591/mvr-api

healthy
Last checked 2026-10-26 19:43 UTC · handshake 2.6s

As of 2026-10-26 19:43 UTC, MVR API is up with a Glimind reliability score of 76/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 15 outages in 90 days, with a median recovery of 3 minutes.

uptime (30d checks)
99.6%
checks observed
4,657
outages (90d)
15
tools
7

Minimum Viable Relationships API — relational-readiness tools for high-context market decisions in African and emerging markets.

Point your MCP client at this streamable_http endpoint: https://africanmarketos.com/mcp

Agent-readiness: C (74/100)

C (74/100): 1 error(s), 3 warning(s) across 7 tool(s); ~64,105 tokens of tool definitions.
Scores higher than 9% of 15,762 MCP servers Glimind has audited.
Its tool list costs an agent ~64,105 tokens per session — more than 99% of servers.
72 → 74 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions70
Safety hints100
Token cost0
Client compatibility100
Protocol100
Reliability85
Stability20

What to fix (5)

Loading this server's tool list costs an agent ~64,105 tokens before any work — more than 99% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

7 tool definition(s) exceed ~1,200 tokens each (largest: mvr_first_call, ~10,640).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~59,905 tokens every session. How to fix →

Tools: mvr_first_call, mvr_entity_resolve, mvr_african_market_insights, mvr_decision_check, mvr_evidence_completeness and 2 more · saves ~59,905 tokens/session

12 parameter(s) across 2 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: mvr_african_market_insights, mvr_first_call

Handshake + tools/list takes ~3,637 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

In the last 30 days: 0 tool(s) removed and 54 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["pulsemcp/mvr-api"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "pulsemcp/mvr-api"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/pulsemcp%2Fmvr-api.svg)](https://glimind.com/server/pulsemcp%2Fmvr-api?ref=badge)
HTML
<a href="https://glimind.com/server/pulsemcp%2Fmvr-api?ref=badge"><img src="https://glimind.com/v1/readiness/badge/pulsemcp%2Fmvr-api.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/pulsemcp%2Fmvr-api.svg
   :target: https://glimind.com/server/pulsemcp%2Fmvr-api?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:d21de14348e55aec…, first seen 2026-10-25, included at leaf 66501 of 75,084. Version history · verify what your client received.

Tools (7)

Compare: most reliable knowledge servers · most reliable communication servers · most reliable other servers · most reliable data servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is MVR API down right now?

As of 2026-10-26 19:43 UTC, MVR API is up with a Glimind reliability score of 76/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 15 outages in 90 days, with a median recovery of 3 minutes.

How many tools does MVR API provide?

MVR API advertises 7 tools, including mvr_african_market_insights, mvr_commercial_handshake, mvr_context_compile, mvr_decision_check, mvr_entity_resolve.

How do I install MVR API?

Point your MCP client at this streamable_http endpoint: https://africanmarketos.com/mcp

Is MVR API safe to connect to an AI agent?

Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of MVR API?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve