
AllocContext
io.github.AllocContextPublished by GitHub account AllocContextv0.3.0Updated Oct 24, 2026
Self-host MCP: portfolio crypto context for agents. PyPI stdio; MIT.
Overview
Self-hosted MCP server that gives an assistant portfolio-aware crypto context: holdings, market data, sentiment, macro, regime, and allocation math.
- What you can do
- AllocContext runs locally and exposes tools that return deterministic JSON context bundles for crypto portfolios. Tools include get_context_bundle for a full snapshot, get_market_context for sentiment, macro, ETF and breadth fields, get_context_at and get_context_delta for saved snapshots and shifts between them, plus get_portfolio_state for live NAV and holdings. Pure math tools such as check_allocation_band, check_allocation_bands and get_rebalance_plan compute drift versus targets and USD rebalance moves without portfolio credentials.
- When to use it
- Use it when an assistant needs repeatable, holdings-scoped crypto market context, allocation drift checks, or rebalance planning, and you are willing to run the ingest and server yourself. It is aimed at self-hosters rather than a hosted service.
- Requirements
- Local Python install of the alloc-context package with the mcp extra, run via uvx or the alloc-context command over stdio. A config file copied from config/config.example.yaml and a .env copied from .env.example. Read-only exchange keys are needed only for portfolio ingest or macro feeds; the ALLOC_CONTEXT_DB environment variable points at the SQLite state file. Absolute paths are recommended.
Installation
In SourceWeft
- Open AllocContext 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- v0.3.0LatestSep 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.