Bug Detector

io.github.madhavi-opseraPublished by GitHub account madhavi-opserav1.0.0Updated Oct 24, 2026

Analyzes code for bugs, security vulnerabilities, and code smells

VerifiedSTDIODesktop onlyDeveloper Tools Security & Monitoring

Server details

Identifier: io.github.madhavi-opsera/bug-detector
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account madhavi-opsera for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.madhavi-opsera%2Fbug-detector.svg)](https://sourceweft.com/mcp/io.github.madhavi-opsera%2Fbug-detector?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local MCP server that analyzes code for bugs, security vulnerabilities and code smells, letting an assistant run code-quality checks.

What you can do: Analyze code for bugs and defects
Flag security vulnerabilities
Report code smells and quality issues
No individual tools are documented; the server is described only as an agent for detecting bugs in code.
When to use it: When you want an assistant to review code for defects, security issues or code smells as part of a development or review workflow.
Requirements: Runs as a local process on the user's machine via Docker, using the published container image; desktop only, no web execution. No authentication, environment variables or headers are declared.

Before you install

The README is minimal and no tools are listed, so the exact behavior and scope of analysis are unclear before installing. No credentials or write actions are declared, but code submitted for analysis is processed by the local container.

Installation

In SourceWeft

Open Bug Detector in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

bug-detector

Agent to detect bugs

Source: README.md at commit 624eff4

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.0.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts
Declare a license in the repository or the registry entry.