Authorization notice. Botscent is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Who it is forA developer who has just added Botscent and needs to confirm both halves work before trusting any verdict.
The problemA half-installed setup returns wrong verdicts without any visible error.
The outcomeA pass, fail, unknown or skipped line for each check, with the likely cause and fix for any line that is not a pass.
What you need first
- A site built with a supported framework such as Next.js, Express, Django or FastAPI
- npm for the TypeScript package or pip for the Python package
- Permission to edit your site's server code and page layout
- A running site URL to test against
Steps
- Install the package with
npm install botscent, orpip install botscentfor Python. - Add the page half and the server half for your framework from the Quickstart section.
- Run
npx botscent check https://your-site.example/. - Read each line. A line that is not a pass also gives the likely cause and the fix.
- Use
--jsonfor scripts or--reportfor an issue. Exit code 0 means the install works, 1 means it is broken and 2 means neither half was confirmed.
Prompt for your agent
Using the botscent repo (nalinbhardwaj/botscent), run `npx botscent check https://<your-site>/` in the project. Expected output: pass, fail, unknown or skipped for each check. Verify that the exit code is 0 and list the files you changed.
Caveat. The check opens the page in a local Chrome that sets the webdriver flag, so the page half will report an agent during the check.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for nalinbhardwaj/botscent and "Check that Botscent is installed correctly"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer