
YogaMag MCP server
Which MCP servers are YogaMag's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-19
- Registry namein.co.yogamag/yogamagverified in the MCP registry
The registry name sits under yogamag.co.in. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-19
- Tools8
- Server calls itselfyogamag-mcp
- Server version1.8.0
- Protocol version2025-06-18
On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 211 ms.
- Its tools do none of the product's use cases we checked: follow timed routines for desk breaks and short resets; play guided yoga nidra scripts for rest.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP score71 of 100answers 100 · does the job 0 · definitions 96 · context 96 · connects 100
- What an agent can do with it0 of 2 use cases
- Answered100% of days17 of 17 daily checks
- Median first answer350 ms
- Space in an agent's context≈ 3,517 tokensthe definitions of all its tools (14), which an agent carries on every turn
- Tool definitionsA · 96 of 100
- Typed results4 of 14 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 3 of 14
What an agent can do with it
- cannot · follow timed routines for desk breaks and short resets
- not sure · find poses by health topic such as back pain or sciatica
- cannot · play guided yoga nidra scripts for rest
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
search_contentSearch YogaMag articles, glossary terms (poses, breathing, Sanskrit), pose comparisons, timed routines, yoga styles, meditation, guides, tools and book summaries. Returns titles, URLs, slugs and the tool to fetch each result (guides and…
get_postGet the full text of a YogaMag article by slug
get_glossary_termGet a yoga glossary entry (pose, breathing technique or term) by slug, including who should skip or modify a pose and its easier versions
get_routineGet a timed yoga routine by slug: every pose with its seconds, sides and breath cue, plus the link to the follow-along timer and, where there is one, the audio class (one MP3 with a spoken cue for every pose) and its podcast episode
get_book_summaryGet a book summary by slug
find_routineFind the YogaMag timed routine for a goal and the minutes the person has: the longest one that fits, or the shortest if none is that short. Returns the routine as published, with its steps, who should skip or modify it, and the…
adapt_routineCheck every step of a YogaMag routine against what the person cannot or does not want to do (the floor, kneeling, weight on the wrists). Each step is kept, swapped for an easier version that the pose's reviewed data lists, marked as…
find_posesList poses from the reviewed YogaMag pose library that match a level, body area or type of pose, and that suit what the person avoids (the floor, kneeling, weight on the wrists), naming the easier version where the pose itself does not…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"yogamag": {
"type": "http",
"url": "https://yogamag.co.in/api/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http yogamag https://yogamag.co.in/api/mcpclaude.ai, ChatGPT and other clients: add https://yogamag.co.in/api/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.