bellwether-mcp
Version: 1.3.5
Documentation — Installation, deployment, and tool usage are maintained in the official documentation.
Crypto discovery/rankings/market caps (CoinMarketCap), Fed macro and liquidity
series with point-in-time vintages (FRED/ALFRED), and the FOMC decision
calendar (hike/cut/hold, sourced) — as an MCP tool surface and, through
agent-connector-sdk's declarative mcp_tool source adapter, as bounded,
checkpointed ingestion streams intended for EG's finance-v1 world-model
ontology (feat/finance-core, not yet published — see AGENTS.md).
Not a venue-specific OHLCV feed. CoinMarketCap's general historical OHLCV
endpoint documents hourly/daily coverage only, not minute-level exchange
candles — pair this package with an emerald-exchange backend for tradable
bars and charts.
Sources
| Ledger row | Sources | Target class (provisional) |
|---|---|---|
| EH-412 (crypto discovery/caps) | CoinMarketCap listings/quotes/global-metrics | Instrument, MacroEvent |
| EH-412 (Fed macro series) | FRED/ALFRED series/observations, series/vintagedates |
EconomicIndicator |
| EH-412 (FOMC calendar) | Curated dataset, sourced to federalreserve.gov press releases | MacroEvent |
| EH-422 (macro/liquidity) | FRED named aliases: WALCL, WDTGAL, M2SL, RRPONTSYD, WRESBAL, DGS10, DTWEXBGS |
EconomicIndicator |
Instrument, EconomicIndicator and MacroEvent are the design doc's own
proposed finance-v1 class names
(plans/refactor/proposals/FINANCE-INTEGRATION-20260924.md section 4/7).
EG's feat/finance-core branch, which owns finance-v1, has not published
anything yet as of this package's build — see AGENTS.md "Ontology mapping"
before trusting these as final.
Tools
Eight MCP tools, one FastMCP server (bellwether-mcp console script):
cmc_listings, cmc_quotes, cmc_global_metrics, fred_macro_series_aliases,
fred_series_observations, fred_series_observations_asof,
fred_series_vintage_dates, fomc_calendar_list.
Every tool is keyless except cmc_* and fred_*, whose credentials are
resolved server-side through agent_connector_sdk.credentials
(BELLWETHER_CMC_API_KEY, BELLWETHER_FRED_API_KEY) — never accepted as a
tool argument. fomc_calendar_list reads a packaged, curated, sourced dataset
and needs no credential and no network.
See AGENTS.md for architecture, the ontology-mapping
authority, the FOMC dataset's provenance, rate limits, and commands.
1 maintainer
Metadata
1 maintainer
Release files for bellwether-mcp 1.3.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| bellwether_mcp-1.3.5.tar.gz | 37.3 kB | Without provenance | Details for bellwether_mcp-1.3.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bellwether_mcp-1.3.5-py3-none-any.whl | Python 3 | none | any | Details for bellwether_mcp-1.3.5-py3-none-any.whl |
Total release size: 87.9 kB
Release files / bellwether_mcp-1.3.5.tar.gz
| Download URL | bellwether_mcp-1.3.5.tar.gz |
|---|---|
| Size | 37.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f5e327e1ee86079b92eb5e6c3345ece153352d0c4801ae6ff3cb62b544a3d646
|
|
BLAKE2b-256 checksum How to use checksums |
f5d2d55eb791b12e7529e142f43866b0eeacf452731df9aa4c49fdbf5d4e2036
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Release files / bellwether_mcp-1.3.5-py3-none-any.whl
| Download URL | bellwether_mcp-1.3.5-py3-none-any.whl |
|---|---|
| Size | 50.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fb8af88b7ca6d4be0b114973d4881f8eb2f04ef32a137176d031ec2f2cd2d7e7
|
|
BLAKE2b-256 checksum How to use checksums |
d97f3b229bac7005fe0376778b24c8560f25751c4980157b4033ba8a7f7ce040
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for bellwether-mcp 1.3.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
