Add cookbook: cross-database CVE verification with TensorFeed (hosted MCP)#2683
Open
RipperMercs wants to merge 3 commits into
Open
Add cookbook: cross-database CVE verification with TensorFeed (hosted MCP)#2683RipperMercs wants to merge 3 commits into
RipperMercs wants to merge 3 commits into
Conversation
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
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
Adds an MCP-pattern cookbook demonstrating anti-hallucination CVE triage using the OpenAI Responses API's native MCP tool integration. Composes three independent vulnerability databases (MITRE CVE List, CISA Known Exploited Vulnerabilities, FIRST.org EPSS) via TensorFeed.ai's hosted MCP server.
What it teaches
The premise: the actual production failure mode of security agents isn't hallucination, it's acting on a single source. A triage agent that judges a CVE off one database can be wrong without ever fabricating anything. The fix is corroboration. The notebook shows the pattern in 10 cells using
client.responses.create(...)withtools=[{type: "mcp", server_url: "https://tensorfeed.ai/api/mcp", ...}]:tools[].type = "mcp"(no manual JSON-RPC loop)confirmed_byso the user can audit which databases backed the answerWhy this fits examples/mcp
The existing
examples/mcp/mcp_tool_guide.ipynbintroduces the Responses API's MCP tool with a single-server demo (gitmcp). This adds a real-world pattern showing multi-tool composition for cross-source corroboration within a single Responses call - a common need for security, compliance, and finance agents that must not act on a single source.Files
examples/mcp/tensorfeed_cve_verification.ipynb— 10 cells (markdown + code interleaved per the cookbook style)registry.yamlentry under examples/mcp with tags[mcp, agents, security]authors.yamlentry forripperQuality checks
OPENAI_API_KEYfrom environment, no hardcoded secretsgpt-5.1); replace withgpt-4.1if preferredtools/listreturns 17 tools, the three referenced (get_cve_record,get_kev_catalog,get_epss_score) all return ok:true on representative queries (verified 2026-05-09)License + redistribution posture
Underlying data:
The notebook itself is MIT under the cookbook repo's license.
About the author
Ripper builds TensorFeed.ai, a free machine-readable AI ecosystem data hub for AI agents. TF is also published as a hosted server in the official Model Context Protocol Registry as
ai.tensorfeed/mcp-server. Recent submissions across the ecosystem: openai/skills#405, anthropics/skills#1114, anthropics/claude-cookbooks#611, anthropics/financial-services#156, anthropics/life-sciences#41, anthropics/knowledge-work-plugins#221.Note on the API-based commit method
This branch was authored via the GitHub Contents API rather than a local clone because the
examples/data/hotel_invoices/extracted_invoice_json /directory contains a trailing space in its name, which Windows refuses to check out. The three files in this PR are all in supported paths (examples/mcp/, rootregistry.yaml, rootauthors.yaml), so the commits are clean and reviewable normally; let me know if you'd like the branch reconstructed locally for any reason.