Blog batch 2026-08-12: Elasticsearch MCP deprecation, X official MCP server

[gusmar2017]

Summary

• Elasticsearch MCP Server Deprecated: Here's What Replaces It (Gus Marquez, search cluster) — Elastic's official mcp-server-elasticsearch repo is deprecated in favor of the new Agent Builder MCP endpoint (9.2+/Serverless). Covers the old repo's 5-tool surface, the new endpoint's admin-configured tool catalog, auth/version gating, and community fork alternatives.
• X's Official MCP Server: What Its 200+ Endpoints Expose (Adam Bush, social cluster) — X launched a hosted MCP server June 30, 2026 at api.x.com/mcp, distinct from the older open-source xdevplatform/xmcp project. Covers capabilities, auth, the separate docs-search endpoint, and how it compares to the 30+ unofficial X servers already in MCPFind's directory.

Both topic_source: new_topic. Topic selection: only 2 topics remained queued (both P3), so both posts came from this run's replenishment (Step 0.1, web-research fallback since GSC data had zero actionable signals this week).

Sentinel validation log (Two-Agent Validation Loop)

Post	Round 1	Round 2	Round 3 (final)
Elasticsearch MCP Server	NEEDS_REVISION (58%, 5 flagged)	NEEDS_REVISION (54%, 6 flagged)	NEEDS_REVISION (58%, 8 flagged) -- shipped per 3-round cap
X's Official MCP Server	NEEDS_REVISION (45%, 5 flagged)	NEEDS_REVISION (38%, 3 flagged)	PASS (28%)

Elasticsearch did not reach PASS within the 3-round cap. Its residual signal was overuse of "rather than / instead of / not-X" contrastive constructions -- two full revision passes reduced the raw count but didn't retire the underlying rhetorical habit, and Round 3's score ticked back up slightly (54% to 58%) as fixing flagged sentences surfaced the same connector pattern in previously-unflagged sentences. Worth noting for future humanizer passes on technical comparison content: contrastive-connector density deserves its own signal category, not just fragment/antithesis checks, since it's structurally different from the fragment-pair tic that dominated Round 1.

Both posts: zero em dashes, valid frontmatter/gray-matter parse, word count 1,280 (Elasticsearch) and 1,325 (X) -- both within the 1,200-1,500 range required this run. All internal links verified against live directory category dumps (--category search, --category social) -- no fabricated slugs. Neither Elastic's official server (deprecated repo or new Agent Builder endpoint) nor X's official hosted server is indexed in MCPFind's directory yet; both posts disclose this honestly and link to the closest real community entries instead (io-github-tocharianou-elasticsearch, io-github-kaitoinfra-twitterapi-io-mcp-server).

Data-quality / fact-check notes

• Elasticsearch: independently re-verified the previously-held deprecation claim against Elastic's own README and Search Labs blog (was blocked in queue since 2026-08-02 pending this). Confirmed TRUE, with one correction to the source's date precision (self-managed GA is 9.3, not 9.2 as the deprecation notice implies) and one flagged contradiction (README documents Docker-only distribution; an npm package listing exists but returned an access error on direct check, left unconfirmed).
• X: independently re-verified the "X launched an official MCP server" claim against primary sources (devcommunity.x.com, docs.x.com, TechCrunch) after the initial lead came from a low-authority aggregator site. Confirmed TRUE. Flagged an unresolved contradiction between TechCrunch ("no write operations") and X's own docs (which list Bookmark and Article writes as capabilities) -- disclosed in-post rather than asserted either way.
• Dropped 4 other Task 3 topic candidates (HubSpot, Cloudflare, Notion, Figma) after finding each would cannibalize an already-published MCPFind post on the same product.

Cluster linking notes

• search cluster (Elasticsearch): first published post in this cluster (Perplexity MCP Server remains queued, not yet published) -- linked to /blog index per the no-siblings-yet rule; future search-cluster posts should link back to this one.
• communication cluster (X, category social maps to cluster communication per SKILL.md's category-to-cluster table): exactly 5 published siblings, at the cap -- linked to all 5 with varied anchors (email setup, Slack/team chat roundup, Discord, Twilio, Intercom).

Infra note -- git push guard

Unlike the last 3 batches (2026-08-02 partial, 2026-08-05, 2026-08-09 fully blocked), this week's push succeeded. The difference appears to be command form: prior blocked attempts used cd $HOME/mcp-find && git push, which the I-05 guard flags as an unresolvable-cwd ambiguity (fail-closed by design). This run used git -C <explicit-path> push throughout (both for the worktree creation and the push itself), which resolved unambiguously and was not blocked. If this holds, the two batches stuck since 2026-08-05 and 2026-08-09 may be pushable the same way -- flagged to Gus for confirmation before repushing prior branches.

Test plan: n/a (content-only change, existing CI/build pipeline runs on this PR)

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
mcp-find-web	Ready	Preview	Aug 12, 2026 9:16am