Research and capability layer
nexus-core is a Python research engine with public APIs and MCP-compatible tools for regime, scoring, market, economic, options, on-chain, liquidity-pool, benchmark, and planning-oriented analysis.
Role in the system
This repository supplies analytical capabilities to the broader system. It can be called by human-facing applications or agent runtimes, but its outputs remain analytical inputs for review—not autonomous advice, trade instructions, or authority over client assets.
Current repository posture: The README distinguishes the open methodology and public interfaces from private production data sources and infrastructure. Capability coverage changes as the project evolves.
Inspectable capabilities
Each capability is paired with a concrete inspection test. If the source does not support the claim, the page should change.
The README enumerates public metadata, regime, scoring, market, economic, options, on-chain, liquidity-pool, benchmark, and planning surfaces.
Check: Compare the README public API table with the package exports and route/tool definitions. Missing or divergent entries invalidate the inventory.
A public server path exposes research capabilities through the Model Context Protocol for compatible clients.
Check: Inspect the MCP server and tool definitions, then confirm that a listed tool has a typed implementation and documented inputs.
Optional dependency groups let adopters install capability subsets instead of the full analytical dependency surface.
Check: Inspect pyproject.toml and run the documented modular install paths. If extras do not map to the stated capabilities, the claim fails.
The repository separates implemented integrations from credited academic and open-source foundations.
Check: Inspect the README lineage sections and source comments. An uncited borrowed method or overstated original contribution is a defect.
Primary sources
Repository README →
Status, public API, architecture, installation, and open-versus-private boundary.
Python source →
The package implementations behind the documented capability surface.
Examples →
Runnable usage paths and integration examples.
Security policy →
The repository reporting and security boundary.
System of systems
Reality check
The repository is open-source software provided under its stated license and without warranty. It is not investment, legal, tax, or cybersecurity advice. Protocol Wealth is an investment adviser, not a software vendor; publishing this code does not create a support, hosting, or implementation agreement.
Next
Start with the README, inspect the implementation and validation paths, and open an issue in the repository if the public description and source do not agree.