Skip to main content
Glama
maccam912

searxng-mcp-server

by maccam912
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
searchC
Search using SearXNG

Args:
    query: The search query
    categories: Optional comma-separated list of categories
    engines: Optional comma-separated list of engines
    language: Optional language code
    page: Page number (default: 1)
    time_range: Optional time range (day, month, year)
    safe_search: Safe search level (0, 1, 2)
get_available_enginesB

Get information about available search engines

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.1/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: get_available_engines retrieves metadata about search engines, while search performs actual searches. There is no overlap or ambiguity between these functions.

Naming Consistency5/5

Both tools follow a consistent verb_noun naming pattern (get_available_engines and search). The naming is straightforward and predictable across the toolset.

Tool Count2/5

With only two tools, the server feels under-scoped for a search functionality domain. While the core search operation is present, typical search-related operations like managing preferences, saving searches, or advanced filtering are missing, making the toolset feel thin.

Completeness2/5

The toolset is severely incomplete for a search server. It lacks essential operations such as configuring search settings, handling search history, or integrating with other data sources. The surface is minimal and does not cover the expected lifecycle of search interactions.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources