Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Viewdaily

by CloudCorpRecordsversion 0.1.0i★ –iRuns on your computer
Registry nameio.github.CloudCorpRecords/viewdaily

Install

Overview

Description from the maker (original English)

Daily research views on assets, macro themes and central banks from 200+ sources.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "viewdaily": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/viewdaily",
        "mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add viewdaily -- npx -y @reneturcios/viewdaily mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "viewdaily": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/viewdaily",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "viewdaily": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/viewdaily",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

  • More stars than 0% of the other 7232 servers in this category
  • Published to the registry more recently than 94% of the other 7232 servers in this category
  • Basic checks equal to or better than 100% of the other 7232 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Viewdaily safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 2 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated 3 days ago
Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago
Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated 44 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

viewdaily

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) and limit (1-300, default 100). A provider id from 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 with get_daily_digests; macro keys also filter search_macro_views and summarize_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 (asset or macro). 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 via offset / next_offset and 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 to https://finchiefs.com/api/mcp. (The override hook is this rebuild's own labelled reconstruction.)
  • FINCHIEFS_API_KEY (optional) - when set, every upstream request carries an Authorization: Bearer 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.

Ask PopNx