Mudpie Public MCP

io.github.aboul3ataPublished by GitHub account aboul3atav0.1.0Updated Oct 24, 2026

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

The publisher's own server: Lazyweb Public Discovery

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

A remote MCP server that lets an assistant search Mudpie's public pages, get cited product answers, and assess fit against your requirements.

What you can do
Search Mudpie's public pages for relevant content and product information. Retrieve product answers that come with citations to the source pages. Assess whether Mudpie fits a set of stated requirements. No individual tools are listed, so exact operations are not documented.
When to use it
Useful when evaluating Mudpie as a product and you want an assistant to pull answers from its public site with citations, or to compare its offering against your requirements.
Requirements
A remote streamable HTTP endpoint at mudpie.mudpie.ai; no package, environment variables, or headers are declared. The manifest declares no authentication, so access may be open or handled by the endpoint itself. Network access to the endpoint is required.
Before you install
The server reads public pages and returns cited answers; no write, send, or delete actions are described. No credentials are requested in the manifest. Answers are limited to Mudpie's own public content, so treat fit assessments as vendor-sourced rather than independent.

Installation

In SourceWeft

  1. Open Mudpie Public MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.aboul3ata%2Fmudpie-public/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 20, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Lazyweb integrations