Is the Astockevent MCP server down?

mcp-registry/com.astockevent/astockevent · v1.28.0

healthy
Last checked 2026-10-26 17:12 UTC · handshake 741ms

As of 2026-10-26 17:12 UTC, the Astockevent MCP server is up with a Glimind reliability score of 79/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 2 minutes.

uptime (30d checks)
99.6%
checks observed
1,336
outages (90d)
6
tools
8

A-share filings: reductions, penalties, regulatory letters and stock halts. Source-linked facts.

Point your MCP client at this streamable-http endpoint: https://astockevent.com/mcp/

Agent-readiness: A (90/100)

A (90/100): 0 error(s), 1 warning(s) across 8 tool(s); ~2,456 tokens of tool definitions.
Scores higher than 69% of 15,769 MCP servers Glimind has audited.
Its tool list costs an agent ~2,456 tokens per session — more than 50% of servers.
90 → 90 since 2026-10-21
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility100
Protocol100
Reliability100
Stability100

What to fix (1)

8 of 8 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: get_entity_state, get_event_with_context, get_filing_parsed, get_related_filings, list_company_filings and 3 more

Auto-fix: 6 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%2Fcom.astockevent%2Fastockevent/fixes

get_entity_state 1 change
{
  "name": "get_entity_state",
  "description": "Return what is true RIGHT NOW about one A-share listed company or one shareholder entity, folded from its regulatory filings: pending and executed share-reduction plans, administrative-penalty proceedings, and exchange inquiry letters. Call this when you need the current situation of a specific subject — for example 'is this shareholder still selling', 'is this company under investigation', 'has it replied to the inquiry letter'.\n\nDo NOT call this to find out what happened across the market rece",
  "inputSchema": {
    "type": "object",
    "title": "get_entity_stateArguments",
    "properties": {
      "code": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Code",
        "default": null,
        "description": "Security code, e.g. '000029'. Must be given together with market."
      },
      "aent_": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Aent",
        "default": null,
        "description": "Opaque entity id taken from a previous response. Never construct or guess one. Mutually exclusive with code/market."
      },
      "locale": {
        "enum": [
          "en",
          "zh"
        ],
        "type": "string",
        "title": "Locale",
        "default": "en",
        "description": "Language of human-readable data labels only; errors and this description are always English."
      },
      "market": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Market",
        "default": null,
        "description": "One of ['SH', 'SZ', 'BJ']. Required when code is given."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_event_with_context 1 change
{
  "name": "get_event_with_context",
  "description": "Return one specific filing event together with its full timeline (every stage the case went through, each with its own source PDF) and which subject's state it changed. Call this after another tool handed you an event id and you need the whole thread rather than a one-line summary — for example to see how a penalty case progressed from filing to decision.\n\nDo NOT call this without an event id from a previous response: ids are opaque and cannot be guessed or constructed. Internal database identif",
  "inputSchema": {
    "type": "object",
    "title": "get_event_with_contextArguments",
    "required": [
      "aevt"
    ],
    "properties": {
      "aevt": {
        "type": "string",
        "title": "Aevt",
        "description": "Opaque event id from a previous response. Must start with 'aevt_'."
      },
      "locale": {
        "enum": [
          "en",
          "zh"
        ],
        "type": "string",
        "title": "Locale",
        "default": "en",
        "description": "Language of data labels only."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_filing_parsed 1 change
{
  "name": "get_filing_parsed",
  "description": "Return ONE filing already parsed for you: its available normalised text and its tables as structured cells. Call it after list_company_filings, with the `aann_` id that tool returned, when you need what a filing actually says rather than just its title and PDF link.\n\nThis is the step your own pipeline would otherwise have to do: a filing PDF is a layout format, not a data format, so pulling clean text and real table cells out of it is where ad-hoc extraction usually goes wrong. Tables come back ",
  "inputSchema": {
    "type": "object",
    "title": "get_filing_parsedArguments",
    "required": [
      "aann_"
    ],
    "properties": {
      "aann_": {
        "type": "string",
        "title": "Aann",
        "description": "Opaque filing id from list_company_filings, e.g. aann_Kyw46MM1gCnIaBxA."
      },
      "text_offset": {
        "type": "integer",
        "title": "Text Offset",
        "default": 0,
        "description": "0-based offset into the filing's full text. Start at 0; then pass next_text_offset from the previous call."
      }
    }
  },
  "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/com.astockevent/astockevent"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.astockevent/astockevent"}) 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%2Fcom.astockevent%2Fastockevent.svg)](https://glimind.com/server/mcp-registry%2Fcom.astockevent%2Fastockevent?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.astockevent%2Fastockevent?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.astockevent%2Fastockevent.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.astockevent%2Fastockevent.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.astockevent%2Fastockevent?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:576214f81698972c…, first seen 2026-10-21, included at leaf 39818 of 74,339. Version history · verify what your client received.

Tools (8)

Compare: most reliable data servers · most reliable retrieval servers · most reliable knowledge 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 Astockevent MCP server down right now?

As of 2026-10-26 17:12 UTC, the Astockevent MCP server is up with a Glimind reliability score of 79/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 2 minutes.

How many tools does Astockevent MCP server provide?

Astockevent MCP server advertises 8 tools, including get_entity_state, get_event_with_context, get_filing_parsed, get_related_filings, list_company_filings.

How do I install Astockevent MCP server?

Point your MCP client at this streamable-http endpoint: https://astockevent.com/mcp/

Is the Astockevent MCP server safe to connect to an AI agent?

Glimind scanned all 8 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 Astockevent 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