/** * MCP Client Foundation — evidence integration (2.13.0). * * MCP tool invocations become first-class Jensen evidence through the existing * L3 Evidence Archive (`EvidenceArchive`). The durable payload is an * `McpEvidence` JSON document stored under kind `tool-result` with a * deterministic, content-addressed id — so `retrieve_evidence` can rehydrate * "I queried the real external system and this is what it reported." * * Secret hygiene: environment contents are never embedded; the archive's * conservative redaction additionally scrubs credential-shaped values before * persistence. */ import type { EvidenceArchive } from "../context-runtime/evidence-archive.js"; import type { McpEvidence, McpServerSession, McpToolResult } from "./mcp-types.js"; /** Deterministic evidence source identity for a (server, tool) pair. */ export declare function mcpEvidenceSource(serverId: string, toolName: string): string; export interface BuildMcpEvidenceInput { result: McpToolResult; /** argv identity for diagnostics; env contents are never included. */ serverCommand: string; session: McpServerSession; /** Safe argument representation (redacted at archive time if needed). */ arguments?: Readonly>; } /** * Build the durable MCP evidence payload. On failure paths this deliberately * carries failure metadata (never a success claim); on success it carries a * bounded result summary rather than unbounded raw content. */ export declare function buildMcpEvidence(input: BuildMcpEvidenceInput): McpEvidence; /** * Persist MCP evidence into the existing Evidence Archive and return its * deterministic evidence id. The archive redacts and hashes the payload, so the * same invocation always resolves to the same reference. */ export declare function recordMcpEvidence(archive: EvidenceArchive, evidence: McpEvidence): Promise; //# sourceMappingURL=mcp-evidence.d.ts.map