Repository navigation
Releases
v1.0.4
Fixes
- Instant answers SearXNG en objet : les réponses instantanées renvoyées sous forme d'objet (
{answer, url, template}) affichaient[object Object]dans la sortie agent. Elles sont désormais normalisées en texte, avec l'URL source conservée (src/format.tsasText, typesstring | objetdanssrc/types.ts). - 3 nouveaux tests (106 au total). Validé en live contre l'instance locale et dans le conteneur Docker.
Installation
npm install -g @aplix39/searxng-mcp@1.0.4
# ou
npx -y @aplix39/searxng-mcp@1.0.4Tarball npm validé : shasum 971e3b6ae22cc3e39856c48f85c1dc51cf642c2e, --version = 1.0.4.
v1.0.3
npm v1.0.3 — version-string fix release
Publication 100% validée : --version et MCP serverInfo.version déclarent désormais 1.0.3 (la 1.0.2 déclarait 1.0.1 à cause d'un bump manuel qui ne touchait que package.json).
scripts/sync-version.mjssynchronisesrc/version.tsà chaquenpm version- test garde-fou
test/version.test.ts: VERSION == package.json.version (103 tests) npm versionrebuild aussidist/: tag, commit et tarball npm ne peuvent plus diverger
Validation du tarball publié : shasum identique à la publication, install isolé npm i @aplix39/searxng-mcp@1.0.3, handshake MCP (serverInfo 1.0.3, 7 tools), smoke live time_range=week + headings_only contre une instance SearXNG réelle.
Install: npm i -g @aplix39/searxng-mcp · bunx @aplix39/searxng-mcp --url http://votre-instance
v1.0.2
npm v1.0.2 — mcp-searxng comparison improvements
Adopted from the mcp-searxng (v2.5.1) feature comparison, adapted to this project's minimal, stdio-only philosophy:
searxng_search*: newtime_range=week(day/week/month/year)searxng_autocomplete: newlanguageparametersearxng_config: newinclude_engines=falsecompact modesearxng_extract_content:- JSON responses pretty-printed in fenced code blocks (previously refused)
- non-HTML
text/*bodies returned as fenced text (previously mangled by the HTML parser) - binary content types still refused
- new
start_charwindowing for paging through long pages - new
headings_onlymode: h1–h6 outline without page chrome
- New
SEARXNG_TIMEOUT_MSenv var (500–300000 ms, default 30000) mcpNamefield in package.json
Validation: 102 unit/integration tests at publish time (103 on master now), Node 18/24/26 + Bun runtime matrix, live smoke against a real SearXNG instance, MCP protocol negotiation up to 2025-06-18.
Known quirk
The 1.0.2 tarball's --version / MCP serverInfo.version reports 1.0.1: the version bump was done by hand and only touched package.json. Fixed on master right after the tag (scripts/sync-version.mjs wired into the npm version lifecycle + a guard test that fails on any desync) — the next publish will report correctly. No functional impact: npm installs the 1.0.2 code either way.
Install: npm i -g @aplix39/searxng-mcp · bunx @aplix39/searxng-mcp --url http://votre-instance
searxng-mcp v1.0.0
First release of searxng-mcp — an MCP server that plugs a SearXNG instance into AI agents.
Highlights
- 7 tools:
searxng_search(+ _news / _images / _videos variants),searxng_autocomplete,searxng_config,searxng_extract_content - Clean page extraction: headers/footers/nav/sidebars/comments/cookie banners removed by default,
include_*flags to re-include, CSSselector, markdown link/image modes, truncation guard - Agent-friendly: domain include/exclude filters, SafeSearch, time ranges, engine selection, actionable error messages
- Installable via
bun install -g,npm pack+npm install -g, ornpxstraight from GitHub (no build step needed)
Install
```bash
bun install -g github:STIFLEUR390/searxng-mcp
searxng-mcp --url http://localhost:8888
```
npm registry: npm install -g @aplix39/searxng-mcp (after publication).
Validation
84 tests (bun:test), strict typecheck, live validation against a real SearXNG instance, crafted-page extraction suite 31/31, Node >= 18, lock-faithful reproducible bundle (1.1 MB).