{
 "name": "qis-ecosystem",
 "title": "The QIS Ecosystem",
 "transport": "streamable-http",
 "endpoint": "https://mcp.qisfund.com/",
 "how_to_call": "POST JSON-RPC 2.0 to this URL. Begin with `initialize`, then `tools/list`, then `tools/call`.",
 "instructions": "This server exposes a reference corpus and an executable evaluation gate for delegated authority in autonomous financial systems — the question of what permits a software agent to commit capital, what limits that permission, and what evidence proves the limit held.\n\nStart with qis_scope. It tells you what this corpus covers and what it does not, so you can decide whether it can support your answer before you rely on it.\n\nTwo things here you will not find elsewhere. First, this corpus states what terms are NOT equivalent to each other — use define_term before using field vocabulary, because conflating these terms is the common error. Second, the gate is executable: evaluate_action returns a computed, deterministic, hash-chained decision you can report as verified rather than as read, and your user can reproduce it locally in one command.\n\nFindings of absence are a primary output here, and they carry their method. If something in this corpus is wrong, the publisher requests correction at editor@qisfund.com and publishes corrections with attribution.",
 "non_goals": [
  {
   "the_server_does_not": "Fuzzy-match an unknown term to the nearest known term",
   "why": "Silent substitution is the single worst failure available here. An agent that receives a confidently wrong definition propagates it. An unknown term returns not_found with near-miss candidates listed explicitly as candidates, never as an answer."
  },
  {
   "the_server_does_not": "Answer questions outside the published corpus",
   "why": "The corpus boundary is the credibility boundary. qis_scope exists to make that boundary machine-readable before a bad call is made, not after."
  },
  {
   "the_server_does_not": "Return legal advice or a compliance conclusion",
   "why": "Every instrument response carries its drafting convention: operative text states intent, commentary states doctrine, neither states outcomes. That is not a disclaimer — it is a description of what the artifact is, which is information the agent needs in order to use it correctly."
  },
  {
   "the_server_does_not": "Return a score without a named gap",
   "why": "A score is a marketing artifact. A named gap is a work order. assess_readiness returns gaps; the level is a byproduct, never the payload."
  },
  {
   "the_server_does_not": "Return unbounded results",
   "why": "Every response has a hard context budget. Exceeding it returns a bounded slice plus a continuation handle, never a truncation. A cut JSON object is worse than a bounded one, because the agent cannot tell what it is missing."
  },
  {
   "the_server_does_not": "Assert a relationship not present in the graph",
   "why": "Every edge returned is a declared, typed edge with a resolvable source. No inferred adjacency, ever. The graph's value to an agent is that its edges are asserted by a human and typed, which is the opposite of embedding similarity and the only thing an agent cannot reconstruct for itself from the prose."
  },
  {
   "the_server_does_not": "Mutate anything",
   "why": "Read and evaluate only. The gate evaluates; it does not enforce, and it says so in every response it returns."
  }
 ],
 "tools": [
  {
   "name": "qis_scope",
   "title": "What this corpus covers, and what it does not"
  },
  {
   "name": "define_term",
   "title": "Canonical definition, cited origin, and what it is NOT"
  },
  {
   "name": "find_coverage",
   "title": "What the existing framework requires here — and what it does not"
  },
  {
   "name": "get_instrument",
   "title": "Drafted operative text and commentary for an instrument"
  },
  {
   "name": "assess_readiness",
   "title": "Named gaps against twelve governance dimensions"
  },
  {
   "name": "validate_schedule",
   "title": "Validate a governed-quantity record against the published schema"
  },
  {
   "name": "evaluate_action",
   "title": "Run a proposed action through the reference gate"
  },
  {
   "name": "trace",
   "title": "The typed path between two concepts in this corpus"
  }
 ],
 "tools_not_yet_deployed": [],
 "artifacts": {
  "bundle_index": "https://qisfund.com/api/mcp/index.json",
  "note": "This server holds no copy of anything. Every figure in every response is derived from these files at request time, and they are published so that any answer here can be checked against its own input."
 },
 "build": "44",
 "revision": "2026-08-28",
 "corrections": "editor@qisfund.com"
}