{ "SchemaVersion": "1", "Kind": "DirectoryIssues", "Slug": "anime-mcp-server", "Name": "anime-mcp-server", "CanonicalUrl": "https://askpod.ai/mcp/anime-mcp-server/issues", "ServerUrl": "https://askpod.ai/mcp/anime-mcp-server", "IssueTotal": 27, "Held": 21, "Issues": [ { "Title": "ux(anime_get_studio): missing-identifier case uses validationError() factory, not ctx.fail — data.reason is null", "Excerpt": "### Server version\n\n0.1.1\n\n### mcp-ts-core version\n\n^0.9.21\n\n### Runtime\n\nNode.js\n\n### Runtime version\n\n>=24.0.0\n\n### Transport\n\nHTTP (Streamable HTTP)\n\n### Description\n\nWhen \\`anime_get_studio\\` is called with neither \\`name\\` nor \\`id\\`, the handler throws via \\`validationError()\\` factory directly (not \\`ctx.fail\\`). This produces \\`error_data: null\\` in the tool response — \\`data.reason\\` is absent, the error contract isn't declared, and machine consumers can't route on the structured reason", "SourceUrl": "https://github.com/cyanheads/anime-mcp-server/issues/5", "PublishedAt": "2026-06-07T04:56:29.000Z", "State": "closed", "Comments": 2, "Reporter": "Maintainer", "Rank": "top", "Extractor": "github_issue" }, { "Title": "ux(anime_search_media): description leaks internal fallback routing detail", "Excerpt": "The `anime_search_media` description ends with: `'AniList is the primary source; Jikan (MAL) is used as a fallback when AniList returns no results.'`\n\nThis exposes internal service routing — which APIs the tool uses and in what order — rather than describing what the tool does for the caller. The output schema already surfaces a `source` field that indicates which service provided results, so callers can observe the actual source without being coached on the internal fallback logic.\n\n### Steps t", "SourceUrl": "https://github.com/cyanheads/anime-mcp-server/issues/4", "PublishedAt": "2026-06-07T04:45:17.000Z", "State": "closed", "Comments": 2, "Reporter": "Maintainer", "Rank": "top", "Extractor": "github_issue" }, { "Title": "ux(anime_get_media): scores output description meta-coaches rather than describes", "Excerpt": "The `scores` output field description in `anime_get_media` ends with a directive: `'AniList and MAL use different scales and methodologies — never blend them.'`\n\nThe phrase \"never blend them\" is meta-coaching — it tells the reader how to use the data rather than describing what the data is. Output schema descriptions should explain what the value *is*, not prescribe how to interpret it.\n\n### Steps to reproduce\n\n1. Call `tools/list` and inspect the `outputSchema.properties.scores.description` for", "SourceUrl": "https://github.com/cyanheads/anime-mcp-server/issues/3", "PublishedAt": "2026-06-07T04:45:07.000Z", "State": "closed", "Comments": 2, "Reporter": "Maintainer", "Rank": "top", "Extractor": "github_issue" }, { "Title": "ux(anime_get_recommendations): liked_aspects param description has audience leak", "Excerpt": "The `liked_aspects` parameter description in `anime_get_recommendations` contains consumer-aware phrasing that names the calling agent as the reader.\n\n### Current description\n\n`'Included in the output for context; the agent can use it to highlight relevant picks.'`\n\nThe phrase \"the agent can use it\" names the LLM reader directly — this violates the definition language rule that descriptions should describe the value, not coach the caller.\n\n### Steps to reproduce\n\n1. Call `tools/list` and inspect", "SourceUrl": "https://github.com/cyanheads/anime-mcp-server/issues/2", "PublishedAt": "2026-06-07T04:44:57.000Z", "State": "closed", "Comments": 2, "Reporter": "Maintainer", "Rank": "top", "Extractor": "github_issue" }, { "Title": "ux(anime_search_media,anime_get_rankings,anime_get_schedule): no notice field in empty-result structuredContent", "Excerpt": "`anime_search_media`, `anime_get_rankings`, and `anime_get_schedule` return empty `results`/`entries` arrays on zero matches, but their `structuredContent` (output schema) has no `notice` field. The `content[]` text says \"No results found (source: anilist).\" but this guidance is invisible to `structuredContent`-only clients (e.g., Claude Code API mode).\n\n## Proposal\n\nAdd a `notice: z.string().optional()` field to the output schemas of these three tools. Populate it on empty results with an actio", "SourceUrl": "https://github.com/cyanheads/anime-mcp-server/issues/1", "PublishedAt": "2026-06-07T04:44:47.000Z", "State": "closed", "Comments": 2, "Reporter": "Maintainer", "Rank": "top", "Extractor": "github_issue" }, { "Title": "feat(config): declare stateless mode in createApp", "Excerpt": "### Use case\n\nSource, `bunx`, and npm launches still inherit the framework's `auto` session-mode default, which resolves to `stateful`. This read-only data server has no request-spanning user or session state.\n\nThe configuration-owned surfaces are already aligned in v0.1.6: `.env.example` actively selects `stateless`, and the Docker image sets `MCP_SESSION_MODE=stateless`.\n\n### Proposed behavior\n\nAfter cyanheads/mcp-ts-core#376 is released and adopted, declare `sessionMode: \"stateless\"` in `src/", "SourceUrl": "https://github.com/cyanheads/anime-mcp-server/issues/17", "PublishedAt": "2026-08-22T19:00:11.000Z", "State": "open", "Comments": 1, "Reporter": "Maintainer", "Rank": "top", "Extractor": "github_issue" }, { "Title": "docs(community-health): CONTRIBUTING.md and SECURITY.md ship unresolved scaffold comments", "Excerpt": "### Description\n\n`.github/CONTRIBUTING.md` and `.github/SECURITY.md` were scaffolded by the framework's community-health generator and committed with placeholder HTML comments still in place, meant to be filled in or removed by the maintainer.\n\n### Actual behavior\n\n`.github/CONTRIBUTING.md`:\n```\n\n\n