LET CLAUDE RUN THE RADAR.

INSTALL THE PLUGIN.

Run these commands inside Claude Code:

/plugin marketplace add https://github.com/optifeed/optifeed-radar.git
/plugin install optifeed-radar@optifeed

Run /reload-plugins or start a new session. Invoke /optifeed-radar:optifeed-radar, or describe the audit you want in plain language.

SKILL ONLY.

If you do not want the MCP server, install the same standalone skill through the Skills CLI:

npx skills add optifeed/optifeed-radar --skill optifeed-radar -g

The skill can drive Radar's CLI through Claude Code's shell access.

MANUAL MCP.

For a project-scoped MCP connection without the plugin:

claude mcp add --transport stdio optifeed-radar -- \
  npx -y --package=optifeed-radar@0.2.3 optifeed-mcp

Then verify it:

claude mcp get optifeed-radar
claude mcp list

Inside Claude Code, open /mcp to inspect connection status and tools. The default local scope associates this manual server with the current project.

PROVE IT FOR FREE.

Use Optifeed Radar to run a free AI-readiness audit on mybrand.com.
Explain the findings, but do not run any tool that spends API credit.

This calls audit_store, which needs no provider keys and makes no AI calls.

USEFUL WORKFLOWS.

Check mybrand.com's AI visibility in quick mode. Use only the engines with configured keys and cap spend at $0.20.

Check these products for mybrand.com: Product A, Product B. Explain any absences and competitors.

Compare the last two Optifeed Radar runs for mybrand.com. Summarize score and per-engine changes, with no new paid run.

KEEP KEYS LOCAL.

For paid tools, provide at least one supported provider key through the local environment or a project-local .env file. Do not paste keys into Claude prompts or commit them. Use max_cost whenever Claude starts a paid check unattended.

OPENAI_API_KEY=...
# or ANTHROPIC_API_KEY, GOOGLE_API_KEY, PERPLEXITY_API_KEY