Mamanida Maternity Catalogue
com.mamanida/mamanida-mcp · 1.0.0
Public read-only MCP server to discover and compare maternity and nursing fashion.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://mamanida.com/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 5 tools.
- Protocol
- 2025-06-18
- Calls itself
- mamanida-mcp 1.0.0
- Handshake time
- 1259 ms
- HTTP status
- 200
The tools it lists (5, as of 3 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
search_productsSearch 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.
get_productFetch 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.
compare_productsCompare 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.
list_categoriesList 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).
get_guidesMamanida'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
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.mamanida/mamanida-mcp, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 40 days ago. The registry entry · mamanida.com