# The Daily Workflow — AI Tools & Free Alternatives (remote · thedailyworkflow.com)

Find free open-source replacements for paid software; search 15,000+ AI tools and MCP servers.

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `thedailyworkflow.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-thedailyworkflow-thedailyworkflow-mcp/api-v1-mcp-bridge.md), [page](https://verifymcp.io/servers/com-thedailyworkflow-thedailyworkflow-mcp/api-v1-mcp-bridge)

## Channel facts

- Endpoint: `https://thedailyworkflow.com/api/v1/mcp/bridge`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4683 tokens (~246/item across 19 items; 19 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the The Daily Workflow — AI Tools & Free Alternatives MCP server?

The Daily Workflow — AI Tools & Free Alternatives is a hosted endpoint at https://thedailyworkflow.com/api/v1/mcp/bridge, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-thedailyworkflow-thedailyworkflow-mcp 'https://thedailyworkflow.com/api/v1/mcp/bridge'
```

### Cursor

```json
{
  "mcpServers": {
    "com-thedailyworkflow-thedailyworkflow-mcp": {
      "url": "https://thedailyworkflow.com/api/v1/mcp/bridge"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-thedailyworkflow-thedailyworkflow-mcp": {
      "type": "http",
      "url": "https://thedailyworkflow.com/api/v1/mcp/bridge"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-thedailyworkflow-thedailyworkflow-mcp]
url = "https://thedailyworkflow.com/api/v1/mcp/bridge"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-thedailyworkflow-thedailyworkflow-mcp": {
      "type": "remote",
      "url": "https://thedailyworkflow.com/api/v1/mcp/bridge",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-thedailyworkflow-thedailyworkflow-mcp --url 'https://thedailyworkflow.com/api/v1/mcp/bridge' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-thedailyworkflow-thedailyworkflow-mcp:
    url: "https://thedailyworkflow.com/api/v1/mcp/bridge"
```

### Netclaw

```json
{
  "McpServers": {
    "com-thedailyworkflow-thedailyworkflow-mcp": {
      "Transport": "http",
      "Url": "https://thedailyworkflow.com/api/v1/mcp/bridge"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-thedailyworkflow-thedailyworkflow-mcp -t streamable-http -u 'https://thedailyworkflow.com/api/v1/mcp/bridge'
```

### Other

```json
{
  "mcpServers": {
    "com-thedailyworkflow-thedailyworkflow-mcp": {
      "type": "http",
      "url": "https://thedailyworkflow.com/api/v1/mcp/bridge"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-04 (score 71, −2)

- [security regression] HSTS header: unverified → fail
- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.10
- [functional improvement] MCP protocol: unverified → pass

### 2026-11-03 (score 73, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.03 → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-02 (score 73, +10)

- [security improvement] Authorization: unverified → partial
- [functional regression] Schema quality: 182 → 246
- [functional improvement] Tool coverage: 0% → 100%
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “build_custom_pipeline_url” reworded the description of “lang”
- [cosmetic] “build_custom_pipeline_url” reworded the description of “task”
- [cosmetic] “find_free_alternative” reworded the description of “product_name”
- [cosmetic] “get_ai_tool_details” reworded the description of “slug”
- [cosmetic] “get_mcp_details” reworded the description of “slug”
- [cosmetic] “get_mcp_install_config” reworded the description of “client”
- [cosmetic] “get_mcp_install_config” reworded the description of “slug”
- [cosmetic] “get_my_saved_tools” reworded the description of “api_key”
- [cosmetic] “get_my_stack_health” reworded the description of “api_key”
- [cosmetic] “get_pipeline_details” reworded the description of “lang”
- [cosmetic] “get_pipeline_details” reworded the description of “slug”
- [cosmetic] “get_popular_pipelines” reworded the description of “lang”
- [cosmetic] “get_popular_pipelines” reworded the description of “limit”
- [cosmetic] “get_tutorial_details” reworded the description of “lang”
- [cosmetic] “get_tutorial_details” reworded the description of “slug”
- [cosmetic] “search_ai_tools” reworded the description of “category”
- [cosmetic] “search_ai_tools” reworded the description of “limit”
- [cosmetic] “search_ai_tools” reworded the description of “pricing”
- [cosmetic] “search_ai_tools” reworded the description of “query”
- [cosmetic] “search_mcp_servers” reworded the description of “category”
- [cosmetic] “search_mcp_servers” reworded the description of “client”
- [cosmetic] “search_mcp_servers” reworded the description of “language”
- [cosmetic] “search_mcp_servers” reworded the description of “limit”
- [cosmetic] “search_mcp_servers” reworded the description of “query”
- [cosmetic] “search_mcp_tutorials” reworded the description of “category”
- [cosmetic] “search_mcp_tutorials” reworded the description of “difficulty”
- [cosmetic] “search_mcp_tutorials” reworded the description of “lang”
- [cosmetic] “search_mcp_tutorials” reworded the description of “limit”
- [cosmetic] “search_mcp_tutorials” reworded the description of “query”
- [cosmetic] “search_pipelines” reworded the description of “lang”
- [cosmetic] “search_pipelines” reworded the description of “limit”
- [cosmetic] “search_pipelines” reworded the description of “query”
- [cosmetic] “search_prompts” reworded the description of “ai_tool”
- [cosmetic] “search_prompts” reworded the description of “category”
- [cosmetic] “search_prompts” reworded the description of “limit”
- [cosmetic] “search_prompts” reworded the description of “query”
- [cosmetic] “search_qa_cases” reworded the description of “category”
- [cosmetic] “search_qa_cases” reworded the description of “lang”
- [cosmetic] “search_qa_cases” reworded the description of “limit”
- [cosmetic] “search_qa_cases” reworded the description of “query”
- [cosmetic] “search_qa_cases” reworded the description of “server”

### 2026-11-01 (score 63)

First indexed and scored.

## MCP tools (19)

### `find_free_alternative` (~239 tokens)

Find verified free open-source replacements for a paid AI product.

    Backed by the Swap Map at thedailyworkflow.com/alternatives — every
    replacement is checked by hand against live GitHub (stars, license,
    last push). Answer honestly from the returned status:
      - "covered": list the replacements (repo, stars, license,
        coverage full/partial, why_en, setup_level) and the money saved.
      - "checked_no_replacement": the product was audited and no
        verified free replacement exists yet — say exactly that.
      - "unknown": not audited yet; may include up to 3 covered
        "suggestions" nearby — present them as neighbours, NOT as
        replacements for this product.

    Args:
        product_name: Paid product name, e.g. "Midjourney", "Notion AI",
                      "Jasper". Case-insensitive.

Input parameters:

- `product_name` (string, required): Name of the paid product to find verified free open-source replacements for, e.g. "Midjourney", "Notion AI" or "Jasper". Case-insensitive.

### `search_mcp_servers` (~465 tokens)

Search the catalog of 3500+ MCP servers at thedailyworkflow.com.

    Args:
        query: Free-text search (matches name, description, keywords). Example: "notion", "postgres database".
        category: Filter by category. Common values: databases, web, filesystem, cloud,
                  productivity, communication, dev, ai, search, monitoring.
        client: Filter by supported MCP client. Values: claude-desktop, cursor, cline,
                windsurf, continue, goose.
        language: Filter by implementation language. Values: typescript, python, go, rust, java.
        limit: Max results to return (1-25, default 10).

    Returns:
        Dict with `count` and `results` (list of MCP server summaries).
        Each result has: slug, name, description, categories, language, transport,
        supported_clients, stars, repo_url, page_url (link to full info).

    Use this when the user asks for an MCP server matching some need ("find me an MCP for X",
    "what MCP servers work with Cursor", "Slack MCP servers"). After choosing a candidate,
    call get_mcp_install_config to get ready-to-paste setup.

Input parameters:

- `category` (string): Filter by MCP server category. Common values: "databases", "web", "filesystem", "cloud", "productivity", "communication", "dev", "ai", "search", "monitoring". Empty string means any category.
- `client` (string): Filter by supported MCP client. One of: "claude-desktop", "cursor", "cline", "windsurf", "continue", "goose". Empty string means any client.
- `language` (string): Filter by implementation language of the MCP server. One of: "typescript", "python", "go", "rust", "java". Empty string means any language.
- `limit` (integer): Maximum number of results to return (1-25; values outside the range are clamped). Default: 10.
- `query` (string): Free-text search query matched against MCP server name, description and keywords. Example: "notion", "postgres database". Empty string returns unfiltered results.

### `get_mcp_install_config` (~302 tokens)

Get a ready-to-paste install config for a specific MCP server and client.

    Args:
        slug: MCP server slug (from search_mcp_servers `slug` field). Example: "github-mcp".
        client: Target client. Values: claude-desktop, cursor, cline, windsurf, continue, goose.
                Default: claude-desktop.

    Returns:
        Dict with `config` (JSON snippet ready to paste into client's config file),
        `install_command` (e.g. `npx @x/y`), `available_clients` (which clients have configs),
        and `page_url`. If config for requested client is missing, `config` will be null —
        try a different client from `available_clients`.

    Use this AFTER finding an MCP via search. Show the user the exact config snippet plus
    the path to their client's config file (e.g. for Claude Desktop on macOS:
    ~/Library/Application Support/Claude/claude_desktop_config.json).

Input parameters:

- `client` (string): Target MCP client to generate the install config for. One of: "claude-desktop", "cursor", "cline", "windsurf", "continue", "goose". Default: "claude-desktop".
- `slug` (string, required): MCP server slug - take it from the `slug` field of search_mcp_servers results, e.g. "github-mcp".

### `get_mcp_details` (~156 tokens)

Get complete details for a specific MCP server: description, use cases, tools, install configs.

    Args:
        slug: MCP server slug.

    Returns:
        Full MCP record with description, long description, use_cases (list of scenarios),
        tools (what the server exposes), install_configs (per-client snippets),
        license, author, stars, page_url.

    Use this when the user wants to learn more about a specific MCP before installing,
    or when they ask "what does X MCP do" or "show me use cases for X".

Input parameters:

- `slug` (string, required): MCP server slug - take it from the `slug` field of search_mcp_servers results, e.g. "github-mcp".

### `list_mcp_categories` (~67 tokens)

List all MCP categories in the catalog with counts.

    Returns:
        Dict with `count` (total categories) and `categories` (list of {name, count}).

    Useful when the user wants to browse by category or asks "what kinds of MCP servers exist".

### `catalog_stats` (~71 tokens)

Stats about the MCP catalog at thedailyworkflow.com.

    Returns:
        total_servers (int), top_languages (list of {language, count}), catalog_url.

    Use this for context-setting questions like "how many MCP servers exist" or
    "what's the most popular language for MCP servers".

### `search_ai_tools` (~369 tokens)

Search 15000+ AI tools in the thedailyworkflow.com catalog.

    Args:
        query: Free-text search (matches name, description, tags). Example: "image generation",
               "transcription", "chatbot".
        category: Filter by category. Examples: "Image Generation", "Productivity",
                  "Code & Development", "Audio & Music", "Writing & Content".
        pricing: Filter by pricing model. Values: "Free", "Freemium", "Paid", "Enterprise".
        limit: Max results (1-25, default 10).

    Returns:
        Dict with `count` and `results`. Each result: slug, name, category, description,
        pricing, logo_url, official_url, page_url.

    Use this when the user asks for an AI tool for a specific task ("find me an AI for X",
    "what are good free AI tools for Y", "compare AI tools for Z"). Follow up with
    get_ai_tool_details for the chosen one.

Input parameters:

- `category` (string): Filter by AI tool category, e.g. "Image Generation", "Productivity", "Code & Development", "Audio & Music", "Writing & Content". Empty string means any category.
- `limit` (integer): Maximum number of results to return (1-25; values outside the range are clamped). Default: 10.
- `pricing` (string): Filter by pricing model. One of: "Free", "Freemium", "Paid", "Enterprise". Empty string means any pricing model.
- `query` (string): Free-text search query matched against AI tool name, description and tags. Example: "image generation", "transcription", "chatbot". Empty string returns unfiltered results.

### `get_ai_tool_details` (~154 tokens)

Full details for a specific AI tool: features, pricing, target audience, USP.

    Args:
        slug: Tool slug from search_ai_tools results (e.g. "chatgpt", "midjourney").

    Returns:
        Dict with full description, key_features, pricing_details, target_audience,
        unique_selling, tags, rating, page_url.

    Use this when the user wants deeper info on a tool before signing up — pricing
    breakdown, who it's for, what makes it different.

Input parameters:

- `slug` (string, required): AI tool slug - take it from the `slug` field of search_ai_tools results, e.g. "chatgpt" or "midjourney".

### `list_ai_tool_categories` (~56 tokens)

List all AI tool categories in the catalog with counts.

    Returns:
        Dict with `count` and `categories` (list of {name, count}).

    Useful when the user wants to browse tools by category.

### `search_pipelines` (~311 tokens)

Search 100+ ready-made AI workflow pipelines (step-by-step recipes).

    A pipeline is a complete plan: which AI tools to use in what order, with
    ready-to-paste prompts at each step, to accomplish a specific goal.

    Args:
        query: Free-text search over pipeline titles and queries. Examples: "podcast",
               "children book", "youtube channel automation".
        lang: Language for output ("en" or "ru"). Default: "en".
        limit: Max results (1-25, default 10).

    Returns:
        Dict with `count` and `results`. Each result: slug, title, goal, query,
        hits (popularity), step_count, page_url.

    Use this when the user describes a goal that involves multiple steps with multiple AI
    tools ("how do I make X using AI", "give me a workflow for Y"). After picking, call
    get_pipeline_details for full step-by-step plan with prompts.

Input parameters:

- `lang` (string): Output language: "en" for English or "ru" for Russian. Default: "en".
- `limit` (integer): Maximum number of results to return (1-25; values outside the range are clamped). Default: 10.
- `query` (string): Free-text search query matched against pipeline titles and the tasks they solve. Example: "podcast", "children book", "youtube channel automation". Empty string returns unfiltered results.

### `get_pipeline_details` (~167 tokens)

Full pipeline: title, goal, all steps with tools, instructions, prompts, pricing.

    Args:
        slug: Pipeline slug (from search_pipelines).
        lang: "en" or "ru" (default "en").

    Returns:
        Dict with title, goal, steps (each: step number, title, tool_name, tool_type,
        instruction, prompt_example, pricing, category, tool_url), step_count, page_url.

    Use this to give the user a complete actionable plan with copy-paste prompts.

Input parameters:

- `lang` (string): Output language: "en" for English or "ru" for Russian. Default: "en".
- `slug` (string, required): Pipeline slug - take it from the `slug` field of search_pipelines results.

### `get_popular_pipelines` (~152 tokens)

Top-N most-used pipelines by hit count — what other users have found valuable.

    Args:
        lang: "en" or "ru" (default "en").
        limit: Max results (1-25, default 10).

    Returns:
        Same shape as search_pipelines, sorted by hits descending.

    Use this for inspiration ("what can I do with AI?", "show me popular AI workflows").

Input parameters:

- `lang` (string): Output language: "en" for English or "ru" for Russian. Default: "en".
- `limit` (integer): Maximum number of results to return (1-25; values outside the range are clamped). Default: 10.

### `build_custom_pipeline_url` (~255 tokens)

For a custom task (no existing pipeline matches), get a deep link to the
    Pipeline Builder on thedailyworkflow.com.

    The builder composes a step-by-step pipeline from 15000+ AI tools with
    ready-to-paste prompts. The MCP server doesn't run it directly — it returns
    the prefilled URL where the user can run it.

    Args:
        task: Description of what the user wants to accomplish. Example:
              "create a YouTube channel with bedtime stories using AI for video and voice".
        lang: "en" or "ru" (default "en").

    Returns:
        Dict with builder_url (open this in browser), task (echoed), and a note explaining
        what happens.

    Use this when search_pipelines returns no good match. ALWAYS call search_pipelines first
    to check for existing solutions before suggesting the builder.

Input parameters:

- `lang` (string): Output language: "en" for English or "ru" for Russian. Default: "en".
- `task` (string, required): Plain-language description of what the user wants to accomplish, e.g. "create a YouTube channel with bedtime stories using AI for video and voice".

### `search_mcp_tutorials` (~465 tokens)

Search 147+ MCP tutorials covering install, configuration, comparison, build guides.

    Tutorials are curated step-by-step guides for installing and using MCP servers
    with specific clients (Claude Desktop, Cursor, Cline, Windsurf), best-of-category
    roundups, build-your-own-server walkthroughs, and concept explainers.

    Args:
        query: Free-text search over titles, summaries, keywords. Example: "cursor mcp",
               "build python mcp server", "windsurf vs cursor".
        category: Filter by category. Values: client_setup, category_best, build, usecase,
                  install, comparison, concept, general.
        difficulty: Filter by level. Values: beginner, intermediate, advanced.
        lang: Output language (en|ru). Default: en.
        limit: Max results (1-25, default 10).

    Returns:
        Dict with `count` and `results`. Each result: slug, title, summary,
        difficulty, category, tutorial_type, estimated_minutes, related_servers,
        page_url.

    Use this when the user asks "how do I install X MCP", "best MCPs for Cursor",
    "how to build my own MCP server", or hits an MCP setup problem. Follow up with
    get_tutorial_details(slug) for the full markdown.

Input parameters:

- `category` (string): Filter by tutorial category. One of: "client_setup", "category_best", "build", "usecase", "install", "comparison", "concept", "general". Empty string means any category.
- `difficulty` (string): Filter by tutorial difficulty. One of: "beginner", "intermediate", "advanced". Empty string means any difficulty.
- `lang` (string): Output language: "en" for English or "ru" for Russian. Default: "en".
- `limit` (integer): Maximum number of results to return (1-25; values outside the range are clamped). Default: 10.
- `query` (string): Free-text search query matched against tutorial titles, summaries and keywords. Example: "cursor mcp", "build python mcp server", "windsurf vs cursor". Empty string returns unfiltered results.

### `get_tutorial_details` (~191 tokens)

Full tutorial content (markdown) with all steps, code blocks, screenshots.

    Args:
        slug: Tutorial slug (from search_mcp_tutorials).
        lang: en | ru. Default: en.

    Returns:
        Dict with title, summary, content (full markdown), difficulty, category,
        target_client, target_server, target_category, estimated_minutes,
        word_count, views_count, page_url.

    Use this AFTER finding a relevant tutorial via search. The `content` field has
    full markdown — render it directly to the user, or extract the install commands
    / config snippets they asked about.

Input parameters:

- `lang` (string): Output language: "en" for English or "ru" for Russian. Default: "en".
- `slug` (string, required): Tutorial slug - take it from the `slug` field of search_mcp_tutorials results.

### `search_qa_cases` (~479 tokens)

Search 147+ Q&A cases — curated solutions to real GitHub Issues with MCP servers
    and AI tools. Each case is structured as: problem (symptom) → cause → solution
    (markdown with code).

    Use this FIRST when the user reports an error or unexpected behavior with an
    MCP server. Many common errors (timeouts, ESM/require issues, Windows path
    bugs, rate limits, connection failures) already have curated fixes.

    Args:
        query: Free-text search over title, problem, error keywords, tools used.
               Example: "ReadTimeout", "ESM require", "windows path", "rate limit".
        server: Filter by related MCP server slug. Example: "fastapi-mcp",
                "github-mcp-server".
        category: troubleshooting | install | config | usage. Default: any.
        lang: en | ru. Default: en.
        limit: Max results (1-25, default 10).

    Returns:
        Dict with `count` and `results`. Each result: slug, title, problem (preview),
        category, tools_used (list), error_keywords (list), related_server_slug,
        quality_score (0-10), helpful_count, page_url.

    The `slug` opens a full case at https://thedailyworkflow.com/qa/<slug> with the
    complete solution markdown.

Input parameters:

- `category` (string): Filter by case category. One of: "troubleshooting", "install", "config", "usage". Empty string means any category.
- `lang` (string): Output language: "en" for English or "ru" for Russian. Default: "en".
- `limit` (integer): Maximum number of results to return (1-25; values outside the range are clamped). Default: 10.
- `query` (string): Free-text search query matched against case title, problem text, error keywords and tools used. Example: "ReadTimeout", "ESM require", "windows path", "rate limit". Empty string returns unfiltered re…
- `server` (string): Filter by the MCP server the case is about, given as its slug, e.g. "fastapi-mcp" or "github-mcp-server". Empty string means any server.

### `search_prompts` (~427 tokens)

Search 1700+ user-submitted AI prompts for ChatGPT, Claude, Midjourney, DALL-E,
    Cursor, Gemini and more. Each prompt is a copy-paste-ready template for a
    specific task (writing, coding, marketing, design, business, etc).

    Args:
        query: Free-text search over title and prompt body. Example: "blog post outline",
               "code refactor", "logo design", "cold email".
        ai_tool: Filter by target AI. Values: ChatGPT, Claude, Midjourney, DALL-E 3,
                 Gemini, Cursor, Copilot.
        category: Filter by category. Values: Writing, Coding, Marketing, Design,
                  Business, Education, Creative, Productivity.
        limit: Max results (1-25, default 10).

    Returns:
        Dict with `count` and `results`. Each result: id, title, category, ai_tool,
        preview (first 200 chars of prompt), page_url.

    Use this when the user asks "give me a prompt for X" or "find a prompt to do Y".
    The full content is at the page_url.

Input parameters:

- `ai_tool` (string): Filter by the AI the prompt is written for. One of: "ChatGPT", "Claude", "Midjourney", "DALL-E 3", "Gemini", "Cursor", "Copilot". Empty string means any AI.
- `category` (string): Filter by prompt category. One of: "Writing", "Coding", "Marketing", "Design", "Business", "Education", "Creative", "Productivity". Empty string means any category.
- `limit` (integer): Maximum number of results to return (1-25; values outside the range are clamped). Default: 10.
- `query` (string): Free-text search query matched against prompt title and prompt text. Example: "blog post outline", "code refactor", "logo design", "cold email". Empty string returns unfiltered results.

### `get_my_saved_tools` (~221 tokens)

Return the saved AI tools ("My Workflow" stack) of the user who owns
    the given personal API key from thedailyworkflow.com.

    The user can generate the key on https://thedailyworkflow.com/my-workflow
    (section "Personal API key"). Ask the user for the key if you do not have it.

    Returns:
        Dict with `count` and `results`: each result has name, url (official
        site), page_url (catalog page), pricing and health (liveness status:
        alive / protected / slow / dead / unknown — re-checked every 4 hours).

    Use this when the user asks about "my tools", "my stack", "what did I save"
    in the context of TheDailyWorkflow.

Input parameters:

- `api_key` (string, required): Personal API key of the TheDailyWorkflow account, generated at https://thedailyworkflow.com/my-workflow (section "Personal API key"). It is sent as a Bearer token and selects whose saved tools are re…

### `get_my_stack_health` (~136 tokens)

Health summary of the user's saved stack on thedailyworkflow.com:
    how many of their tools are alive, protected, slow or dead, and which
    ones are dead. Needs the personal API key (see get_my_saved_tools).

    Use this when the user asks whether their tools are up, or wants a
    status report on their AI stack.

Input parameters:

- `api_key` (string, required): Personal API key of the TheDailyWorkflow account, generated at https://thedailyworkflow.com/my-workflow (section "Personal API key"). It is sent as a Bearer token and selects whose stack health is su…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-thedailyworkflow-thedailyworkflow-mcp/api-v1-mcp-bridge#diagnostics

## Score history

- 2026-11-05: 72
- 2026-11-04: 71
- 2026-11-03: 73
- 2026-11-02: 73
- 2026-11-01: 63

## Common questions

### What is the The Daily Workflow — AI Tools & Free Alternatives MCP server?

The Daily Workflow — AI Tools & Free Alternatives is an MCP server listed in the public MCP registry as com.thedailyworkflow/thedailyworkflow-mcp. Find free open-source replacements for paid software; search 15,000+ AI tools and MCP servers. This page covers its hosted endpoint (https://thedailyworkflow.com/api/v1/mcp/bridge).

### Is the The Daily Workflow — AI Tools & Free Alternatives MCP server safe to use?

The Daily Workflow — AI Tools & Free Alternatives scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the The Daily Workflow — AI Tools & Free Alternatives MCP server expose?

The Daily Workflow — AI Tools & Free Alternatives exposes 19 tools: find_free_alternative, search_mcp_servers, get_mcp_install_config, get_mcp_details, list_mcp_categories, and 14 more. Their descriptions and schemas cost roughly 4,683 tokens of context every time the server is loaded.

### Does the The Daily Workflow — AI Tools & Free Alternatives MCP server require authentication?

No. We connected to The Daily Workflow — AI Tools & Free Alternatives without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the The Daily Workflow — AI Tools & Free Alternatives MCP server still maintained?

The Daily Workflow — AI Tools & Free Alternatives is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the The Daily Workflow — AI Tools & Free Alternatives MCP server?

VerifyMCP ran 13 checks on The Daily Workflow — AI Tools & Free Alternatives, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://thedailyworkflow.com/api/v1/mcp/bridge
- Repository: https://github.com/vlsky2603/thedailyworkflow-mcp
- Website: https://thedailyworkflow.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-thedailyworkflow-thedailyworkflow-mcp/api-v1-mcp-bridge.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-thedailyworkflow-thedailyworkflow-mcp/api-v1-mcp-bridge/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-thedailyworkflow-thedailyworkflow-mcp/api-v1-mcp-bridge.json
- HTML version of this page: https://verifymcp.io/servers/com-thedailyworkflow-thedailyworkflow-mcp/api-v1-mcp-bridge