
AION Indian Market Intelligence for Macro Event & Sector Impact Analysis
io.github.AION-AnalyticsPublished by GitHub account AION-Analyticsv1.0.6Updated Oct 24, 2026
Indian macro-event and sector impact intelligence for MCP workflows.
Overview
Local MCP server for Indian macro-event and sector impact intelligence, giving an assistant context on how events affect Indian markets and sectors.
- What you can do
- Provides Indian macro-event and sector impact intelligence to MCP workflows.
- Supplies context on macro events and their sector-level effects for Indian markets.
- No tool list, instructions or README were supplied, so the exact operations are not documented.
- When to use it
- When an assistant needs background on Indian macroeconomic events and how they may affect specific sectors, for example in market commentary or research workflows.
- Requirements
- Runs as a local process installed from the PyPI package aion-indian-market-intelligence over stdio; a Python environment is needed. No authentication, environment variables or headers are declared. Desktop only; not executable on the web.
Installation
In SourceWeft
- Open AION Indian Market Intelligence for Macro Event & Sector Impact Analysis in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.0.6LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.