Is the Memoryapi Filing MCP server down?

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

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

SEC filings, insider trades, and earnings data

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

Agent-readiness: B (82/100)

What to fix (3)

Auto-fix: 5 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%2Ffiling/fixes

{
  "name": "get_earnings_data",
  "description": "Get structured financial data from SEC XBRL filings. Returns revenue, net income, EPS, assets, and more with historical data and YoY growth.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "cik": {
        "type": "string",
        "description": "SEC CIK number"
      },
      "ticker": {
        "type": "string",
        "description": "Stock ticker symbol"
      },
      "concept": {
        "type": "string",
        "default": "revenue",
        "description": "Financial concept: revenue, net_income, eps, assets, liabilities, equity, operating_income, gross_profit, cash, debt"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "get_fda_data",
  "description": "Get FDA drug recalls and adverse event reports from openFDA. Search 17,000+ recalls and 20M+ adverse events by drug name or company.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "drug": {
        "type": "string",
        "description": "Drug name to search (e.g. aspirin, Tylenol)"
      },
      "type": {
        "type": "string",
        "default": "recalls",
        "description": "recalls (default) or adverse_events"
      },
      "limit": {
        "type": "number",
        "default": 10,
        "description": "Number of results (max 25)"
      },
      "company": {
        "type": "string",
        "description": "Company/manufacturer name"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "get_insider_trades",
  "description": "Get insider trading activity from SEC Form 4 filings. Shows when executives and directors buy or sell company stock — a key alpha signal for trading agents.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "cik": {
        "type": "string",
        "description": "SEC CIK number"
      },
      "limit": {
        "type": "number",
        "default": 10,
        "description": "Number of trades"
      },
      "ticker": {
        "type": "string",
        "description": "Stock ticker symbol"
      }
    }
  },
  "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/filing"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/org.memoryapi/filing"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~702 tokens).
• Tool names are unique and portable across clients.
• 99.80% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• get_recent_filings ~159 tokens
• get_fda_data ~154 tokens
• get_earnings_data ~148 tokens
• get_insider_trades ~122 tokens
• get_material_events ~119 tokens

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:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.memoryapi%2Ffiling.svg)](https://glimind.com/server/mcp-registry%2Forg.memoryapi%2Ffiling?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Forg.memoryapi%2Ffiling?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.memoryapi%2Ffiling.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.memoryapi%2Ffiling.svg
   :target: https://glimind.com/server/mcp-registry%2Forg.memoryapi%2Ffiling?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:108bb3a7dda84045…, first seen 2026-10-17, included at leaf 14224 of 75,084. Version history · verify what your client received.

Tools (5)

• get_earnings_data
• get_fda_data
• get_insider_trades
• get_material_events
• get_recent_filings

Compare: most reliable finance servers · most reliable data servers

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

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

FAQ

Is the Memoryapi Filing MCP server down right now?

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

How many tools does Memoryapi Filing MCP server provide?

Memoryapi Filing MCP server advertises 5 tools, including get_earnings_data, get_fda_data, get_insider_trades, get_material_events, get_recent_filings.

How do I install Memoryapi Filing MCP server?

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

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

Glimind scanned all 5 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 Filing 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.