Polymarket and Predict.fun historical tick data, plus backtest quotes and status, over MCP
Nothing to run from here
Astockevent is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
8
tools declared
remote
at its publisher
—
calls last 7d
What it does
AStockEvent MCP Server — Structured A-share announcement event feed for AI agents
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http astockevent-mcp https://astockevent.com/mcp/
# 2 — ask your agent for something these tools do
# get_entity_state, get_event_with_context, whats_new and 5 more
Astockevent costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
NEAll 1 server
nengjianglunpi1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http astockevent-mcp https://astockevent.com/mcp/Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 i
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | no | Security code, e.g. '000029'. Must be given together with market. | |
| market | no | One of ['SH', 'SZ', 'BJ']. Required when code is given. | |
| aent_ | no | Opaque entity id taken from a previous response. Never construct or guess one. Mutually exclusive with code/market. | |
| locale | string | no | Language of human-readable data labels only; errors and this description are always English. |
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. Do NOT call this without an event id from
| Parameter | Type | Required | Notes |
|---|---|---|---|
| aevt | string | yes | Opaque event id from a previous response. Must start with 'aevt_'. |
| locale | string | no | Language of data labels only. |
Discover events with a linked filing dated within the last seven Beijing calendar days including today, and updated in the last seven days. A new filing may mention an old case; this does not imply new case progress. matched_filing gives the filing date and PDF that qualified the event; root source_pdf_url, phase and payload describe current event context. announce_ts remains the original first di
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cursor | no | The cursor value from a previous response, passed back verbatim. | |
| cursor_aevt | no | The cursor_aevt value from the same response. Required together with cursor for correct paging. | |
| limit | integer | no | 1..100. Default 50. |
| locale | string | no | Language of data labels only. |
Discover one filing event type across companies using linked filing dates within the last seven Beijing calendar days including today. Dates omitted use this whole window; one omitted end uses the corresponding allowed boundary. Partial overlap is clamped; reversed or wholly outside dates are errors. effective_since/effective_until report the actual dates. A new filing mentioning an old case quali
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_type | string | yes | Which filing type to scan. Call list_coverage for the current scope. |
| since | no | Inclusive start date, YYYY-MM-DD. | |
| until | no | Inclusive end date, YYYY-MM-DD (the whole day counts). | |
| phase | no | Restrict to one stage of the case. Must belong to the chosen event_type; the error message lists the valid values. | |
| limit | integer | no | 1..100. Default 50. |
| cursor | no | Return the previous cursor unchanged to continue within its frozen dates. | |
| locale | string | no | Language of data labels only. |
List the most recent filings of ONE listed company: title, date, a direct link to the source PDF, and — where we have it — the structured extraction that filing produced. Call this to answer 'what has this company filed lately' and 'give me the original document', which is what most callers actually want before any analysis. This is the widest view we offer: it covers EVERY filing we hold for the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | Six-digit A-share ticker, e.g. 000029. |
| market | string | yes | Which exchange the ticker belongs to. |
| limit | integer | no | 1..50. Default 20. |
Return ONE filing already parsed for you: its normalised full 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. This 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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| aann_ | string | yes | Opaque filing id from list_company_filings, e.g. aann_Kyw46MM1gCnIaBxA. |
| text_offset | integer | no | 0-based offset into the filing's full text. Start at 0; then pass next_text_offset from the previous call. |
Return the other filings this filing cites. Call it after list_company_filings or get_filing_parsed, with the aann_ id they returned, when you need the paper trail around a filing rather than the filing alone. Chinese listed companies print a filing number on most of their filings (e.g. 2026-047) and later filings cite it in their text. This tool follows those citations. Matching is exact and s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| aann_ | string | yes | Opaque filing id from list_company_filings, e.g. aann_Kyw46MM1gCnIaBxA. |
| limit | integer | no | Max related filings to return. See limits.related_limit_max. |
Return exactly what this server covers and the limits it enforces. Call this first, or whenever a query comes back empty and you want to know whether the filing type is even in scope, before concluding the data is incomplete. It takes no arguments and does not touch the database, so it works even when everything else is degraded. Coverage is deliberately narrow and expanding over time; the `event
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Astockevent or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 0.2.1 · scanned 6 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings1 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest2dc22d3bf39daa3966da07121ef3ae7218597d0cc75600bd6ac9471b4c82a657
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest2dc22d3bf39daa39
Scanned2026-10-06
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.2.1.
0.2.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Astockevent can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.