Agent Audit vs Leetcode MCP Server
A side-by-side look at the Agent Audit and Leetcode MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Agent Audit for coding agents work as a local process; choose Leetcode MCP Server for coding agents as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Agent Audit when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
LIGHTHOUSE_MCP_ALLOW_LOCALHOST. - You want tools like
analyze_website_performance.
Choose Leetcode MCP Server when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You want tools like
get_daily_challenge, get_problem, search_problems.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 53/100 · Good | 69/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | LIGHTHOUSE_MCP_ALLOW_LOCALHOST | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 155 |
| Directory activity | 1 views 0 installs 0 upvotes | 8 views 0 installs 0 upvotes |
| Tools | 1 | 9 |
| Full listing | View Agent Audit | View Leetcode MCP Server |
Tools & capabilities
Agent Audit tools 1
analyze_website_performanceRuns Lighthouse and site intelligence against a target URL:
Leetcode MCP Server tools 9
get_daily_challengeRetrieves today's Daily Challenge problem with full description (read-only, no auth). Returns problem details for the current date as JSON. Use get_problem when you know a specific titleSlug; use search_problems to discover problems by filters.get_problemRetrieves a single LeetCode problem by titleSlug (read-only, no auth). Returns description, examples, constraints, and metadata as JSON. Use search_problems to find problems by keyword/tag/difficulty; use get_daily_challenge for today's featured problem.search_problemsSearches LeetCode problems by category, tags, difficulty, and keywords (read-only, no auth). Supports pagination via limit/offset. Returns matching problem list as JSON. Use get_problem when you already know the titleSlug; use this to browse or discover problems.get_user_profileRetrieves any user's public profile by username (read-only, no auth). Returns ranking, avatar, bio, submission stats, and platform-specific progress. Use this to look up other users or public stats. Use get_user_status (requires auth) instead to verify the current session user's login state—not for looking up arbitrary users.get_recent_submissionsRetrieves a user's recent submission history on LeetCode Global (read-only, no auth). Includes both accepted and failed submissions. Global only—not available on CN. Use get_recent_ac_submissions for accepted-only results, or get_all_submissions (auth, current user) for paginated full history with filters.get_recent_ac_submissionsRetrieves a user's recent accepted (AC) submissions (read-only, no auth). Available on both Global and CN. Use get_recent_submissions (Global only) to include failed attempts, or get_all_submissions (auth, current user) for full paginated history.get_user_contest_rankingRetrieves a user's contest ranking and participation history (read-only, no auth). Returns overall rating, ranking, and per-contest performance as JSON. Use get_user_profile for general stats and ranking; use this specifically for contest performance data.list_problem_solutionsLists community solution articles for a problem (read-only, no auth). Returns metadata only (topicId)—not full content. Use get_problem_solution with the returned topicId to read the full article. Do not call this when you already have a topicId and need the solution text.get_problem_solutionRetrieves full content of a community solution article (read-only, no auth). Requires topicId from list_problem_solutions. Returns article text, author, and metadata as JSON. Use list_problem_solutions first to discover solutions and obtain topicId.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Agent Audit
{
"mcpServers": {
"agent-audit": {
"command": "npx",
"args": [
"-y",
"@fullstackdegen/agent-audit"
],
"env": {
"LIGHTHOUSE_MCP_ALLOW_LOCALHOST": "YOUR_LIGHTHOUSE_MCP_ALLOW_LOCALHOST_HERE"
}
}
}
}
Leetcode MCP Server
{
"mcpServers": {
"jinzcdev-leetcode-mcp-server": {
"command": "npx",
"args": [
"-y",
"@jinzcdev/leetcode-mcp-server"
]
}
}
}
Frequently asked questions
Agent Audit is categorized under Coding Agents and uses a local stdio subprocess. Leetcode MCP Server belongs to Coding Agents and uses a local stdio subprocess. Pick Agent Audit for coding agents work and Leetcode MCP Server for coding agents.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Agent Audit has no declared pricing — check the project's own site. Leetcode MCP Server is listed as free. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add agent-audit and jinzcdev-leetcode-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agent Audit has a quality signal of 53/100 (Good) with 1 views, 0 installs and 4 GitHub stars. Leetcode MCP Server has 69/100 (Great) with 8 views, 0 installs and 155 GitHub stars.