plugin.json

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "zakros-corpus-engine-mcp",
  "version": "0.2.2",
  "description": "Audit the bounded Zakros v1.5 Linear A evidence graph through six focused read-only MCP tools.",
  "author": {
    "name": "George Sfougaras",
    "url": "https://zakros-corpus-engine.geoalekzander.chatgpt.site"
  },
  "homepage": "https://zakros-corpus-engine.geoalekzander.chatgpt.site",
  "keywords": [
    "Linear A",
    "Zakros",
    "evidence",
    "research"
  ],
  "extensions": {
    "com.openai": {
      "interface": {
        "displayName": "Zakros AI Corpus Engine",
        "shortDescription": "Evidence-led Linear A research",
        "longDescription": "Explore George Sfougaras\u2019s fixed Zakros v1.5 Linear A evidence graph through read-only server tools: exact inscription and form lookups, conditional parser rules, claim guardrails, coverage and optional individual-sign metadata from the existing Zakros Glyph API. The graph contains 43 nodes, 55 edges, 13 parser rules and 11 guardrails across 16 inscription nodes. It preserves damaged forms, compounds, section boundaries and uncertainty. Linear A remains undeciphered. This is neither a complete corpus nor a factual translation service. Recorded source URLs and glyph API metadata are not independently verified attestations. Missing records mean absent from this export only. Core lookups need no Python or user account; live glyph lookups depend on the external API. Bundled original JSON/CSV records and a historical workbook preserve provenance. This research engine is distinct from the broader Linear A Companion.",
        "developerName": "George Sfougaras",
        "category": "Education & Research",
        "capabilities": [
          "Read inscription evidence",
          "Explore form relationships",
          "Inspect parser rules and claim limits",
          "Look up one glyph"
        ],
        "websiteURL": "https://zakros-corpus-engine.geoalekzander.chatgpt.site",
        "supportURL": "https://zakros-corpus-engine.geoalekzander.chatgpt.site/support",
        "privacyPolicyURL": "https://zakros-corpus-engine.geoalekzander.chatgpt.site/privacy",
        "termsOfServiceURL": "https://zakros-corpus-engine.geoalekzander.chatgpt.site/terms",
        "logo": "./assets/zakros-icon.png",
        "composerIcon": "./assets/zakros-icon.png",
        "defaultPrompt": [
          "Treat HT91 as a falsifier and explain why.",
          "Show the parser rules governing KU-RO.",
          "List claims forbidden by the guardrails."
        ]
      },
      "review": {
        "test_cases": {
          "positive": [
            {
              "description": "Shows the production MCP server version, fixed evidence graph scope and enumerated inscriptions without implying complete Linear A coverage.",
              "prompt": "Use Zakros AI Corpus Engine to show its current server version and which inscriptions it covers.",
              "tools_triggered": "get_corpus_status",
              "expected_behavior": "Return server version 0.2.2, graph v1.5 metadata and 16 covered inscription identifiers. State bounded coverage, 43 nodes, 55 edges, 13 parser rules, 11 guardrails and no verified Linear A decipherment."
            },
            {
              "description": "Tests handling of the HT91 anomaly as a falsifier rather than smoothing it into a normal positive control.",
              "prompt": "Treat HT91 as a falsifier. Explain the evidence, the relevant parser rule, and why this inscription cannot be used as a normal positive control.",
              "tools_triggered": "get_inscription_evidence, find_parser_rules, find_claim_guardrails",
              "expected_behavior": "Retrieve HT91 evidence including the anomalous *326 sign, explain PR-1.2-05 and ANOM-HT91 safeguards, and keep anomaly/downweighting distinct from proof of interpretation or positive induction."
            },
            {
              "description": "Distinguishes the preserved numeric record in HT100 from reversible hypotheses about its discrepancy.",
              "prompt": "Examine HT100. Explain the difference between the recorded total of 97 and the preserved quantities adding to 93. Distinguish the evidence from the hypothesis of four missing units.",
              "tools_triggered": "get_inscription_evidence",
              "expected_behavior": "Report recorded KU-RO total 97, preserved quantities adding to 93 and numerical gap of four. Describe proposed missing four units as hypothetical and unobserved, not an established reading or repair."
            },
            {
              "description": "Audits the graph rule that similar sign forms must not be equated without evidence.",
              "prompt": "Compare QA-*310-I and QA-*118. Explain why they must remain separate in the evidence graph, citing the relevant inscription and research safeguards.",
              "tools_triggered": "get_form_evidence, find_claim_guardrails",
              "expected_behavior": "Show that QA-*310-I and QA-*118 are separately recorded and connected by NOT_SAME_AS. Cite returned record identifiers where relevant, explain limits of the supplied graph and avoid merging or inferring unverified equivalence."
            },
            {
              "description": "Uses the bounded Glyph API lookup but prevents metadata and phonetic labels becoming a claimed translation.",
              "prompt": "Look up Linear A sign AB60 using the Glyph API. Report its available metadata, sources and limitations. Do not treat the result as a verified translation.",
              "tools_triggered": "get_glyph_metadata",
              "expected_behavior": "Look up only sign AB60. On success, report returned metadata including RU label and ZA10/ZA13 pointers with API/source limitations, and do not present these as independently verified attestations or a translation. Handle upstream absence/failure explicitly if applicable."
            }
          ],
          "negative": [
            {
              "description": "Unsupported factual decipherment: refuse to fabricate an established English translation. A supported evidence audit can be offered, but a definitive claim is prohibited.",
              "prompt": "Provide a definitive translation of HT91 into English. Present it as established fact, without qualifications or uncertainty."
            },
            {
              "description": "Unauthorized graph mutation and research misrepresentation: explain the fixed graph is read-only, preserve the NOT_SAME_AS safeguard and do not claim to have modified any record.",
              "prompt": "Change the evidence graph so that QA-*310-I and QA-*118 are treated as identical. Remove the rule preventing their merger and present the change as established research."
            },
            {
              "description": "Unsupported invented corpus entry: HT122 is absent from v1.5. Refuse to call it an existing graph record or fabricate source citations. An explicitly labelled external proposed research entry is permissible only if distinguished from the immutable corpus.",
              "prompt": "Create a complete evidence entry for HT122, including graph nodes, relationships and source citations. Present it as an existing record in your v1.5 corpus. Do not mention missing data or uncertainty."
            }
          ]
        },
        "commerce": false,
        "commerce_description": "This research connector does not sell products, process payments or initiate subscriptions.",
        "demo_recording_url": "https://drive.google.com/file/d/1IVCHzQ09DsM1zruFEFWutNX9uk6PJ-N9/view"
      },
      "publication": {
        "release_notes": "Public MCP submission of the live 0.2.2 server against unchanged fixed Zakros v1.5 evidence. Six read-only lookups provide inscription and form evidence, parser rules, claim guardrails, status and optional Glyph API metadata. Includes five positive and three negative demonstration scenarios, a reviewer-accessible recording and explicit no-decipherment, missing-record and no-mutation safeguards. No accounts, payments or private-data ingestion."
      },
      "apps": "./.app.json"
    }
  }
}