Skip to content

Add optional Hermes Tweet search backend - #1

Open
kriptoburak wants to merge 3 commits into
fluyeporlaweb:mainfrom
kriptoburak:codex/add-hermes-tweet-search-backend
Open

Add optional Hermes Tweet search backend#1
kriptoburak wants to merge 3 commits into
fluyeporlaweb:mainfrom
kriptoburak:codex/add-hermes-tweet-search-backend

Conversation

@kriptoburak

@kriptoburak kriptoburak commented May 24, 2026

Copy link
Copy Markdown

Summary

  • add an optional Hermes Tweet/Xquik backend for search_viral_content
  • keep the existing backend as the default path for all tools
  • support backend selection with request arguments, headers, and worker secrets
  • document server-side and request-scoped configuration

Independent Repository Fix

  • validate JSON-RPC request envelopes before dispatch
  • return -32600 for malformed scalars, objects, and empty batches
  • keep mixed batches valid when one member is malformed
  • return an empty 204 response for single and batch notifications

This prevents malformed input from throwing during destructuring or being silently treated as a notification.

Validation

  • npm ci --ignore-scripts --no-audit --no-fund
  • npm run build
  • npx wrangler deploy --dry-run
  • executable 10-case JSON-RPC smoke test covering malformed bodies, empty and mixed batches, notifications, and a valid request
  • git diff --check
  • public diff secret-pattern scan
  • all PR comments, reviews, inline threads, commits, files, statuses, and checks paginated and audited
  • fork verified as kriptoburak/mcp-x-intelligence, parent fluyeporlaweb/mcp-x-intelligence

@Pautthead

Copy link
Copy Markdown
Collaborator

Thanks for the contribution! Really appreciate it.

I'm reviewing the changes carefully before merging.
The README was recently rewritten so there are conflicts
to resolve. I'll come back to this once the initial
launch is stable.

Will keep this PR open for consideration.

@kriptoburak

Copy link
Copy Markdown
Author

Refreshed this branch against current main to resolve the README/src conflicts while keeping the new MCPize/worker-secret flow intact. Hermes Tweet remains optional for search_viral_content only.

Validation:

  • npm ci --ignore-scripts --no-audit --no-fund
  • npm run build
  • conflict-marker scan clean
  • target-diff whitespace check clean
  • added-line secret pattern scan clean
  • Hermes Tweet and target GitHub links returned HTTP 200

@kriptoburak

Copy link
Copy Markdown
Author

Pushed commit 6d3b77f with an independent JSON-RPC boundary repair. Malformed scalars, objects, and empty batches now return -32600 instead of throwing or disappearing; mixed batches retain valid responses; notifications return 204 with no body. TypeScript, Wrangler dry-run bundling, and a 10-case executable protocol smoke test pass. The branch remains conflict-free against current main.

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.

2 participants