Skip to content

Conversation

@nitish-raj
Copy link

Replacing SearXNG MCP with an active development

Description

Server Details

  • Server:
  • Changes to:

Motivation and Context

How Has This Been Tested?

Breaking Changes

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation
  • My changes follows MCP security best practices
  • I have updated the server's README accordingly
  • I have tested this with an LLM client
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

Additional context

Replacing SearXNG MCP with an active development
@Technetium1
Copy link

These are both active, why replace?

@Technetium1
Copy link

@ihor-sokoliuk what is the status of your project? #403

@ihor-sokoliuk
Copy link
Contributor

@Technetium1 My project is actively developing. I respond to all issues, review all pull requests (PRs), and implement new features. I'm not sure why the PR's author is replacing mine.

@nitish-raj nitish-raj closed this May 25, 2025
@nitish-raj nitish-raj deleted the patch-1 branch May 25, 2025 18:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants