AStockEvent
REMOTE · ASTOCKEVENT.COM
A-share filings: reductions, penalties, regulatory letters and stock halts. Source-linked facts.
Available components
Last scanned (5 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability55
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 231 tokens (~77/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 15 days we've observed: 8 tool removals, 0 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +42
- Stability: unverified → fail ▼ security
- Tool “get_entity_state” was removed ▼ security
- Tool “get_event_with_context” was removed ▼ security
- Tool “get_filing_parsed” was removed ▼ security
- Tool “get_related_filings” was removed ▼ security
- Tool “list_company_filings” was removed ▼ security
- Tool “list_coverage” was removed ▼ security
- Tool “scan_recent_events” was removed ▼ security
- Tool “whats_new” was removed ▼ security
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool coverage: 100% → 0% ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: fail → pass ▲ functional
- Schema quality: excellent → fair functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- New tool “get_passage” functional
- New tool “get_timeline” functional
- New tool “list_deals” functional
- 28 Oct 26 −41
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.20 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 21 Oct 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://astockevent.com/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=astockevent.com | CN=YE1,O=Let's Encrypt,C=US | 1 Nov 2026 | 30 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5e4c1a4dcbe31927c4abbe6d42837ce7a66 |
| SANs: astockevent.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of astockevent.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| astockevent.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'self'; script-src 'self'; style-src 'self'; connect-src 'self'; img-src 'self' data:; object-src 'none'; base-uri 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://astockevent.com/mcp/ | Verified | 200 | |
| http (plaintext) | http://astockevent.com/mcp/ | HTTPS enforced | 308 | https://astockevent.com/mcp/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_passage ~56
Read a citation returned by the selected deal, with neighbouring source paragraphs.
| Name | Type | Req | Description |
|---|---|---|---|
| block | string | yes | – |
| build | – | – | – |
| deal | string | yes | – |
| document | string | yes | – |
| run | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_timeline ~75
Read source mentions by filing date (YYYY-MM-DD), including coverage and qualifiers. Omit build for current results; explicit build requests historical results. Repeated mentions are not newly occurring events or notification changes.
| Name | Type | Req | Description |
|---|---|---|---|
| build | – | – | – |
| deal | string | yes | – |
| end | – | – | – |
| start | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_deals ~37
Find astockevent acquisitions by name, verified ticker/alias or CIK; not all-market search.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the AStockEvent MCP server?
AStockEvent is a hosted endpoint at https://astockevent.com/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · astockevent.com
claude mcp add --transport http com-astockevent-astockevent 'https://astockevent.com/mcp/'
What is the AStockEvent MCP server?
AStockEvent is an MCP server listed in the public MCP registry as com.astockevent/astockevent. A-share filings: reductions, penalties, regulatory letters and stock halts. Source-linked facts. This page covers its hosted endpoint (https://astockevent.com/mcp/).
Is the AStockEvent MCP server safe to use?
AStockEvent scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AStockEvent MCP server expose?
AStockEvent exposes 3 tools: list_deals, get_timeline, get_passage. Their descriptions and schemas cost roughly 168 tokens of context every time the server is loaded.
Does the AStockEvent MCP server require authentication?
No. We connected to AStockEvent without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AStockEvent MCP server still maintained?
AStockEvent is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.