About viewdaily
viewdaily is a local MCP bridge and CLI for read-only daily research across assets, macro themes, and central banks. It forwards FinChiefs tools, which organize research from more than 200 providers and link back to source publications.
Key features
- 01Browse followed research providers
- 02Summarize asset and macro views
- 03Search directional asset and macro views
- 04Find research publications by topic
- 05Retrieve daily digests and policy signals
Use cases
- 01Review daily views on an asset category
- 02Compare provider leanings on a macro theme
- 03Find central-bank decisions and guidance
MCP support
It exposes the captured FinChiefs tool list through a local MCP server and forwards calls to the hosted MCP endpoint, passing successful results through unchanged.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
8Saved tool list · updated 1w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| limit | integer | No | Default 100. |
| query | string | No | Part of the provider name, e.g. "ECB" or "Federal Reserve". Omit to list all. |
Details
From the project READMEviewdaily
viewdaily is a small local bridge to FinChiefs' hosted MCP server, which collects daily research from more than 200 providers - banks, asset managers, central banks, multilaterals and independent researchers - and distils it into directional views on assets, macro themes, written daily digests and structured central-bank policy signals, each with a link back to the source publication.
The bridge keeps no research data of its own. It serves the upstream server's tool list locally, exactly as captured from the live endpoint, and forwards each tool call upstream, returning the result untouched. The whole captured surface is read-only: nothing here places orders, moves money or sends anything anywhere.
Tools
list_providers- the providers the service follows. Optional:query(part of a provider name) andlimit(1-300, default 100). A provideridfrom here limits the other tools to one source.list_categories- asset digest categories (such as gold, oil, us_bonds, eurusd) and macro categories (such as monetary_policy, geopolitics). Keys flagged with a daily digest work withget_daily_digests; macro keys also filtersearch_macro_viewsandsummarize_views. No arguments.summarize_views- the overall picture from every matching view in one small response: totals, up/down counts, provider leanings, busiest providers, a week-by-week trend and the most-discussed subjects. Required:kind(assetormacro). Optional:terms,asset_class,category,provider_id,since,until.search_asset_views- individual directional (up/down) views on assets, with provider, date, horizon, rationale and source link, paged viaoffset/next_offsetand spread across providers by default.search_macro_views- individual macro themes and drivers from provider research, each with a description and source link, paged the same way.search_research- research publications (articles, reports, podcasts) with title, provider, date, a short description and the link to the original, ranked by term match then newest.get_daily_digests- daily summaries written from all providers' views for a category, with the day's up/down tallies. Required:categories(1-10 category keys, e.g.["gold"], or["__overall__"]for the cross-asset summary).get_policy_signals- structured reads of central-bank and multilateral publications: decisions, stance (-2 dovish to +2 hawkish), guidance, conditions, speaker and forecasts, newest first.
Configuration
FINCHIEFS_MCP_URL(optional) - override the upstream endpoint. Defaults tohttps://finchiefs.com/api/mcp. (The override hook is this rebuild's own labelled reconstruction.)FINCHIEFS_API_KEY(optional) - when set, every upstream request carries anAuthorization: Bearer <key>header. When it is not set, no auth header is sent. (This forwarding is also a labelled reconstruction; the original surface was captured keyless.)
Forwarding mechanics
On the first tool call the client opens a streamable
HTTP session with the upstream: a JSON-RPC initialize
request (protocolVersion 2025-03-26, clientInfo name
viewdaily), then a notifications/initialized
notification, then the tools/call request carrying
the caller's arguments unchanged. When the upstream
answers initialize with an Mcp-Session-Id header,
that value rides on every later request of the session,
which is reused for the life of the process. Replies
may arrive as plain JSON or as server-sent events;
both are read.
Successful upstream results pass through verbatim,
including any isError flag the upstream sets.
Failures - a JSON-RPC error, a non-2xx status, an
unreadable response, or a request that cannot be
completed - come back as an isError result whose
text starts with viewdaily error: (this rendering
is this rebuild's own labelled reconstruction).
CLI
Each tool is also a subcommand taking one JSON argument string (omit it for tools that take none):
npx @reneturcios/viewdaily list_providers '{"query":"ECB"}'
npx @reneturcios/viewdaily summarize_views '{"kind":"asset","terms":["gold"]}'
npx @reneturcios/viewdaily get_daily_digests '{"categories":["gold"]}'
npx @reneturcios/viewdaily list_categories
npx @reneturcios/viewdaily --version
Exit codes: 0 on success, 1 on an isError
result, 2 on a usage error.
MCP server
npx -y @reneturcios/viewdaily mcp
MCP client config:
{
"mcpServers": {
"viewdaily": {
"command": "npx",
"args": ["-y", "@reneturcios/viewdaily", "mcp"]
}
}
}
Docker
docker run -i ghcr.io/cloudcorprecords/viewdaily
docker run --rm ghcr.io/cloudcorprecords/viewdaily --version
The container's default command is mcp, so the first
form is a stdio MCP server; any other arguments reach
the CLI normally.
Development
npm install
npm run build
npm test
npm run dev
The test suite runs entirely against a stubbed JSON-RPC upstream - no live network calls.
License
MIT - see LICENSE.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.