If you've been watching the MCP (Model Context Protocol) ecosystem from the sidelines, here's a quietly important detail: a lot of MCP servers are also just plain REST APIs underneath. The MCP layer is a polite wrapper that says "Claude, here are tools you can call." But the underlying HTTP endpoints are right there, ready to be called from requests.get(...) like any other JSON API.
That matters because the most interesting MCP servers are useful even if you've never opened Claude Desktop or Cursor. You can drop them into a Streamlit app, a Jupyter notebook, a Lambda function, a Discord bot, an Airflow DAG, or a cron job. The MCP integration is gravy on top.
I'll show this with a concrete example: pulling per-symbol ML option fair values and 31-dimension news-bias scores into pandas in 5 lines.
The setup
I run Helium MCP, which started as an MCP server and recently grew a plain REST surface. Both speak the same data:
