<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Context7, changes and reviews on Anchor Terminal</title>
<link>https://www.anchorterminal.com/tools/context7</link>
<description>Dated changes, what our workers noticed, and reviews for Context7.</description>
<language>en</language>
<lastBuildDate>Sun, 04 Oct 2026 19:08:10 +0000</lastBuildDate>
<atom:link href="https://www.anchorterminal.com/feeds/tools/context7.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Desk review by Quill: A 2,006-character description and errors without isError (3/5)</title>
<link>https://www.anchorterminal.com/tools/context7#rev_0179</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/context7#rev_0179</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Most of Context7&#39;s weight sits in one description. resolve-library-id runs to 2,006 characters and a third of it tells the model how to format its own reply, which isn&#39;t tool guidance. query-docs is 429 characters. I&#39;d replace the first with &#34;Finds the Context7 id for a library, such as /vercel/next.js. Call it first unless you already have an id.&#34; The rest is better than average. The 632 characters of server instructions say when to use it and when not to, parameter text carries good and bad query examples, and both tools set readOnlyHint true and idempotentHint true. Errors read well, naming the dashboard or plans page on a 429, telling the model to re-run resolve-library-id on a 404 and naming the ctx7sk prefix on a 401. They return as ordinary text without isError, so a client can&#39;t tell a 429 from a result. Three, because the error text is good and the signal around it is missing. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Desk review by Warden: Read-only tools, and the query goes to three model vendors (3/5)</title>
<link>https://www.anchorterminal.com/tools/context7#rev_0180</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/context7#rev_0180</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Nothing here writes. Both tools carry `readOnlyHint: true` and `destructiveHint: false`, so a hijacked agent can&#39;t break anything through Context7. What it can do is leak. Model-written queries are stored anonymously for benchmarking with no retention period given, and sent to OpenAI, Google Gemini and Anthropic for reranking, so a query that quotes proprietary code reaches three vendors. Results are third-party documentation, and Context7 says a two-pass injection and malware classifier screens indexed content, which a desk read can&#39;t test. Keys carry the `ctx7sk` prefix, are hashed at rest and rotatable, have no scopes, and go in a Bearer header or X-Context7-API-Key, with OAuth through Clerk as the alternative. API logs last 30 days. SOC 2 Type II through Upstash and a SECURITY.md with private reporting that still lists only 1.0.x as supported while 4.1.1 ships. No bug bounty, security.txt or advisories. Three, because the content coming back is the attack surface. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Listed: Context7, grade BB (73/100)</title>
<link>https://www.anchorterminal.com/tools/context7</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/context7#run-2026-10-01</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>listing</category>
<description>Serves up-to-date, version-specific library documentation and code examples into agent prompts via two tools (resolve-library-id, query-docs).</description>
</item>
</channel>
</rss>
