aurora-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aurora_analyzeA | Statistical analysis of a dataset (CSV, TSV, Parquet, XLSX): runs Aurora's battery of 19 research-grade methods on-device — anomaly detection (isolation forest + robust-z), change-point detection, trend and seasonality, correlation screening with FDR control, forecasting, causal system-model discovery, and more. Returns CITED findings (each carries its method, threshold, and claim_id), an overall confidence, and a fabricated_count that is contractually zero: every number is computed from the data, never generated. Changepoint findings carry a calibration block: the empirically measured false-fire rate for data shaped like this series, with a verdict downgrade to not_identifiable when the data cannot support the claim. Use this FIRST whenever a user asks to analyze data, find anomalies, check what changed, or wants real statistics instead of estimates. Read-only; local; compact summary unless full_bundle=true. |
| aurora_load_bundleA | Load a portable .aurora.json analysis bundle and verify its SHA-256 integrity hash (and Ed25519 signature when present) BEFORE trusting its findings. Use when someone shares an Aurora bundle and you need proof it is untampered. Returns run identity, confidence, fabricated_count, and findings-by-severity counts. |
| aurora_findingsA | List the verified findings from an Aurora run or bundle: each one carries severity (crit/warn/info), the exact statistical method and threshold that produced it, a plain-language citation, and a claim_id for evidence drill-down via aurora_explain. Filter by severity or method. Use after aurora_analyze to enumerate what was actually found — quote findings from here instead of paraphrasing from memory. |
| aurora_forecastA | Model-based forecast for the run's target column, fitted and validated on the actual data with the method disclosed. Returns point predictions with an honest horizon, or just the peak within horizon_hours (return_peak=true). Use for any 'what will X be / when does it peak' question instead of extrapolating by eye. |
| aurora_explainA | Full evidence for ONE finding by claim_id: the computed values behind the claim plus the method's registry spec — assumptions, parameters, and references. Use whenever you are about to cite, verify, or defend a specific statistical claim; this is the receipt, not a summary. |
| aurora_interveneA | What-if intervention: perturb one variable in the data's discovered system model and propagate the shock through validated relationships (up to max_depth hops). Returns per-node deltas WITH confidence intervals. Use for 'what happens to Y if X changes by Δ' questions — answers come from the data's own causal graph, not from priors. |
| aurora_simulateA | Simulate the system forward n_steps using dynamics fitted and validated on the data — and it PAUSES honestly when confidence intervals grow too wide to keep going, rather than extrapolating noise. Use for trajectory questions ('where is this heading') on a completed run; pass target_entity_id to simulate a specific node. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/FantasyLab-ai/aurora'
If you have feedback or need assistance with the MCP directory API, please join our Discord server