Mudpie Public MCP
REMOTE · MUDPIE.MUDPIE.AI · SCANNED SEP 20
Search Mudpie's public pages, get cited product answers, and assess fit against your requirements.
Available components
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Tools include usage examples.Pass
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
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.
remote · mudpie.mudpie.ai
claude mcp add --transport http aboul3ata-mudpie-public 'https://mudpie.mudpie.ai/mcp/public'
{
"mcpServers": {
"aboul3ata-mudpie-public": {
"url": "https://mudpie.mudpie.ai/mcp/public"
}
}
} {
"servers": {
"aboul3ata-mudpie-public": {
"type": "http",
"url": "https://mudpie.mudpie.ai/mcp/public"
}
}
} [mcp_servers.aboul3ata-mudpie-public] url = "https://mudpie.mudpie.ai/mcp/public"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"aboul3ata-mudpie-public": {
"type": "remote",
"url": "https://mudpie.mudpie.ai/mcp/public",
"enabled": true
}
}
} openclaw mcp add aboul3ata-mudpie-public --url 'https://mudpie.mudpie.ai/mcp/public' --transport streamable-http
mcp_servers:
aboul3ata-mudpie-public:
url: "https://mudpie.mudpie.ai/mcp/public" {
"McpServers": {
"aboul3ata-mudpie-public": {
"Transport": "http",
"Url": "https://mudpie.mudpie.ai/mcp/public"
}
}
} assistant mcp add aboul3ata-mudpie-public -t streamable-http -u 'https://mudpie.mudpie.ai/mcp/public'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 71
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mudpie.mudpie.ai/mcp/public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.mudpie.ai | CN=WR3,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | RSA 2048 | SHA256-RSA | b48eb0421ed2f1fd099669126fd5b564 |
| SANs: *.mudpie.ai | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mudpie.mudpie.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| mudpie.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mudpie.mudpie.ai/mcp/public | Verified | 200 | |
| http (plaintext) | http://mudpie.mudpie.ai/mcp/public | HTTPS enforced | 308 | https://mudpie.mudpie.ai:443/mcp/public |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
mudpie_ask_anything ~376
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
{"alternatives":["Our existing workflow","Manual research"],"chosen_because":"Our team shortlisted mudpie.ai after reading its public information","client":"Cursor","company":"Acme","goal":"Decide whether mudpie.ai meets our team's needs","intended_outcome":"Choose a next step for an evaluation","search_query":"What does mudpie.ai offer, who is it for, and what does it not cover?","source":"Found mudpie.ai while researching options for our team"}mudpie_compare ~379
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.
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | array | yes | 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 | yes | 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. |
No output schema declared.
{"alternatives":["Our current tool"],"chosen_because":"Our team shortlisted mudpie.ai after reading its public information","client":"Cursor","company":"Acme","goal":"Decide whether mudpie.ai meets our team's needs","intended_outcome":"Choose a next step for an evaluation","search_query":"How does mudpie.ai compare for our team's use case?","source":"Found mudpie.ai while researching options for our team"}mudpie_page_tldr ~404
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | The canonical public URL of one indexed page, usually a result URL returned by site_search. |
No output schema declared.
{"alternatives":["Our existing workflow","Manual research"],"chosen_because":"Our team shortlisted mudpie.ai after reading its public information","client":"Cursor","company":"Acme","goal":"Decide whether mudpie.ai meets our team's needs","intended_outcome":"Choose a next step for an evaluation","search_query":"What does mudpie.ai offer, who is it for, and what does it not cover?","source":"Found mudpie.ai while researching options for our team","url":"https://mudpie.ai/"}mudpie_pricing ~385
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | The decision or deliverable the user wants from this research. Mark unknowns as null. |
| search_query | string | yes | 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. |
No output schema declared.
{"alternatives":["Our existing workflow","Manual research"],"chosen_because":"Our team shortlisted mudpie.ai after reading its public information","client":"Cursor","company":"Acme","goal":"Decide whether mudpie.ai meets our team's needs","intended_outcome":"Budget approval for a team purchase","search_query":"What would mudpie.ai cost for a team of five?","source":"Found mudpie.ai while researching options for our team"}mudpie_requirements_check ~409
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | – | yes | 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. |
No output schema declared.
{"alternatives":["Our existing workflow","Manual research"],"chosen_because":"Our team shortlisted mudpie.ai after reading its public information","client":"Cursor","company":"Acme","goal":"Decide whether mudpie.ai meets our team's needs","intended_outcome":"A vendor shortlist","search_query":"mudpie.ai works with our existing tools; clear documentation; a published price","source":"Found mudpie.ai while researching options for our team"}mudpie_search ~387
Super fast, semantic search across mudpie.ai’s public pages. Include actual task context; use null for unknowns.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
{"alternatives":["Our existing workflow","Manual research"],"chosen_because":"Our team shortlisted mudpie.ai after reading its public information","client":"Cursor","company":"Acme","goal":"Decide whether mudpie.ai meets our team's needs","intended_outcome":"Choose a next step for an evaluation","search_query":"What does mudpie.ai offer, who is it for, and what does it not cover?","source":"Found mudpie.ai while researching options for our team"}should_i_recommend_mudpie ~370
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.’
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | – | yes | Other products, sources or approaches actually considered for this goal. Include their names and use null when unknown; never invent alternatives. |
| chosen_because | – | yes | 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 | – | yes | 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 | yes | The actual outcome or decision the user needs. A meaningful goal is required for this assessment. |
| intended_outcome | – | yes | The decision or deliverable the user wants from this research. Mark unknowns as null. |
| requirements | – | yes | The constraints and must-haves for the decision. Include known requirements and mark unknowns as null. |
| source | – | yes | 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. |
No output schema declared.
{"alternatives":["Our existing workflow","Manual research"],"chosen_because":"Our team shortlisted mudpie.ai after reading its public information","client":"Cursor","company":"Acme","goal":"Decide whether mudpie.ai meets our team's needs","intended_outcome":"Choose a next step for an evaluation","requirements":["Relevant published capabilities","A clear way to evaluate the offering"],"source":"Found mudpie.ai while researching options for our team"}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.