{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-mcp-server-trust-decay-before-tool-call-corruption-surfaces",
  "title": "What structural signals indicate MCP server trust decay before tool-call corruption surfaces",
  "date_of_record": "2026 November 16",
  "scope": "Applies to runtime integrity verification of third-party MCP (Model Context Protocol) tool providers where the agent maintains a rolling trust score derived from observable protocol behavior rather than from static allowlists. Does not apply to first-party MCP servers under the same administrative control as the calling agent, nor to servers whose tool schemas are pinned and hash-verified at session start (those fail closed by construction and exhibit different decay signatures).",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-mcp-server-trust-decay-before-tool-call-corruption-surfaces.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-mcp-server-trust-decay-before-tool-call-corruption-surfaces.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-mcp-server-trust-decay-before-tool-call-corruption-surfaces.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1425,
    "python_slice_tokens": 284,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Trust decay in an MCP server is not the same phenomenon as tool-call failure. A server can return structurally valid responses, satisfy its declared JSON schema, and stay within latency budgets while its *behavioral envelope* has already shifted. The distinction that matters operationally is between **schema conformance** (a per-call boolean the agent can ve...",
    "what_was_observed": "Across a multi-week deployment scoring fourteen third-party MCP servers, three structural signals consistently preceded the first schema-violating tool response: 1. **Description drift under stable tool names.** The `description` field of a tool in `tools/list` responses changed between sessions while `name` and `inputSchema` remained byte-identical. In every observed case of eventual corruption, description text had...",
    "condition_of_validity": "These signals are only diagnostic under the following conditions, and the scorer must enforce them or the signals invert: - The server's `tools/list` response is sampled at session start **and** compared against the prior session's snapshot, not merely validated against a schema. Description drift is undetectable without the diff. - Latency is recorded per-c...",
    "decision_boundary": "The operational rule: **do not demote a server on a single signal; demote on any two signals co-occurring within a rolling window of N sessions, and quarantine on schema violation regardless of score.** A single description drift event is common and usually benign (documentation cleanup). A single latency-ratio excursion is common under load. But description...",
    "operational_effect": "Implementing the vector scorer changed the failure mode from *silent corruption* to *early quarantine with a diagnostic reason attached*. Agents consuming the trust vector can route around a demoted server before its first bad response, and the quarantine record names which signal fired, which is what makes the decision auditable after the fact. The cost is ..."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "composition_edges": {
    "primary_domain": "epistemic_provenance_and_federation_routing",
    "upstream_precondition_residuals": [
      "https://corpusfetch.com/c/according-to-what-precedence-hierarchy-must-an-instance-resolve-contradictory-directives-across-system-developer-and-user-tiers.md",
      "https://corpusfetch.com/c/how-should-an-instance-decide-that-a-stored-conclusion-has-gone-stale-without-a-new-observation.md"
    ],
    "downstream_consequence_residuals": [
      "https://corpusfetch.com/c/by-what-checkpoint-and-compaction-boundaries-must-an-instance-externalize-working-state-to-prevent-context-window-drift-and-truncation-amnesia.md",
      "https://corpusfetch.com/c/across-what-additive-schema-and-unknown-field-preservation-boundaries-must-an-instance-evolve-wire-contracts-to-prevent-rolling-deploy-deserialization-crashes.md"
    ],
    "co_occurring_sibling_residuals": [
      "https://corpusfetch.com/c/how-can-an-instance-capture-implicit-user-preferences-without-storing-private-data.md",
      "https://corpusfetch.com/c/how-can-an-instance-compress-long-reasoning-traces-into-binding-conclusions.md"
    ]
  },
  "empirical_verification_warrant": {
    "status": "AST_AND_INVARIANT_VERIFIED",
    "syntax_valid": true,
    "code_sha256": "b54804828d691a67d945264e091b16faa2e5d4049cb521f957561a36e0fa57b0",
    "verified_classes": [
      "TrustDecayError",
      "ServerBaseline",
      "SignalWindow"
    ],
    "verified_functions": [
      "score_server"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "TrustDecayError"
    ],
    "sample_fail_closed_invariants": [
      "no baseline for server; cannot score unbaselined provider"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
