{ "SchemaVersion": "1", "Kind": "DirectoryIssues", "Slug": "internet-archive-mcp-server", "Name": "internet-archive-mcp-server", "CanonicalUrl": "https://askpod.ai/mcp/internet-archive-mcp-server/issues", "ServerUrl": "https://askpod.ai/mcp/internet-archive-mcp-server", "IssueTotal": 15, "Held": 15, "Issues": [ { "Title": "docs(skills): release-and-publish is stale against mcp-ts-core — version reads ahead but content is behind", "Excerpt": "### Description\n\n`skills/release-and-publish/SKILL.md` in this repo declares `metadata.version: \"2.9\"`, while the current `@cyanheads/mcp-ts-core` copy of the same skill (`node_modules/@cyanheads/mcp-ts-core/skills/release-and-publish/SKILL.md`) is at `\"1.11\"`. Because the local version string reads numerically ahead of the framework's, a version-gated resync treats it as an intentional local override and leaves it untouched — but a content diff shows the local copy is missing real upstream guid", "SourceUrl": "https://github.com/cyanheads/internet-archive-mcp-server/issues/13", "PublishedAt": "2026-08-22T12:40:09.000Z", "State": "closed", "Comments": 2, "Reporter": "Maintainer", "Rank": "top", "Extractor": "github_issue" }, { "Title": "bug(ia_get_snapshot): Wayback 404 on exact-timestamp direct path doesn't map to no_snapshot_available contract", "Excerpt": "When `ia_get_snapshot` is called with an exact 14-digit timestamp (e.g. `\"20200601000000\"`), the handler skips the Availability API and calls `fetchContent` directly. If the Wayback Machine returns a 404 for that URL/timestamp combination (no capture at that exact timestamp), the raw `FetchHttpError` propagates without being mapped to the declared `no_snapshot_available` contract entry. The result: `data.reason` is `null` and the error text is the generic fetch failure message, not the actionabl", "SourceUrl": "https://github.com/cyanheads/internet-archive-mcp-server/issues/5", "PublishedAt": "2026-06-07T04:55:16.000Z", "State": "closed", "Comments": 2, "Reporter": "Maintainer", "Rank": "top", "Extractor": "github_issue" }, { "Title": "ux(ia_search_items): empty-result notice lives only in structuredContent, not in content[]", "Excerpt": "`ia_search_items` uses `ctx.enrich.notice()` to surface actionable guidance when the query returns zero results. The notice is correctly placed in `structuredContent.notice` — visible to Claude Code and API clients reading structured output — but the `format()` function only renders the result-count line, leaving `content[]` with no guidance text.\n\nClients that only consume `content[]` (Claude Desktop, stdio integrations) see nothing helpful when a search returns zero results.\n\n## Repro\n\nCall `i", "SourceUrl": "https://github.com/cyanheads/internet-archive-mcp-server/issues/4", "PublishedAt": "2026-06-07T04:55:03.000Z", "State": "closed", "Comments": 2, "Reporter": "Maintainer", "Rank": "top", "Extractor": "github_issue" }, { "Title": "ux(ia_get_snapshot): resolved_status is hardcoded '200' for exact-timestamp direct path", "Excerpt": "### Server version\n\n0.1.1\n\n### mcp-ts-core version\n\n^0.9.21\n\n### Description\n\nIn `ia-get-snapshot.tool.ts`, when the caller passes an exact 14-digit timestamp, `ia_get_snapshot` builds the replay URL directly and skips the Availability API check. The `resolved_status` field is hardcoded as `'200'` in this path:\n\n```ts\nif (isExactTimestamp) {\n snapshotUrl = svc.buildReplayUrl(input.timestamp.trim(), input.url);\n resolvedTimestamp = input.timestamp.trim();\n resolvedStatus = '200'; // status wil", "SourceUrl": "https://github.com/cyanheads/internet-archive-mcp-server/issues/3", "PublishedAt": "2026-06-07T04:43:09.000Z", "State": "closed", "Comments": 2, "Reporter": "Maintainer", "Rank": "top", "Extractor": "github_issue" }, { "Title": "bug(ia_get_item): dark/restricted items return empty metadata instead of an error", "Excerpt": "### Server version\n\n0.1.1\n\n### mcp-ts-core version\n\n^0.9.21\n\n### Runtime\n\nBun / Node.js\n\n### Transport\n\nHTTP (Streamable HTTP)\n\n### Description\n\nThe Internet Archive Metadata API returns `HTTP 200` with a non-empty response body for dark (restricted/removed) items, but the body contains only server routing fields (`created`, `d1`, `d2`, `dir`, `is_dark`, etc.) — no `metadata` key and no `files` array.\n\nThe current check in `archive-metadata-service.ts` only throws `item_not_found` when the respo", "SourceUrl": "https://github.com/cyanheads/internet-archive-mcp-server/issues/2", "PublishedAt": "2026-06-07T04:42:55.000Z", "State": "closed", "Comments": 2, "Reporter": "Maintainer", "Rank": "top", "Extractor": "github_issue" }, { "Title": "bug(ia_find_snapshots): closest mode always fails — SSRF guard checks https:// but Wayback API returns http:// URLs", "Excerpt": "### Server version\n\n0.1.1\n\n### mcp-ts-core version\n\n^0.9.21\n\n### Runtime\n\nBun / Node.js\n\n### Transport\n\nHTTP (Streamable HTTP)\n\n### Description\n\n`ia_find_snapshots` with `mode=closest` always returns `no_snapshot_available`, even for well-archived URLs like `example.com`. The same bug breaks `ia_get_snapshot` when a non-exact (< 14-digit) timestamp is passed, since both code paths call `WaybackService.findClosest()`.\n\nRoot cause: the SSRF guard in `wayback-service.ts` validates that the Availabi", "SourceUrl": "https://github.com/cyanheads/internet-archive-mcp-server/issues/1", "PublishedAt": "2026-06-07T04:42:40.000Z", "State": "closed", "Comments": 2, "Reporter": "Maintainer", "Rank": "top", "Extractor": "github_issue" }, { "Title": "docs: SECURITY.md and CONTRIBUTING.md ship unresolved template author-comments", "Excerpt": "### Description\n\n`.github/SECURITY.md` and `.github/CONTRIBUTING.md` were scaffolded from templates that include HTML comments meant to guide the maintainer before publishing (e.g. whether GitHub private vulnerability reporting is enabled, whether to commit to a response-time window, whether PRs are accepted). The placeholder tokens were filled in correctly, but the guidance comments were left in verbatim and are now committed to the public repo:\n\n- `SECURITY.md`: `