mcp-registry/org.memoryapi/intel · v1.0.0
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.
LLM provider intelligence: recommendations, pricing, and status
Point your MCP client at this streamable-http endpoint: https://intel.memoryapi.org/mcp
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 →
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 →
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
{
"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
}
}{
"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 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.
recommend_llm ~210 tokenslist_providers ~157 tokenscheck_provider_status ~76 tokensStatic 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:
[](https://glimind.com/server/mcp-registry%2Forg.memoryapi%2Fintel?ref=badge)
<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>
.. 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
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.
Compare: most reliable devops servers · most reliable knowledge servers · most reliable ml servers
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.
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"
}
}
}
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.
Memoryapi Intel MCP server advertises 3 tools, including check_provider_status, list_providers, recommend_llm.
Point your MCP client at this streamable-http endpoint: https://intel.memoryapi.org/mcp
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.
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.