Blog batch 2026-08-23: Exa MCP, Firecrawl MCP, New Relic vs Datadog MCP - #148
Open
gusmar2017 wants to merge 1 commit into
Open
Blog batch 2026-08-23: Exa MCP, Firecrawl MCP, New Relic vs Datadog MCP#148gusmar2017 wants to merge 1 commit into
gusmar2017 wants to merge 1 commit into
Conversation
…tadog MCP guides Three new MCP server posts: Exa MCP Server (search, Gus), Firecrawl MCP Server (devtools, Adam), New Relic vs Datadog MCP Servers (monitoring comparison, Gus). All 3 completed the Two-Agent Validation Loop. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Weekly MCPFind blog batch (run 2026-08-23, Sunday). 3 new posts, all completed the Two-Agent Validation Loop, all above the 1,200-word floor.
exa-mcp-server-ai-search-guidefirecrawl-mcp-server-web-scraping-guidenew-relic-vs-datadog-mcp-serversTopic selection: Priority 1 (listicle slots 86-93) empty, all shipped/deferred. Priority 2 (striking-distance) empty, GSC returned 0 actionable signals across all 4 categories (11th+ consecutive week). Selected from Priority 3 replenishment queue (Topics 130/131/132 of 10 newly-sourced candidates), FIFO, all P2.
Directory data: Extracted cleanly, 24,493 total servers. search category 1,631 servers/17.5 avg stars; devtools 6,290/17.19 avg; monitoring 280/0.53 avg (one of the thinnest categories in the index).
Anti-fabrication: Exa's official server IS indexed (
ai-exa-exa, 4,083 stars) and linked directly. Firecrawl's official server is NOT yet indexed — post links to/categories/devtoolsand/categories/automationinstead of a fabricated slug. Neither New Relic's nor Datadog's official server is indexed — post discloses this and links to/categories/monitoringand the existingdatadog-mcp-server-observabilitysibling post instead.Fact-check correction: The New Relic vs Datadog post's original "maturity gap by GitHub stars" framing was reworked after keyword/fact research found neither vendor treats GitHub as its primary distribution channel (New Relic's repo is a 7-star stub pointing to docs.newrelic.com; Datadog has no repo under its real
DataDogorg at all, and the closest match,datadog-labs/mcp-server, is explicitly disclaimed as experimental/unsupported). Reframed around release stage (preview vs. GA) and documented tool coverage instead, which is a comparison that actually applies to both.Sentinel validation log (Two-Agent Validation Loop)
All 3 posts reached PASS within the 3-round cap. Zero em dashes and zero blocklist phrases across every round for every post; residual signals were structural (antithesis "X, not Y" tags, colon-list enumeration, symmetric hedge constructions) rather than lexical.
Linking / cluster notes
/blog/perplexity-mcp-server-search-guide) will 404 until PR Blog batch 2026-08-19: Perplexity MCP, AWS vs Terraform MCP, PostHog MCP #146 merges — same known-gap pattern as prior batches with in-flight sibling PRs.Editorial calendar reconciliation (out of band, this run)
Found the calendar (mac-mini-agent repo) had drifted from reality: Topics 114 (Perplexity), 125 (1Password vs Bitwarden), 126 (Pinterest/MS Advertising), and 127 (AWS vs Terraform) were still marked
status: queueddespite being drafted and shipped in the 2026-08-16 (PR #142, merged) and 2026-08-19 (PR #146, still open) batches. ClickHouse and PostHog (also shipped in those batches) had no calendar entries at all. Corrected all 6 entries this run — separate commit to the mac-mini-agent repo, not part of this PR.Test plan
.mdxfiles parse cleanly viagray-matter/servers/,/categories/,/blog/paths (no fabricated slugs)🤖 Generated with Claude Code