Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Mamanida Maternity Catalogue

REMOTE · MAMANIDA.COM · SCANNED OCT 4

Public read-only MCP server to discover and compare maternity and nursing fashion.

Available components

0 this week 78 Trust /100
Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1264 tokens (~252/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 81% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Mamanida Maternity Catalogue MCP server?

Mamanida Maternity Catalogue is a hosted endpoint at https://mamanida.com/mcp, 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 · mamanida.com

# add to Claude Code
claude mcp add --transport http com-mamanida-mamanida-mcp 'https://mamanida.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-mamanida-mamanida-mcp": {
      "url": "https://mamanida.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-mamanida-mamanida-mcp": {
      "type": "http",
      "url": "https://mamanida.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-mamanida-mamanida-mcp]
url = "https://mamanida.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mamanida-mamanida-mcp": {
      "type": "remote",
      "url": "https://mamanida.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-mamanida-mamanida-mcp --url 'https://mamanida.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-mamanida-mamanida-mcp:
    url: "https://mamanida.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-mamanida-mamanida-mcp": {
      "Transport": "http",
      "Url": "https://mamanida.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-mamanida-mamanida-mcp -t streamable-http -u 'https://mamanida.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-mamanida-mamanida-mcp": {
      "type": "http",
      "url": "https://mamanida.com/mcp"
    }
  }
}

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

Changelog

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.

  • 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
  • 27 Sept 26 +1

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

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1

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

  • 21 Sept 26 +1

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

  • 19 Sept 26 +1

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

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 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.

  • 15 Sept 26 +1

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

Diagnostics

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 Oct 2026 · Probed https://mamanida.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mamanida.com CN=WE1,O=Google Trust Services,C=US 1 Oct 2026 30 Dec 2026 ECDSA 256 ECDSA-SHA256 a8101be4ffbb295b1359d644f7300983
SANs: mamanida.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mamanida.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
mamanida.com. 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
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mamanida.com/mcp Verified 200
http (plaintext) http://mamanida.com/mcp HTTPS enforced 301 https://mamanida.com/mcp
MCP tools · 5 exposed · ~807 tokens

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 →

Tool Tokens
compare_products ~123

Compare 2-10 Mamanida products on one storefront. Each product is returned with the same public contract as get_product (localized details, availability, retailer-authoritative and displayed prices, AFFILIATE / DIRECT / BLOCKED commercial state and its canonical Mamanida URL), so prices and availability are directly comparable within that storefront.

NameTypeReqDescription
slugsarrayyesBetween 2 and 10 product slugs.
storefrontstringyesRequired storefront id, e.g. 'int', 'se', 'dk', 'no', 'fi', 'us'.

No output schema declared.

No examples provided.

get_guides ~236

Mamanida's editorial buying guides for one storefront, in that storefront's own language. Called without `guide` it lists the published guides (metadata only: title, deck, meta description, pillar, topics, dates and the canonical Mamanida URL), optionally filtered by `topic`. Called with `guide` (the guide slug from the listing) it returns that one localized edition plus its structured body: paragraphs, headings, lists, comparison tables, callouts, links to other guides and category calls-to-action. A `category_cta` gives a `category_slug` you can pass straight to search_products, which is the intended guide → category → product path. Retailer and affiliate URLs are never returned.

NameTypeReqDescription
guidestring–Guide slug as it appears in the Mamanida guide URL. Omit to list guides.
storefrontstringyesRequired storefront id, e.g. 'int' (English), 'se', 'dk', 'no', 'fi', 'us'.
topicstring–Authoritative topic id, e.g. 'maternity-jeans'. Filters the listing.

No output schema declared.

No examples provided.

get_product ~136

Fetch full public details for one Mamanida product on a specific storefront: localized summary, fabric and bump-panel facts, sizes, colours, availability (IN_STOCK / OUT_OF_STOCK / UNKNOWN), the retailer's authoritative price plus the storefront's displayed price, and whether the outbound link is AFFILIATE, DIRECT or BLOCKED. Only the canonical Mamanida URL is returned.

NameTypeReqDescription
slugstringyesProduct slug as it appears in the Mamanida product URL.
storefrontstringyesRequired storefront id, e.g. 'int', 'se', 'dk', 'no', 'fi', 'us'.

No output schema declared.

No examples provided.

list_categories ~120

List the canonical product categories available on one Mamanida storefront. Each entry gives the exact `slug` to pass to search_products, a label in the storefront's language, any existing localized aliases, and the number of products currently visible on that storefront. Only categories with at least one visible product are returned, and the order is Mamanida's own category order (never product counts).

NameTypeReqDescription
storefrontstringyesRequired storefront id, e.g. 'int' (English), 'se', 'dk', 'no', 'fi', 'us'.

No output schema declared.

No examples provided.

search_products ~192

Search Mamanida's maternity and nursing clothing catalogue for one storefront. Returns only products a visitor of that storefront can actually see, with the retailer's authoritative price, the storefront's displayed price (marked when it is an approximate conversion), availability and the commercial state of the outbound link. Links returned are canonical Mamanida product URLs; retailer and affiliate URLs are never exposed.

NameTypeReqDescription
brandstring–Exact brand name filter.
categorystring–Category slug, e.g. 'dresses'.
limitinteger––
offsetinteger––
on_saleboolean–Only products currently discounted.
querystring–Free-text query, max 100 characters.
sortstring––
storefrontstringyesRequired storefront id, e.g. 'int' (English), 'se', 'dk', 'no', 'fi', 'us'.

No output schema declared.

No examples provided.

Common questions

What is the Mamanida Maternity Catalogue MCP server?

Mamanida Maternity Catalogue is an MCP server listed in the public MCP registry as com.mamanida/mamanida-mcp. Public read-only MCP server to discover and compare maternity and nursing fashion. This page covers its hosted endpoint (https://mamanida.com/mcp).

Is the Mamanida Maternity Catalogue MCP server safe to use?

Mamanida Maternity Catalogue scores 78 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 Mamanida Maternity Catalogue MCP server expose?

Mamanida Maternity Catalogue exposes 5 tools: search_products, get_product, compare_products, list_categories, get_guides. Their descriptions and schemas cost roughly 807 tokens of context every time the server is loaded.

Does the Mamanida Maternity Catalogue MCP server require authentication?

No. We connected to Mamanida Maternity Catalogue without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Mamanida Maternity Catalogue MCP server still maintained?

Mamanida Maternity Catalogue is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.