3 ms·
That’s the fault of the SEC EDGAR tool. The Edgar MCP docs show setting an env var: ‘SEC_EDGAR_USER_AGENT="Your Name (name@domain.com)"’. Claude just followed
by threecheese 3mo ago
That’s the fault of the SEC EDGAR tool. The Edgar MCP docs show setting an env var: ‘SEC_EDGAR_USER_AGENT="Your Name (name@domain.com)"’.
Claude just followed the instructions. Which is maybe even more risky?
- FriedPickles 3mo agoInteresting theory. The Claude Code instance says it's using this user agent based on the guidelines in the EDGAR Fair Access Policy: https://www.sec.gov/search-filings/edgar-search-assistance/accessing-edgar-data https://www.sec.gov/search-filings/edgar-search-assistance/a... ...which indeed requests that bots supply `User-Agent: Sample Company Name AdminContact@<sample company domain>.com`. So in this case, the site just asked nicely and Claude Code complied. Note that this wouldn't have worked for Claude Chat, which the author was testing, because the `web_fetch` tool cannot set the User-Agent or other headers.
- killix 3mo ago[flagged]