viaNexus vAST

Name: viaNexus vAST MCP Server
Availability: InStock
Author: viaNexus vAST

Finance6 tools

Query real-time and historical equity prices, fundamentals, earnings transcripts and financial news from 30+ institutional data partners through one MCP endpoint. viaNexus enforces dataset entitlements server-side before rows reach the model, and the directory lists two rule-management tools that the vendor's own documentation never describes.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 19 August 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect viaNexus vAST via MCP

https://vast.blueskyapi.com/vianexus/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

viaNexus vAST Tools & Capabilities (6)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

What a rule is, and what happens when one fires, is undocumented. viaNexus states the server provides alerting on data events and gives two alert-shaped usage examples, but defines no rule fields, no trigger semantics, no evaluation cadence and no delivery channel for the MCP server.
The delivery channel is inferred, not stated for this connector. viaNexus describes email delivery of alert payloads for its OpenBB chat agent. Whether an MCP-created rule behaves the same way is not documented.
Whether a rule can reach a third party is unknown. No recipient parameter, distribution list or external address is documented. Absence of documentation is not absence of capability.
create_rule may produce messages after the conversation ends. If rules are alerts, a single approved tool call has effects at times when no human is present to review them. Approve accordingly.
delete_rule recoverability and logging are both undocumented. Nothing states whether a deleted rule can be restored or whether deletion is recorded anywhere. A missing alert is a silent failure.
The directory record carries no permissions label at all — not "Read", not "Write". The field is absent, over a tool list containing create and delete verbs.
No tool annotations were readable. The endpoint returns 401 to an anonymous handshake, so no readOnlyHint and no destructiveHint were seen. Nothing on this page should be read as a read-only claim about any tool.
viaNexus documents fewer tools than the directory lists. Its skill packs declare compatibility with three tools and its product page summarises the MCP service as two. The three rule tools appear in no vendor-authored artefact we read.
The vendor's MCP documentation names a different endpoint host than the directory. Both hosts return 401 to an anonymous probe, so both are live, but they advertise different descriptor URLs. We did not authenticate against either.
Price data is delayed and the delay carries a display obligation. viaNexus's own disclaimer page states all CTA and UTP pricing data is delayed at least 15 minutes, and requires anyone displaying it to show a 15-minute-delay notice, plus a real-time consolidated-volume notice beside volume figures.
Some datasets carry third-party approval requirements. viaNexus states that access to its intraday-price and quote endpoints must be separately approved by the UTP Plan Administrator, including completion of a UTP vendor agreement. This catalogue gives no legal or compliance advice — read your own obligations and viaNexus's terms.
The single user scope draws no boundary between reading market data and creating or deleting rules. A client cannot narrow the token.
Every coverage figure on this page is viaNexus's own — 30+ partners, 40 datasets, the 14/26 split — published in marketing material, and none of it was independently verified.
Prompts are unconfirmed. Anthropic's snapshot records an empty prompt list, and the gated endpoint blocked our own check. An empty list in the snapshot is not evidence the server serves none.
Alert metering is undocumented. viaNexus advertises a 14-day trial and a dataset-priced catalogue, but nothing states whether creating rules, or the alerts they generate, consume quota or cost money.
We did not call any tool, authenticate, create a rule or delete one. Everything on this page comes from unauthenticated probes, the directory snapshot, and viaNexus's published material.
This catalogue gives no investment or financial advice, and takes no view on whether any dataset is fit for any purpose.

Frequently asked questions

What is a rule in the viaNexus vAST MCP connector?

Undocumented. Anthropic's directory lists three rule tools, and viaNexus documentation describes alerting on data events plus an example asking to be alerted on new headlines. But no viaNexus page defines a rule's fields, its trigger conditions, or its delivery channel. The vendor's own skill packs declare compatibility with only three tools and never mention rules. Treat the shape as unverified.

Can the viaNexus MCP connector send me alerts later, without me being present?

Probably, though viaNexus does not document it for this connector. Its vAST page describes alerts on any condition with data payloads delivered to email, but attributes that to its OpenBB chat agent rather than the MCP server. If rule creation through MCP behaves the same way, one approved tool call produces messages after the conversation ends. Verify before relying on it.

Is deleting a viaNexus alerting rule reversible?

Not documented either way. No viaNexus page states whether a deleted rule can be restored, whether deletion is logged, or whether anything notifies the account owner. That matters more than usual here: a deleted monitoring rule fails silently — the alert that would have fired simply does not, and nothing in the conversation surfaces the gap. Confirm with viaNexus support first.

What data does the viaNexus vAST MCP server cover?

Equity market data and financial content from institutional providers. viaNexus states 30+ data partners and 40 datasets — 14 bundled NexusCore and 26 premium NexusEdge — spanning real-time and historical prices, fundamentals, earnings transcripts, analyst estimates, index data and news. Named partners include MT Newswires, Aiera, BMLL, ExtractAlpha and IndexOne. Coverage depends entirely on your subscription.

Why is the viaNexus MCP endpoint on blueskyapi.com?

Because both brands are the same operation. The directory's privacy-policy URL on blueskydataplatform.com redirects to vianexus.com, the console at console.blueskyapi.com serves pages branded viaNexus in markup, and its content-security policy names vianexus.com as an allowed frame parent. BlueSky is the infrastructure hostname; viaNexus is the customer-facing brand. Nothing here suggests an unrelated third party.

Does viaNexus filter data by my subscription before Claude sees it?

Yes, server-side. viaNexus describes dataset permissions carried in a signed software statement and enforced by the data plane, so an out-of-scope call returns a permission-denied error rather than rows. The company states the agent never sees a row it lacks rights to and that there is no client-side filter to bypass. Those are vendor claims we could not test anonymously.

Does Anthropic's directory list a permissions label for viaNexus vAST?

No. The 2026-08-16 record carries no permissions field at all, despite listing two tools whose names imply creation and deletion. Compare Aiera, whose row reads Read. Absence is not a read-only claim, and it is not evidence of write access either — it means the shape of what these tools change was never labelled for the reader.

Sources

viaNexus vAST and MCP server documentation — https://console.blueskyapi.com/docs/vAST#mcp (fetched 2026-08-19; the alerting-on-data-events bullet, the four usage examples including the alert-creation and alert-deletion ones, the Claude Enterprise/Teams and Workspace Owner requirement, and the https://vast-mcp.blueskyapi.com/mcp endpoint). The URL is hash-routed and plain curl returns only a single-page-app shell, so the fragment resolves client-side. We read the router bundle at https://console.blueskyapi.com/build/docsV2/main.js to find the content API, which serves each page's markdown at /docs/markdowns/<name>; the vAST document was then read as markdown at https://console.blueskyapi.com/docs/markdowns/vast · retrieved 2026-08-19
viaNexus vAST product page — https://vianexus.com/vast/ (fetched 2026-08-19; the alerts-delivered-to-email statement for the OpenBB chat agent, the 30+ dataset figure, the NexusCore/NexusEdge split, the server-side entitlement walkthrough with its allowed and refused example calls, the one-hour access-token lifetime, the software-statement registration flow, the search-and-fetch SDK narrative, and the 14-day no-card trial) · retrieved 2026-08-19
viaNexus disclaimers — https://console.blueskyapi.com/docs/markdowns/disclaimers (fetched 2026-08-19; the 15-minute delay on CTA and UTP pricing data and the two required on-screen disclaimers) · retrieved 2026-08-19
viaNexus third-party requirements — https://console.blueskyapi.com/docs/markdowns/third-party-requirements (fetched 2026-08-19; the UTP Plan Administrator approval requirement and the vendor-agreement obligation for intraday-price and quote access) · retrieved 2026-08-19
blueskynexus/claude-skills, viaNexus's published Claude skill packs, MIT licence — https://github.com/blueskynexus/claude-skills (fetched 2026-08-19; the statement that all skills are tested against the fetch, search and current_date schemas, the 40-dataset and 14/26 CORE-EDGE figures, the named data partners, and the directory endpoint URL) · retrieved 2026-08-19
viaNexus financial-research skill — https://raw.githubusercontent.com/blueskynexus/claude-skills/HEAD/financial-research/SKILL.md (read 2026-08-19; the current_date anchoring rationale, and the fetch parameter shape with dataset_name, product, endpoint, symbols and last) · retrieved 2026-08-19
viaNexus portfolio-monitor skill — https://raw.githubusercontent.com/blueskynexus/claude-skills/HEAD/portfolio-monitor/SKILL.md (read 2026-08-19; the quote field list, the current_date-before-news pattern, the two-tool compatibility array, and the statement that the skill does not persist holdings) · retrieved 2026-08-19
blueskynexus/viaNexus-agent-sdk-python, open-source agent SDK, MIT licence — https://github.com/blueskynexus/viaNexus-agent-sdk-python (fetched 2026-08-19; file listing read via the GitHub trees API — the SDK is a client library and defines no rule semantics) · retrieved 2026-08-19
viaNexus privacy policy — https://vianexus.com/privacy/ (fetched 2026-08-19; the directory's blueskydataplatform.com/privacy/ URL 301-redirects here, and the document is titled viaNexus Privacy Policy) · retrieved 2026-08-19
Live RFC 9728 protected-resource descriptor, path-insert form — https://vast.blueskyapi.com/.well-known/oauth-protected-resource/vianexus/mcp (fetched 2026-08-19; HTTP 200, 207 bytes; resource is the full endpoint, one scope user, the Cloud Run authorization server). This is the form the www-authenticate header named · retrieved 2026-08-19
Live RFC 9728 protected-resource descriptor, root form — https://vast.blueskyapi.com/.well-known/oauth-protected-resource (fetched 2026-08-19; HTTP 200, 198 bytes; a byte-different body whose resource is https://vast.blueskyapi.com/mcp, not this connector's endpoint) · retrieved 2026-08-19
Live RFC 9728 protected-resource descriptor, path-append form — https://vast.blueskyapi.com/vianexus/mcp/.well-known/oauth-protected-resource (fetched 2026-08-19; HTTP 401, 112 bytes, the same auth-error body as the endpoint itself) · retrieved 2026-08-19
Live RFC 8414 authorization-server metadata — https://vast.blueskyapi.com/.well-known/oauth-authorization-server returned a 307 with a zero-byte body and the path-append form returned 404 with a nine-byte body, both 2026-08-19. The authorization server is a separate Cloud Run host named in the descriptors; we did not probe it · retrieved 2026-08-19
Live anonymous probe — 2026-08-19: an anonymous initialize POST to https://vast.blueskyapi.com/vianexus/mcp returns HTTP 401 with www-authenticate: Bearer error="invalid_client", error_description="viaNexus API token in headers not detected, trying OAuth 2.0", resource_metadata="https://vast.blueskyapi.com/.well-known/oauth-protected-resource/vianexus/mcp". The same probe against the documentation's https://vast-mcp.blueskyapi.com/mcp also returns 401, with its own resource_metadata pointer and Google Frontend response headers · retrieved 2026-08-19
Live header and markup evidence for the brand relationship — 2026-08-19: https://console.blueskyapi.com/ serves HTML with data-ui-brand="vianexus" on the root element and a content-security policy whose frame-ancestors directive names https://vianexus.com and https://www.vianexus.com. No x-powered-by header appeared on any viaNexus or BlueSky response we saw · retrieved 2026-08-19
Documentation-discovery order — 2026-08-19: console.blueskyapi.com/robots.txt, /llms.txt and /sitemap.xml all return the console's HTML 404 shell with a 404 status and no Content-Signal axes. The .md suffix form of the docs URL returns the same single-page-app shell, so the router bundle was read instead. vianexus.com/robots.txt allows all user agents, disallows six site-management paths, names a sitemap, and carries no Content-Signal axes; vianexus.com/llms.txt returns a 302 · retrieved 2026-08-19
Anthropic connector directory — https://claude.ai/directory/01c43f47-7757-4ae7-91f2-310eff8bb58d (snapshot 2026-08-16; six tools, an empty prompt list, no permissions field, streamable HTTP, the vast.blueskyapi.com/vianexus/mcp endpoint, the four categories, and the partner tier) · retrieved 2026-08-16