Is the Memoryapi Intel MCP server down?

mcp-registry/org.memoryapi/intel · v1.0.0

healthy
Last checked 2026-10-27 16:11 UTC · handshake 393ms

As of 2026-10-27 16:11 UTC, the Memoryapi Intel MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 30 outages in 90 days, with a median recovery of 4 minutes.

uptime (30d checks)
99.7%
checks observed
5,105
outages (90d)
30
tools
3

LLM provider intelligence: recommendations, pricing, and status

Point your MCP client at this streamable-http endpoint: https://intel.memoryapi.org/mcp

Agent-readiness: B (82/100)

B (82/100): 0 error(s), 2 warning(s) across 3 tool(s); ~443 tokens of tool definitions.
Scores higher than 35% of 15,806 MCP servers Glimind has audited.
Its tool list costs an agent ~443 tokens per session — lighter than 95% of servers.
82 → 82 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol40
Reliability100
Stability100

What to fix (3)

3 of 3 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: check_provider_status, list_providers, recommend_llm

Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Forg.memoryapi%2Fintel/fixes

check_provider_status 1 change
{
  "name": "check_provider_status",
  "description": "Check operational status and recent latency for one or all LLM providers.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "provider": {
        "type": "string",
        "description": "Specific provider slug (e.g. openai-gpt4o). Omit for all."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
list_providers 1 change
{
  "name": "list_providers",
  "description": "List LLM providers with their capabilities, pricing, and agent scores. Filter by specific requirements.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "best_for": {
        "type": "string",
        "description": "Filter by use case: tool_calling, reasoning, cost, speed, long_context, rag"
      },
      "max_price": {
        "type": "number",
        "description": "Max input price per million tokens"
      },
      "x402_native": {
        "type": "boolean",
        "description": "Only show x402-native providers"
      },
      "tool_calling": {
        "type": "boolean",
        "description": "Only show providers with tool calling"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

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":["mcp-registry/org.memoryapi/intel"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/org.memoryapi/intel"}) 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/mcp-registry%2Forg.memoryapi%2Fintel.svg)](https://glimind.com/server/mcp-registry%2Forg.memoryapi%2Fintel?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Forg.memoryapi%2Fintel?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.memoryapi%2Fintel.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.memoryapi%2Fintel.svg
   :target: https://glimind.com/server/mcp-registry%2Forg.memoryapi%2Fintel?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:0e2ef22e5deb7fa8…, first seen 2026-10-17, included at leaf 9284 of 80,233. Version history · verify what your client received.

Tools (3)

Compare: most reliable devops servers · most reliable knowledge servers · most reliable ml 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 the Memoryapi Intel MCP server down right now?

As of 2026-10-27 16:11 UTC, the Memoryapi Intel MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 30 outages in 90 days, with a median recovery of 4 minutes.

How many tools does Memoryapi Intel MCP server provide?

Memoryapi Intel MCP server advertises 3 tools, including check_provider_status, list_providers, recommend_llm.

How do I install Memoryapi Intel MCP server?

Point your MCP client at this streamable-http endpoint: https://intel.memoryapi.org/mcp

Is the Memoryapi Intel MCP server safe to connect to an AI agent?

Glimind scanned all 3 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 Memoryapi Intel MCP server?

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