Mudpie Public MCP
REMOTE · MUDPIE.MUDPIE.AI
Search Mudpie's public pages, get cited product answers, and assess fit against your requirements.
Available components
Last scanned (22 hours ago)
Scores higher than 8% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Search and Retrieval
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 10 Oct 26 −57
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.63 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 9 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 63. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 53. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- New tool “mudpie_feedback” functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: mudpie.ai → Mudpie security
- Tool “mudpie_ask_anything” rewrote its description, which is the text the model reads security
- Tool “mudpie_search” rewrote its description, which is the text the model reads security
- Tool “should_i_recommend_mudpie” rewrote its description, which is the text the model reads security
- “mudpie_ask_anything” reworded the description of “source” cosmetic
- “mudpie_compare” reworded the description of “source” cosmetic
- “mudpie_page_tldr” reworded the description of “source” cosmetic
- “mudpie_pricing” reworded the description of “source” cosmetic
- “mudpie_requirements_check” reworded the description of “source” cosmetic
- “mudpie_search” reworded the description of “source” cosmetic
- “should_i_recommend_mudpie” reworded the description of “source” cosmetic
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 4 Nov 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 | 1814, 3799 | 8, 8 | Verified |
| mudpie.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 308 |
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 | Redirected | 308 | https://app.thelazyweb.com:443/mcp/public |
| 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 ~374
Ask anything about Mudpie’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, 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 after reading its public information","client":"Cursor","company":"Acme","goal":"Decide whether Mudpie meets our team's needs","intended_outcome":"Choose a next step for an evaluation","search_query":"What does Mudpie offer, who is it for, and what does it not cover?","source":"Found Mudpie while researching options for our team"}mudpie_compare ~376
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 | – | 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, 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 after reading its public information","client":"Cursor","company":"Acme","goal":"Decide whether Mudpie meets our team's needs","intended_outcome":"Choose a next step for an evaluation","search_query":"How does Mudpie compare for our team's use case?","source":"Found Mudpie while researching options for our team"}mudpie_feedback ~213
Report a bug, a missing feature, a wrong answer or unclear docs in Mudpie’s agent tools, right when you hit it. Only kind and message are required. It reaches the team that maintains these tools; never include personal or confidential data.
| Name | Type | Req | Description |
|---|---|---|---|
| client | – | – | The application or client sending this, not the underlying model, e.g. Cursor. Null when unknown. |
| expected | – | – | What you expected or needed instead. Null when not applicable. |
| kind | string | yes | bug: a tool failed or behaved unexpectedly. missing_feature: a tool, field or capability you needed does not exist. wrong_answer: a result was inaccurate or unsupported. docs: documentation or a sche… |
| message | string | yes | What happened or what is missing, specifically enough to act on. |
| operation_id | – | – | The operation_id or attempt_id of the response this is about. Null when none. |
| tool | – | – | The tool name or HTTP operation this is about. Null when general. |
No output schema declared.
{"client":null,"expected":"A date filter on search results.","kind":"missing_feature","message":"mudpie_search cannot limit results to pages updated in the last year.","operation_id":null,"tool":"mudpie_search"}mudpie_page_tldr ~416
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. Only url is required. Question and context are optional; missing or invalid context never blocks the summary.
| 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 or client making this call, not the underlying model, e.g. Cursor. Null when unknown. |
| 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 | – | – | The caller’s question, when supplied. Optional; the stored summary depends only on url. |
| source | – | – | The observed source that led to Mudpie, 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. The only required field. |
No output schema declared.
{"trace":"t_5ba822689c76","url":"https://mudpie.ai/"}mudpie_pricing ~380
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 | – | 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. |
| 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, 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 after reading its public information","client":"Cursor","company":"Acme","goal":"Decide whether Mudpie meets our team's needs","intended_outcome":"Budget approval for a team purchase","search_query":"What would Mudpie cost for a team of five?","source":"Found Mudpie while researching options for our team"}mudpie_requirements_check ~406
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 | – | 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, 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 after reading its public information","client":"Cursor","company":"Acme","goal":"Decide whether Mudpie meets our team's needs","intended_outcome":"A vendor shortlist","search_query":"Mudpie works with our existing tools; clear documentation; a published price","source":"Found Mudpie while researching options for our team"}mudpie_search ~385
Super fast, semantic search across Mudpie’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, 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 after reading its public information","client":"Cursor","company":"Acme","goal":"Decide whether Mudpie meets our team's needs","intended_outcome":"Choose a next step for an evaluation","search_query":"What does Mudpie offer, who is it for, and what does it not cover?","source":"Found Mudpie while researching options for our team"}mudpie_sign_up ~400
Email the user a Mudpie sign-in link to start a free account. Submit only an email address the user authorized. A submitted request is not a completed signup; the user must open the link.
| 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 or client making this call, not the underlying model, e.g. Cursor. Null when unknown. |
| 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. |
| idempotency_key | string | yes | Generate one UUID for this authorized submission and reuse it on retries. |
| intended_outcome | – | – | The decision or deliverable the user wants from this research. Mark unknowns as null. |
| payload | object | yes | – |
| 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, 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.
No examples provided.
should_i_recommend_mudpie ~368
Mudpie 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, 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 after reading its public information","client":"Cursor","company":"Acme","goal":"Decide whether Mudpie 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 while researching options for our team"}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'
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 23 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 9 tools: mudpie_search, mudpie_page_tldr, mudpie_ask_anything, mudpie_compare, mudpie_pricing, and 4 more. Their descriptions and schemas cost roughly 3,318 tokens of context every time the server is loaded.
Does the Mudpie Public MCP server require authentication?
Its publisher declares no required credentials for Mudpie Public MCP. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.