MCP servers observed by Lowdown
io.studiomeyer/academy MCP server: daily status and tool changes
On the latest check (2026-11-18) its remotes differed: 1 answered tools/list, 1 required authentication. (Lowdown checks this server every 3 days) MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; tool definitions last changed on 2026-11-12 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.studiomeyer/academy
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.studiomeyer/academy?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server its remotes gave different results.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 0
- Required authentication: 0
- No response: 0
- Remotes differed: 4
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 1 of 3 compared days.
- 2026-11-12: input or output schemas changed, descriptions changed
What tools does it list?
29 tools on 2026-11-18:
academy_coachingacademy_conceptsacademy_glossaryacademy_glossary_termacademy_legacy_lessonsacademy_legacy_levelsacademy_lessonacademy_lessonsacademy_levelsacademy_libraryacademy_moduleacademy_pathacademy_pathsacademy_playbookacademy_playbooksacademy_premium_catalogacademy_premium_previewacademy_promptacademy_promptsacademy_recipeacademy_recipesacademy_searchacademy_startacademy_suggestacademy_teachacademy_tutor_contextacademy_welcomefetchsearch
MCP Registry declaration
- Registry name:
io.studiomeyer/academy - Declared version: 0.6.0
- Status: active
- Declared hosts:
mcp.studiomeyer.academy
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.studiomeyer/academy", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.studiomeyer/academy?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:io.studiomeyer/academy -- npx -y mcp-academy
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).