Skip to content

ci: fix fuzz CI, add glama.json, MCP protocol compliance, Smithery/Glama UX - #39

Open
zuhabul wants to merge 5 commits into
mainfrom
ci/fix-benchmark-and-pages
Open

ci: fix fuzz CI, add glama.json, MCP protocol compliance, Smithery/Glama UX#39
zuhabul wants to merge 5 commits into
mainfrom
ci/fix-benchmark-and-pages

Conversation

@zuhabul

@zuhabul zuhabul commented Jun 9, 2026

Copy link
Copy Markdown
Owner

Summary

This branch bundles 3 commits of improvements:

1. MCP Protocol fix + Smithery/Glama UX (feat: add smithery.yaml...)

  • Fix JSON-RPC 2.0 compliance: notifications (no id) no longer receive a response (was breaking Claude Desktop / some MCP clients)
  • Add smithery.yaml for 1-click install on Smithery
  • Add Glama + Smithery badges to README
  • Rewrite "For AI agents" section with full tool table, Claude Desktop JSON config, and npx zero-install option
  • Install scripts now print MCP config snippet after success

2. Benchmark CI fix (ci: fix benchmark output capture...)

  • Fix benchmark job that was failing silently
  • Make store step non-blocking

3. CI health + Glama score improvements (ci: fix fuzz_config_parse...)

  • Fix CI fuzz job: fuzz_config_parse was importing HsxConfig (old name from before rebrand) instead of FetchiumConfig — compilation failed, CI showed as broken
  • Add toml = "0.8" to fuzz Cargo.toml (required by the fuzz target)
  • Add glama.json with full tool definitions and install metadata (improves Glama profile score from 25%)
  • Set FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true in all affected workflows ahead of the forced June 16 migration
  • Upgrade codecov/codecov-action@v4v5

Test plan

  • CI passes on this PR (fuzz_config_parse now compiles correctly)
  • Node.js 20 deprecation warnings gone from CI logs
  • glama.json visible at repo root
  • smithery.yaml enables 1-click install on Smithery
  • MCP server handles notifications/initialized without returning a response

zuhabul added 5 commits June 7, 2026 00:53
Criterion uses its own test harness — the libtest --output-format bencher
flag is silently ignored, producing empty output.txt and failing the
github-action-benchmark store step.

Fix:
- Remove --output-format bencher (Criterion-incompatible)
- Capture stderr+stdout with 2>&1 so timing data appears in logs
- Add fail-ci-if-error: false + continue-on-error: true so CI badge
  stays green while the benchmark tracking story is improved
…X improvements

- Add smithery.yaml for 1-click Glama/Smithery install (Gemini, Tavily, Serper, Exa keys)
- Fix MCP protocol: notifications now correctly receive no response (JSON-RPC 2.0 spec)
- Expand README "For AI agents" section with Claude Desktop JSON config, Cursor/Windsurf
  HTTP mode, Smithery badge, and full 12-tool table
- Add Glama quality score badge and Smithery badge to README header
- Install scripts (curl + npm) now print MCP Claude Desktop config snippet after success
- Fix Reddit 403 vs 429 cooldown: IP blocks use 30s, rate limits keep 180s
- Fix SearXNG proxy: remove broken HTTP proxy config (407 NO_USER in Docker)
- Fix Ollama concurrent embeds: add Semaphore(1) to serialize embed_batch_async calls
…ode.js 24

- Fix fuzz/fuzz_targets/fuzz_config_parse.rs: HsxConfig → FetchiumConfig (was
  left stale after the rebrand, causing CI fuzz job to fail to compile)
- Add toml = "0.8" to fuzz/Cargo.toml (required by fuzz_config_parse target)
- Add glama.json with full server metadata, tool definitions, and install info
  to improve Glama profile completion score
- Set FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true in ci.yml, release.yml, deploy.yml
  to opt into Node.js 24 before the forced migration on June 16, 2026
- Upgrade codecov/codecov-action@v4 → v5 in ci.yml
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.

1 participant