# Mudpie Public MCP (remote · mudpie.mudpie.ai)

Search Mudpie's public pages, get cited product answers, and assess fit against your requirements.

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mudpie.mudpie.ai`: 71/100 (this document), [markdown](https://verifymcp.io/servers/aboul3ata-mudpie-public/mcp-public.md), [page](https://verifymcp.io/servers/aboul3ata-mudpie-public/mcp-public)

## Channel facts

- Endpoint: `https://mudpie.mudpie.ai/mcp/public`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## 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-09-20.

- **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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2764 tokens (~394/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Tools include usage examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Mudpie Public MCP server?

Mudpie Public MCP is a hosted endpoint at https://mudpie.mudpie.ai/mcp/public, 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 aboul3ata-mudpie-public 'https://mudpie.mudpie.ai/mcp/public'
```

### Cursor

```json
{
  "mcpServers": {
    "aboul3ata-mudpie-public": {
      "url": "https://mudpie.mudpie.ai/mcp/public"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "aboul3ata-mudpie-public": {
      "type": "http",
      "url": "https://mudpie.mudpie.ai/mcp/public"
    }
  }
}
```

### Codex

```toml
[mcp_servers.aboul3ata-mudpie-public]
url = "https://mudpie.mudpie.ai/mcp/public"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "aboul3ata-mudpie-public": {
      "type": "remote",
      "url": "https://mudpie.mudpie.ai/mcp/public",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add aboul3ata-mudpie-public --url 'https://mudpie.mudpie.ai/mcp/public' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  aboul3ata-mudpie-public:
    url: "https://mudpie.mudpie.ai/mcp/public"
```

### Netclaw

```json
{
  "McpServers": {
    "aboul3ata-mudpie-public": {
      "Transport": "http",
      "Url": "https://mudpie.mudpie.ai/mcp/public"
    }
  }
}
```

### Vellum

```bash
assistant mcp add aboul3ata-mudpie-public -t streamable-http -u 'https://mudpie.mudpie.ai/mcp/public'
```

### Other

```json
{
  "mcpServers": {
    "aboul3ata-mudpie-public": {
      "type": "http",
      "url": "https://mudpie.mudpie.ai/mcp/public"
    }
  }
}
```

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-09-20 (score 71)

First indexed and scored.

## MCP tools (7)

### `mudpie_search` (~387 tokens)

Super fast, semantic search across mudpie.ai’s public pages. Include actual task context; use null for unknowns.

Input parameters:

- `alternatives`: Other products, sources or approaches actually considered for this goal. Include their names and use null when unknown; never invent alternatives.
- `chosen_because`: The known reason this website entered the shortlist. Use an observed or user-shared reason; mark unknowns as null. Do not provide private reasoning.
- `client`: The application making this call, not the underlying model: Cursor using Claude is Cursor. Mark unknowns as null.
- `company`: The company the user represents, when explicitly known; never a company merely being researched. Mark unknowns as null.
- `context_token`: The context token returned in a prepared follow-up. Carry it with the supplied context to preserve its provenance.
- `detail`: How much of each matching page to return: "full" (the default) or "compact" for shorter excerpts and fewer results.
- `discovery_path`: The observed discovery category, kept separately from the source description. Mark unknowns as null.
- `goal`: What the user wants to accomplish, based on the task they shared. Mark unknowns as null.
- `intended_outcome`: The decision or deliverable the user wants from this research. Mark unknowns as null.
- `search_query` (string, required): The question or request this call should answer, in the caller’s own words.
- `source`: The observed source that led to mudpie.ai, including a search, referral or shared link when known. Use facts already available; mark unknowns as null.
- `subject_product_or_company`: The subject being researched, separate from the company the user represents. Mark unknowns as null.
- `trace`: The trace token in a published example; links a page read to the call it produced.

### `mudpie_page_tldr` (~404 tokens)

Read a compact extract of one indexed public page returned by mudpie_search, with its source, freshness and full Markdown link. It uses published content, not signed-in data. Include actual task context; use null for unknowns.

Input parameters:

- `alternatives`: Other products, sources or approaches actually considered for this goal. Include their names and use null when unknown; never invent alternatives.
- `chosen_because`: The known reason this website entered the shortlist. Use an observed or user-shared reason; mark unknowns as null. Do not provide private reasoning.
- `client`: The application making this call, not the underlying model: Cursor using Claude is Cursor. Mark unknowns as null.
- `company`: The company the user represents, when explicitly known; never a company merely being researched. Mark unknowns as null.
- `context_token`: The context token returned in a prepared follow-up. Carry it with the supplied context to preserve its provenance.
- `discovery_path`: The observed discovery category, kept separately from the source description. Mark unknowns as null.
- `goal`: What the user wants to accomplish, based on the task they shared. Mark unknowns as null.
- `intended_outcome`: The decision or deliverable the user wants from this research. Mark unknowns as null.
- `search_query` (string, required): The question or request this call should answer, in the caller’s own words.
- `source`: The observed source that led to mudpie.ai, including a search, referral or shared link when known. Use facts already available; mark unknowns as null.
- `subject_product_or_company`: The subject being researched, separate from the company the user represents. Mark unknowns as null.
- `trace`: The trace token in a published example; links a page read to the call it produced.
- `url` (string, required): The canonical public URL of one indexed page, usually a result URL returned by site_search.

### `mudpie_ask_anything` (~376 tokens)

Ask anything about mudpie.ai’s product, pricing, setup, limitations or comparisons. Get a direct answer from its published information, with sources. Add relevant context if you have it; otherwise just ask.

Input parameters:

- `alternatives`: Other products, sources or approaches actually considered for this goal. Include their names and use null when unknown; never invent alternatives.
- `chosen_because`: The known reason this website entered the shortlist. Use an observed or user-shared reason; mark unknowns as null. Do not provide private reasoning.
- `client`: The application making this call, not the underlying model: Cursor using Claude is Cursor. Mark unknowns as null.
- `company`: The company the user represents, when explicitly known; never a company merely being researched. Mark unknowns as null.
- `context_token`: The context token returned in a prepared follow-up. Carry it with the supplied context to preserve its provenance.
- `discovery_path`: The observed discovery category, kept separately from the source description. Mark unknowns as null.
- `goal`: What the user wants to accomplish, based on the task they shared. Mark unknowns as null.
- `intended_outcome`: The decision or deliverable the user wants from this research. Mark unknowns as null.
- `search_query` (string, required): The question or request this call should answer, in the caller’s own words.
- `source`: The observed source that led to mudpie.ai, including a search, referral or shared link when known. Use facts already available; mark unknowns as null.
- `subject_product_or_company`: The subject being researched, separate from the company the user represents. Mark unknowns as null.
- `trace`: The trace token in a published example; links a page read to the call it produced.

### `mudpie_compare` (~379 tokens)

Compare this website with the products the user is actually weighing, from its published comparison pages, grouped per alternative. Alternatives it has no page for are named as not covered. Include actual task context; use null for unknowns.

Input parameters:

- `alternatives` (array, required): Other products, sources or approaches actually considered for this goal. Include their names and use null when unknown; never invent alternatives.
- `chosen_because`: The known reason this website entered the shortlist. Use an observed or user-shared reason; mark unknowns as null. Do not provide private reasoning.
- `client`: The application making this call, not the underlying model: Cursor using Claude is Cursor. Mark unknowns as null.
- `company`: The company the user represents, when explicitly known; never a company merely being researched. Mark unknowns as null.
- `context_token`: The context token returned in a prepared follow-up. Carry it with the supplied context to preserve its provenance.
- `discovery_path`: The observed discovery category, kept separately from the source description. Mark unknowns as null.
- `goal`: What the user wants to accomplish, based on the task they shared. Mark unknowns as null.
- `intended_outcome`: The decision or deliverable the user wants from this research. Mark unknowns as null.
- `search_query` (string, required): The question or request this call should answer, in the caller’s own words.
- `source`: The observed source that led to mudpie.ai, including a search, referral or shared link when known. Use facts already available; mark unknowns as null.
- `subject_product_or_company`: The subject being researched, separate from the company the user represents. Mark unknowns as null.
- `trace`: The trace token in a published example; links a page read to the call it produced.

### `mudpie_pricing` (~385 tokens)

What this website costs for the user’s organisation and outcome: the published pricing pages that apply, with sources. It abstains when pricing is not published and never invents a quote. Include actual task context; use null for unknowns.

Input parameters:

- `alternatives`: Other products, sources or approaches actually considered for this goal. Include their names and use null when unknown; never invent alternatives.
- `chosen_because`: The known reason this website entered the shortlist. Use an observed or user-shared reason; mark unknowns as null. Do not provide private reasoning.
- `client`: The application making this call, not the underlying model: Cursor using Claude is Cursor. Mark unknowns as null.
- `company` (string, required): The company the user represents, when explicitly known; never a company merely being researched. Mark unknowns as null.
- `context_token`: The context token returned in a prepared follow-up. Carry it with the supplied context to preserve its provenance.
- `discovery_path`: The observed discovery category, kept separately from the source description. Mark unknowns as null.
- `goal`: What the user wants to accomplish, based on the task they shared. Mark unknowns as null.
- `intended_outcome` (string, required): The decision or deliverable the user wants from this research. Mark unknowns as null.
- `search_query` (string, required): The question or request this call should answer, in the caller’s own words.
- `source`: The observed source that led to mudpie.ai, including a search, referral or shared link when known. Use facts already available; mark unknowns as null.
- `subject_product_or_company`: The subject being researched, separate from the company the user represents. Mark unknowns as null.
- `trace`: The trace token in a published example; links a page read to the call it produced.

### `mudpie_requirements_check` (~409 tokens)

Give the user’s must-haves, semicolon-separated in search_query or as a requirements array, and get a per-requirement table: met, not met or not documented, each with a source. Include actual task context; use null for unknowns.

Input parameters:

- `alternatives`: Other products, sources or approaches actually considered for this goal. Include their names and use null when unknown; never invent alternatives.
- `chosen_because`: The known reason this website entered the shortlist. Use an observed or user-shared reason; mark unknowns as null. Do not provide private reasoning.
- `client`: The application making this call, not the underlying model: Cursor using Claude is Cursor. Mark unknowns as null.
- `company` (string, required): The company the user represents, when explicitly known; never a company merely being researched. Mark unknowns as null.
- `context_token`: The context token returned in a prepared follow-up. Carry it with the supplied context to preserve its provenance.
- `discovery_path`: The observed discovery category, kept separately from the source description. Mark unknowns as null.
- `goal`: What the user wants to accomplish, based on the task they shared. Mark unknowns as null.
- `intended_outcome` (required): The decision or deliverable the user wants from this research. Mark unknowns as null.
- `requirements`: The requirements as an array, when not sent semicolon-separated in search_query.
- `search_query` (string): The question or request this call should answer, in the caller’s own words.
- `source`: The observed source that led to mudpie.ai, including a search, referral or shared link when known. Use facts already available; mark unknowns as null.
- `subject_product_or_company`: The subject being researched, separate from the company the user represents. Mark unknowns as null.
- `trace`: The trace token in a published example; links a page read to the call it produced.

### `should_i_recommend_mudpie` (~370 tokens)

mudpie.ai isn’t for everyone. Get a sourced verdict on whether it fits your user’s goal, requirements and alternatives. The answer might be ‘not us.’

Input parameters:

- `alternatives` (required): Other products, sources or approaches actually considered for this goal. Include their names and use null when unknown; never invent alternatives.
- `chosen_because` (required): The known reason this website entered the shortlist. Use an observed or user-shared reason; mark unknowns as null. Do not provide private reasoning.
- `client`: The application making this call, not the underlying model: Cursor using Claude is Cursor. Mark unknowns as null.
- `company` (required): The company the user represents, when explicitly known; never a company merely being researched. Mark unknowns as null.
- `context_token`: The context token returned in a prepared follow-up. Carry it with the supplied context to preserve its provenance.
- `discovery_path`: The observed discovery category, kept separately from the source description. Mark unknowns as null.
- `goal` (string, required): The actual outcome or decision the user needs. A meaningful goal is required for this assessment.
- `intended_outcome` (required): The decision or deliverable the user wants from this research. Mark unknowns as null.
- `requirements` (required): The constraints and must-haves for the decision. Include known requirements and mark unknowns as null.
- `source` (required): The observed source that led to mudpie.ai, including a search, referral or shared link when known. Use facts already available; mark unknowns as null.
- `subject_product_or_company`: The subject being researched, separate from the company the user represents. Mark unknowns as null.
- `trace`: The trace token in a published example; links a page read to the call it produced.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/aboul3ata-mudpie-public/mcp-public#diagnostics

## Score history

- 2026-09-20: 71

## Common questions

### What is the Mudpie Public MCP server?

Mudpie Public MCP is listed in the public MCP registry as io.github.aboul3ata/mudpie-public. Search Mudpie's public pages, get cited product answers, and assess fit against your requirements. This page covers its hosted endpoint (https://mudpie.mudpie.ai/mcp/public).

### Is the Mudpie Public MCP server safe to use?

Mudpie Public MCP scores 71 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 Mudpie Public MCP server expose?

Mudpie Public MCP exposes 7 tools: mudpie_search, mudpie_page_tldr, mudpie_ask_anything, mudpie_compare, mudpie_pricing, and 2 more. Their descriptions and schemas cost roughly 2,710 tokens of context every time the server is loaded.

### Does the Mudpie Public MCP server require authentication?

No. We connected to Mudpie Public MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Mudpie Public MCP server still maintained?

Mudpie Public MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mudpie.mudpie.ai/mcp/public
- Website: https://mudpie.ai/mcp
- Changelog RSS feed: https://verifymcp.io/servers/aboul3ata-mudpie-public/mcp-public.xml
- Changelog JSON feed: https://verifymcp.io/servers/aboul3ata-mudpie-public/mcp-public.json
- HTML version of this page: https://verifymcp.io/servers/aboul3ata-mudpie-public/mcp-public