Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Aster Agent Gateway

PYPI · ASTER-AGENT-GATEWAY

Read-only MCP gateway to Aster DEX: 24/7 gold, oil and equity perps, funding with real intervals.

0 this week 91 Trust /100

Last scanned (17 hours ago)

Scores higher than 92% of PyPI servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 15 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to alekskram/aster-agent-gateway). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 59 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1595 tokens (~122/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 19 Nov 26 +1
    • Stability: 0.97 → pass security
  • 18 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 5 Nov 26 −3
    • Security disclosure: fail → unverified ▼ functional
    • Stability: pass → 0.77 functional
  • 30 Oct 26 +1
    • Stability: 0.97 → pass security
Diagnostics

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 21 Nov 2026 · Analysed pypi/aster-agent-gateway@0.1.3

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo alekskram/aster-agent-gateway
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/alekskram/aster-agent-gateway/.github/workflows/release.yml@refs/tags/v0.1.3
Rekor log index 2910449370
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:2e30d949fe40c503d4421265d958bcb43c749b4eb5392b3fe54aecd3db9836f8

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 15 packages
Packages resolved 15
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~1,432 tokens

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 →

Tool Tokens
account_view ~127

Keyless tapi account read for ANY address (Aster Chain JSON-RPC): aster_getBalance / aster_openOrders / aster_userFills (+ spot variants when they exist). Account privacy hides most accounts: a privacy-empty result returns an honest error dict explaining WHY (privacy, not an API failure). `data` in {balance (default), openOrders, userFills, spotBalance, spotOpenOrders, spotUserFills}. Example: account_view(address="0x...")

NameTypeReqDescription
addressstringyes–
datastring––

Structured output declared, but exposes no named fields.

No examples provided.

deposit_flows ~125

Vault deposit flows: Solana getSignaturesForAddress on the Aster vault program (keyless) + EVM eth_getLogs Transfer-to-vault on BSC/ETH/ARB when ASTER_EVM_RPC_URL* is configured; plus the D4 sub-block deposit_stats: hourly buckets and chain breakdown of what was fetched. `chain_filter` in {all (default), solana, bsc, eth, arb}. Example: deposit_flows(limit=20)

NameTypeReqDescription
chain_filterstring––
limitinteger––

Structured output declared, but exposes no named fields.

No examples provided.

exchange_symbols ~114

Symbol universe with filters/precisions/statuses incl. the micro view (MIN_NOTIONAL, stepSize, leverageFilter kind). Junk filter: TEST* spot names and SETTLING futures statuses are hidden unless include_junk=True. venue in {futures, spot, both}. Single-symbol detail when `symbol` given. Example: exchange_symbols(venue="futures", symbol="BTCUSDT")

NameTypeReqDescription
include_junkboolean––
symbol–––
venuestring––

Structured output declared, but exposes no named fields.

No examples provided.

funding_overview ~85

Funding panel from premiumIndex ALL + fundingInfo: all ~730 rates with intervals (1/2/4/8h mixed - flagged honestly), cap/ floor, interestRate, nextFundingTime. `sort` in {rate (default), interval}. Example: funding_overview(limit=10)

NameTypeReqDescription
limitinteger––
sortstring––

Structured output declared, but exposes no named fields.

No examples provided.

funding_screener ~112

One-call ranking of ALL markets by annualized funding rate, by premium, by mark-index spread; plus the D1 sub-block funding_regime: distance to cap/floor (headroom bps) per market from fundingInfo. `direction` in {both (default), long, short} - long = positive rates (longs pay), short = negative. Example: funding_screener(top=5)

NameTypeReqDescription
directionstring––
topinteger––

Structured output declared, but exposes no named fields.

No examples provided.

klines ~131

Klines (OHLCV). price_type last|mark|index selects fapi klines/markPriceKlines/indexPriceKlines; spot goes to sapi /api/v3/klines (price_type ignored). intervals 1m..1M; limit snapped to a priced tier (max 1000). Example: klines(symbol="BTCUSDT", interval="4h", limit=50)

NameTypeReqDescription
intervalstring––
limitinteger––
marketstring––
price_typestring––
symbolstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

mark_index_divergence ~82

Mark/index divergence screener from ONE premiumIndex call (markPrice vs indexPrice spread), cross-checked with markPriceKlines vs klines for the widest divergences (up to 3 symbol-pairs of klines, weight-economical). Example: mark_index_divergence(limit=10)

NameTypeReqDescription
limitinteger––

Structured output declared, but exposes no named fields.

No examples provided.

market_overview ~109

Futures market overview from ONE ticker/24hr ALL call joined with exchangeInfo: panel of TRADING markets (symbol, last, 24h change %, quote volume, trades count), top volumes, status counts, and fresh listings (newest onboardDate, N rows). `sort` in {volume (default), change, listings}. `limit` max 100. Example: market_overview(limit=10)

NameTypeReqDescription
limitinteger––
sortstring––

Structured output declared, but exposes no named fields.

No examples provided.

oi_snapshot ~107

Open interest snapshot. openInterest is a per-symbol endpoint ONLY (each symbol = 1 call); N is capped at 10 per invocation. There is NO keyless OI history (/futures/data/openInterestHist 404s) - stated honestly, never invented. When `symbols` is None the top-volume futures symbols are used. Example: oi_snapshot(symbols=["BTCUSDT", "ETHUSDT"])

NameTypeReqDescription
symbols–––
topinteger––

Structured output declared, but exposes no named fields.

No examples provided.

order_book ~110

Aggregated order book: fapi /depth (futures) or sapi /api/v3/ depth (spot). The requested depth is snapped to the nearest priced tier (weight-aware: 5/10/20/50=2, 100=5, 500=10, 1000=20 weight). Example: order_book(symbol="BTCUSDT", depth=20)

NameTypeReqDescription
depthinteger––
symbolstringyes–
venuestring––

Structured output declared, but exposes no named fields.

No examples provided.

spot_overview ~89

Spot market overview: sapi ticker/24hr ALL joined with exchangeInfo. The spot ticker list carries ~24k ephemeral BTC_UP_DOWN_5M_* options rows that never appear in exchangeInfo; the join keeps only listed symbols with status TRADING (~68 pairs). TEST* junk filtered by name. Example: spot_overview(limit=10)

NameTypeReqDescription
limitinteger––

Structured output declared, but exposes no named fields.

No examples provided.

trades ~87

Recent trades. Futures fapi /trades is keyless and fresh. The spot /trades path was uncertain at recon time - probed live in smoke; if dead the tool returns an honest error dict. Example: trades(symbol="BTCUSDT", limit=10)

NameTypeReqDescription
limitinteger––
symbolstringyes–
venuestring––

Structured output declared, but exposes no named fields.

No examples provided.

tradfi_markets ~154

TradFi-perp screener (24/7 markets): local asset-class map by baseAsset (metals, equity-index, equity-single, energy, treasuries, forex) with per-class volumes/prices/funding, plus the D3 sub-block tradfi_crypto_corr: rolling correlation of a TradFi representative vs BTC computed locally from klines (at most 2 klines calls, cached when possible; honest note when data is insufficient). `window` in {24h, 7d, 30d} selects the correlation window. Example: tradfi_markets(limit=10, window="7d")

NameTypeReqDescription
limitinteger––
window–––

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Aster Agent Gateway MCP server?

Aster Agent Gateway runs locally as a PyPI package, launched with uvx aster-agent-gateway. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · aster-agent-gateway

# add to Claude Code
claude mcp add alekskram-aster-agent-gateway -- uvx aster-agent-gateway
Common questions

What is the Aster Agent Gateway MCP server?

Aster Agent Gateway is an MCP server listed in the public MCP registry as io.github.alekskram/aster-agent-gateway. Read-only MCP gateway to Aster DEX: 24/7 gold, oil and equity perps, funding with real intervals. This page covers its PyPI package (aster-agent-gateway).

Is the Aster Agent Gateway MCP server safe to use?

Aster Agent Gateway scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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 Aster Agent Gateway MCP server expose?

Aster Agent Gateway exposes 13 tools: market_overview, exchange_symbols, order_book, klines, trades, and 8 more. Their descriptions and schemas cost roughly 1,432 tokens of context every time the server is loaded.

Is the Aster Agent Gateway MCP server still maintained?

Aster Agent Gateway is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Aster Agent Gateway MCP server under?

Aster Agent Gateway declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Aster Agent Gateway MCP server?

VerifyMCP ran 16 checks on Aster Agent Gateway, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.