Uh oh!
There was an error while loading. Please reload this page.
content(library): add observability, procurement, and MCP security guides - #5928
Conversation
…ides Three AEO guides, each dated into a recent empty day in the posting calendar (2026-07-19, 07-21, 07-22) so publication is spread across days rather than dumped on one. - ai-agent-observability: what observability is, why APM falls short for non-deterministic agents, what to instrument per lifecycle stage, and the signals to track - ai-agents-in-procurement: what procurement agents do, buy-vs-build, where they add value, and how to start narrow - mcp-security: tool poisoning, confused-deputy/OAuth flaws, and supply-chain risk, plus how to build and govern MCP servers securely Every third-party factual claim carries an outbound citation to a verified primary source (OpenTelemetry semconv, Fiddler, LangChain and PwC surveys, Icertis/ProcureCon, Ironclad, GEP, the MCPoison/CurXecute CVEs on NVD, Anthropic's MCP announcement, RFC 8707/9700, OAuth 2.1, the MCP auth spec), and each post carries 3 internal links to related library posts. One claim from the source copy — a "November 2025" date on the WhatsApp MCP exfil case — could not be verified and was dropped; the case itself is cited to Docker's writeup. Covers come from the autogeneration pipeline via the standard /library/<slug>/cover.jpg path.
The latest updates on your projects. Learn more about Vercel for GitHub. |
PR SummaryLow Risk Overview
No application code changes; cover images are referenced but not committed in this diff (autogen pipeline). Reviewed by Cursor Bugbot for commit a0989bb. Configure here. |
waleedlatif1
commented
Jul 24, 2026
@cursor review |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 2e45cc5. Configure here.
Greptile SummaryAdds three dated AEO library guides:
Confidence Score: 5/5The PR appears safe to merge. No blocking failure remains within the scope of the previous review thread. Important Files Changed
Reviews (2): Last reviewed commit: "fix(library): correct two unverifiable c..." | Re-trigger Greptile |
Uh oh!
There was an error while loading. Please reload this page.
Accuracy pass on the three new posts turned up two claims that could not be substantiated: - HIPAA compliance: the procurement post claimed Sim has "SOC2 and HIPAA compliance," but the canonical compliance data (lib/compare/data/sim.ts) states SOC2 only, and explicitly that Sim offers self-hosting "beyond SOC2, rather than additional certifications." Removed HIPAA; kept SOC2 plus self-hosting for data residency. (The same claim exists in ~5 pre-existing library posts and should be corrected separately.) - "more than 18,000 servers were listed on MCP Market": no source substantiates this figure. Replaced with "thousands of community-built servers," which the ecosystem supports, keeping the Anthropic and MCP Market links. Every other third-party claim was verified against a primary source (both CVEs on NVD, RFC 8707 title, RFC 9700 as January 2025, and all six survey statistics).
waleedlatif1
commented
Jul 24, 2026
waleedlatif1
commented
Jul 24, 2026
@cursor review |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit a0989bb. Configure here.
Uh oh!
There was an error while loading. Please reload this page.
Summary
Three new AEO library guides, each dated into a recent empty day in the posting calendar so publication is spread out rather than dumped on one day:
ai-agent-observabilityai-agents-in-procurementmcp-securityNote the three provided slugs were
/blog/..., but the content is textbook AEO/GEO (focus keyword, meta description, key takeaways, FAQ) and you asked for the library — so they live at/library/<slug>, matching the section's purpose.canonicaland internal links use/library/.Citations — every claim traced to a verified primary source
Per
.claude/rules/landing-seo-geo.md, every third-party factual claim carries an outbound citation, and I verified each source actually substantiates the claim before linking it (not just that the URL resolves):One correction to the source copy: it stated the WhatsApp MCP flaw was found "In November 2025." I could not verify that date (the disclosure was earlier in 2025), so I dropped the specific month rather than assert it — the case itself is cited to Docker's writeup. Per the rule: an unlinked/undated claim beats a wrong one.
Internal links: 3 per post to related library posts (e.g. procurement → AI agents vs RPA, MCP security → what an MCP server is). No self-links; all internal targets exist.
Covers
Cover art comes from your autogeneration pipeline. Each post references the standard
ogImage: /library/<slug>/cover.jpgpath; I did not commit placeholder art. Until autogen runs, the hero image at those three paths will 404 — flagging so it's not a surprise.Testing
Verified against a running dev server:
/libraryindex with correct dates.target="_blank" rel="noopener noreferrer"(5/5, 4/4, 9/9); internal links carry neither. (This relies on the MDX-anchor fix from improvement(library): add citations and internal links, correct stale pricing #5913, now on staging.)bun run lintclean;check:boundaries,check:api-validation:strict,check:client-boundaryall pass.Heads-up unrelated to this PR:
bunx tscreports 5 errors inproviders/anthropic/core.ts(Anthropic SDKOutputConfig/output_configtypings). These are pre-existing on staging — this PR adds only MDX, whichtscdoesn't compile — but worth a look since they'll trip a full typecheck.Type of Change
Checklist