technical-answer-validator 0.1.0__tar.gz → 0.1.1__tar.gz

technical_answer_validator-0.1.1/.github/workflows/publish-mcp-registry.yml

@@ -0,0 +1,29 @@
+name: Publish MCP server to Registry
+
+on:
+  workflow_dispatch:
+  push:
+    tags:
+      - "v*"
+
+permissions:
+  contents: read
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      id-token: write
+    steps:
+      - uses: actions/checkout@v5
+      - name: Install MCP Publisher
+        run: |
+          curl -L "https://github.com/modelcontextprotocol/registry/releases/latest/download/mcp-publisher_linux_amd64.tar.gz" | tar xz mcp-publisher
+          chmod +x mcp-publisher
+      - name: Validate server descriptor
+        run: ./mcp-publisher validate server.json
+      - name: Authenticate to MCP Registry
+        run: ./mcp-publisher login github-oidc
+      - name: Publish server metadata
+        run: ./mcp-publisher publish server.json

technical_answer_validator-0.1.1/PKG-INFO

@@ -0,0 +1,35 @@
+Metadata-Version: 2.5
+Name: technical-answer-validator
+Version: 0.1.1
+Summary: MCP and REST tools for deterministic rubric-based technical answer review
+License-Expression: MIT
+License-File: LICENSE
+Requires-Python: >=3.10
+Requires-Dist: mcp==2.2.0
+Description-Content-Type: text/markdown
+
+# Technical Answer Validator
+
+
+<!-- mcp-name: io.github.Christofer566/technical-answer-validator -->
+
+
+A tiny, deterministic answer review tool for AI agents, available over **MCP stdio** and as a REST API. Each caller supplies the concepts, accepted synonyms, numeric requirements, and answer text for a single evaluation. It does not include a question bank or answer corpus.
+
+
+This is an **assistive practice tool**, not an official certification exam grader. Keyword matching can miss semantically correct paraphrases and can accept misleading surface matches. Users should review the supplied rubric and every result.
+
+
+## Run locally
+
+
+Python 3.10+; the REST server uses the standard library. The MCP adapter uses the official Python SDK 2.2.0.
+
+
+```powershell
+$env:TAV_API_KEY = "replace-with-a-long-random-secret-at-least-24-characters"
+python -m tav_api
+```
+
+
+The service listens on `127.0.0.1:8080` by default. To change it, set `TAV_HOST` and `TAV_PORT`. Local single-key mode refuses to start without a `TAV_API_KEY` of at least 24 characters. For deployment, create a distinct key per caller with `python scripts/create_api_key.py CLIENT_ID` and configure `TAV_API_KEYS` as a JSON object mapping each client ID to the generated SHA-256 digest. Store the one-time raw key with that client; do not store or commit it in this repository. When `TAV_API_KEYS` is set, it takes precedence over `TAV_API_KEY`.

technical_answer_validator-0.1.1/README.md

@@ -0,0 +1,25 @@
+# Technical Answer Validator
+
+
+<!-- mcp-name: io.github.Christofer566/technical-answer-validator -->
+
+
+A tiny, deterministic answer review tool for AI agents, available over **MCP stdio** and as a REST API. Each caller supplies the concepts, accepted synonyms, numeric requirements, and answer text for a single evaluation. It does not include a question bank or answer corpus.
+
+
+This is an **assistive practice tool**, not an official certification exam grader. Keyword matching can miss semantically correct paraphrases and can accept misleading surface matches. Users should review the supplied rubric and every result.
+
+
+## Run locally
+
+
+Python 3.10+; the REST server uses the standard library. The MCP adapter uses the official Python SDK 2.2.0.
+
+
+```powershell
+$env:TAV_API_KEY = "replace-with-a-long-random-secret-at-least-24-characters"
+python -m tav_api
+```
+
+
+The service listens on `127.0.0.1:8080` by default. To change it, set `TAV_HOST` and `TAV_PORT`. Local single-key mode refuses to start without a `TAV_API_KEY` of at least 24 characters. For deployment, create a distinct key per caller with `python scripts/create_api_key.py CLIENT_ID` and configure `TAV_API_KEYS` as a JSON object mapping each client ID to the generated SHA-256 digest. Store the one-time raw key with that client; do not store or commit it in this repository. When `TAV_API_KEYS` is set, it takes precedence over `TAV_API_KEY`.

{technical_answer_validator-0.1.0 → technical_answer_validator-0.1.1}/pyproject.toml

@@ -2,9 +2,10 @@
 requires = ["hatchling>=1.27,<2"]
 build-backend = "hatchling.build"
 
+
 [project]
 name = "technical-answer-validator"
-version = "0.1.0"
+version = "0.1.1"
 description = "MCP and REST tools for deterministic rubric-based technical answer review"
 readme = "README.md"
 requires-python = ">=3.10"
@@ -12,18 +13,22 @@ license = "MIT"
 license-files = ["LICENSE"]
 dependencies = ["mcp==2.2.0"]
 
+
 [project.scripts]
 tav-mcp = "mcp_server:main"
 tav-api = "tav_api:main"
 
+
 [tool.hatch.build.targets.wheel]
 only-include = ["mcp_server.py", "tav_core.py", "tav_api.py"]
 
+
 [tool.hatch.build.targets.wheel.force-include]
 "mcp_server.py" = "mcp_server.py"
 "tav_core.py" = "tav_core.py"
 "tav_api.py" = "tav_api.py"
 
+
 [tool.hatch.build.targets.sdist]
 only-include = [
   ".dockerignore", ".env.example", ".gitignore", "Dockerfile", "NOTICE.md",
@@ -33,5 +38,5 @@ only-include = [
   "tav_api.py", "tav_core.py", "uv.lock", ".github", "scripts", "tests"
 ]
 
+
 [tool.pytest.ini_options]
-testpaths = ["tests"]

{technical_answer_validator-0.1.0 → technical_answer_validator-0.1.1}/server.json

@@ -1,9 +1,9 @@
 {
   "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
-  "name": "io.github.christofer566/technical-answer-validator",
+  "name": "io.github.Christofer566/technical-answer-validator",
   "title": "Technical Answer Validator",
-  "description": "Deterministic rubric-based technical answer feedback for AI agents; review required, not an official grade.",
-  "version": "0.1.0",
+  "description": "Rubric-based technical answer feedback for AI agents. Human review required; not an official grade.",
+  "version": "0.1.1",
   "repository": {
     "url": "https://github.com/Christofer566/technical-answer-validator",
     "source": "github"
@@ -13,8 +13,9 @@
       "registryType": "pypi",
       "registryBaseUrl": "https://pypi.org",
       "identifier": "technical-answer-validator",
-      "version": "0.1.0",
+      "version": "0.1.1",
       "transport": { "type": "stdio" }
     }
   ]
 }
+

{technical_answer_validator-0.1.0 → technical_answer_validator-0.1.1}/uv.lock

@@ -863,7 +863,7 @@ wheels = [
 
 [[package]]
 name = "technical-answer-validator"
-version = "0.1.0"
+version = "0.1.1"
 source = { editable = "." }
 dependencies = [
     { name = "mcp" },

technical_answer_validator-0.1.0/PKG-INFO

@@ -1,92 +0,0 @@
-Metadata-Version: 2.5
-Name: technical-answer-validator
-Version: 0.1.0
-Summary: MCP and REST tools for deterministic rubric-based technical answer review
-License-Expression: MIT
-License-File: LICENSE
-Requires-Python: >=3.10
-Requires-Dist: mcp==2.2.0
-Description-Content-Type: text/markdown
-
-# Technical Answer Validator
-
-<!-- mcp-name: io.github.christofer566/technical-answer-validator -->
-
-A tiny, deterministic answer review tool for AI agents, available over **MCP stdio** and as a REST API. Each caller supplies the concepts, accepted synonyms, numeric requirements, and answer text for a single evaluation. It does not include a question bank or answer corpus.
-
-This is an **assistive practice tool**, not an official certification exam grader. Keyword matching can miss semantically correct paraphrases and can accept misleading surface matches. Users should review the supplied rubric and every result.
-
-## Run locally
-
-Python 3.10+; the REST server uses the standard library. The MCP adapter uses the official Python SDK 2.2.0.
-
-```powershell
-$env:TAV_API_KEY = "replace-with-a-long-random-secret-at-least-24-characters"
-python -m tav_api
-```
-
-The service listens on `127.0.0.1:8080` by default. To change it, set `TAV_HOST` and `TAV_PORT`. Local single-key mode refuses to start without a `TAV_API_KEY` of at least 24 characters. For deployment, create a distinct key per caller with `python scripts/create_api_key.py CLIENT_ID` and configure `TAV_API_KEYS` as a JSON object mapping each client ID to the generated SHA-256 digest. Store the one-time raw key with that client; do not store or commit it in this repository. When `TAV_API_KEYS` is set, it takes precedence over `TAV_API_KEY`.
-
-## MCP for AI agents
-
-Install the pinned MCP SDK 2.2.0 in a virtual environment from the committed lockfile:
-
-```powershell
-uv sync --locked
-.\.venv\Scripts\Activate.ps1
-```
-
-The stdio MCP server exposes one tool: `evaluate_answer(rubric, answer)`. Configure an MCP host with the absolute path to the environment's Python and `mcp_server.py`. Example Claude Desktop configuration (replace paths):
-
-```json
-{
-  "mcpServers": {
-    "technical-answer-validator": {
-      "command": "C:\\path\\to\\technical-answer-validator\\.venv\\Scripts\\python.exe",
-      "args": ["C:\\path\\to\\technical-answer-validator\\mcp_server.py"]
-    }
-  }
-}
-```
-
-After publishing to PyPI, run with `uvx --from technical-answer-validator tav-mcp`. For local development use the `.venv` Python plus `mcp_server.py`. For Codex CLI or another MCP host, use its stdio server configuration with that command and script path. Restart the host, then ask it to list tools and call `evaluate_answer`. The stdio transport is local to the user's agent host and needs no internet endpoint or API key.
-
-The Codex TOML template is `codex-mcp-config.example.toml`; the Claude Desktop JSON template is `claude-mcp-config.example.json`. Replace both placeholder paths with absolute paths. Merge the block into the host configuration; do not overwrite other MCP servers or global settings.
-
-## Request
-
-`POST /v1/evaluate`
-
-```json
-{
-  "rubric": {
-    "required_concepts": ["isolation", "lockout tag"],
-    "accepted_synonyms": {"isolation": ["energy isolation"]},
-    "numeric_requirements": [],
-    "required_count": 2
-  },
-  "answer": "Apply energy isolation and attach a lockout tag."
-}
-```
-
-`accepted_synonyms` keys must exactly match a concept. `numeric_requirements` is an optional array such as `[{"value":"10","unit":"kN","tolerance":"0"}]`. Numbers in an answer are only checked when explicit requirements are provided. Concept score is matched concepts / required_count (defaults to the number of concepts), capped at 1.0; numeric failures apply a 50% score penalty. The verdict thresholds are `correct >= 0.8`, `partial >= 0.4`, otherwise `wrong`.
-
-## Response and errors
-
-Successful requests return `api_version`, `status`, `score`, `verdict`, matched/missing concepts, numeric check details, and `review_required: true`.
-
-Errors use JSON `{ "error": { "code": "...", "message": "..." } }`. Statuses include 400 (invalid request), 401 (missing/invalid key), 404, 405, 413 (body over 64 KiB), and 429 (over 60 requests/minute per client ID). The rate limit is 60 requests/minute per authenticated client ID, in memory, and resets when the process restarts. Daily request/success/client-error/rate-limited counters are persisted in SQLite without answer text and expire after 90 days. `GET /v1/usage` returns only the caller's current UTC-day counts. Retain and back up the usage volume as desired; it contains client IDs and aggregates only.
-
-## Privacy and deployment limits
-
-The server does not log request bodies or answers. It stores daily counts keyed by client ID and request timestamps in process memory for REST rate limiting. The **stdio MCP option runs locally inside the agent host** and sends no requests to this HTTP server. The REST API is containerized and keeps usage counters in a persistent volume. Before public service, terminate TLS at a reverse proxy, set proxy-level rate/concurrency limits, deploy from a secret manager, monitor the host, and publish a data-retention/contact policy. The app-level per-client rate limit resets on restart and is not a substitute for edge controls.
-
-## Verify
-
-```powershell
-python -m unittest discover -s tests -v
-```
-
-The OpenAPI contract is in `openapi.yaml`; the draft official MCP Registry descriptor is `server.json`, with publication steps in `PUBLISHING.md`. Run locally with Docker Compose after copying `.env.example` to `.env` and adding a private key; Compose publishes the service only on loopback, so configure an HTTPS reverse proxy separately. `compose.yaml` persists aggregate usage in a named volume and applies a read-only root filesystem, dropped Linux capabilities, and resource limits.
-
-These tests check API and grading behavior; they do not establish professional exam accuracy.

technical_answer_validator-0.1.0/README.md

@@ -1,82 +0,0 @@
-# Technical Answer Validator
-
-<!-- mcp-name: io.github.christofer566/technical-answer-validator -->
-
-A tiny, deterministic answer review tool for AI agents, available over **MCP stdio** and as a REST API. Each caller supplies the concepts, accepted synonyms, numeric requirements, and answer text for a single evaluation. It does not include a question bank or answer corpus.
-
-This is an **assistive practice tool**, not an official certification exam grader. Keyword matching can miss semantically correct paraphrases and can accept misleading surface matches. Users should review the supplied rubric and every result.
-
-## Run locally
-
-Python 3.10+; the REST server uses the standard library. The MCP adapter uses the official Python SDK 2.2.0.
-
-```powershell
-$env:TAV_API_KEY = "replace-with-a-long-random-secret-at-least-24-characters"
-python -m tav_api
-```
-
-The service listens on `127.0.0.1:8080` by default. To change it, set `TAV_HOST` and `TAV_PORT`. Local single-key mode refuses to start without a `TAV_API_KEY` of at least 24 characters. For deployment, create a distinct key per caller with `python scripts/create_api_key.py CLIENT_ID` and configure `TAV_API_KEYS` as a JSON object mapping each client ID to the generated SHA-256 digest. Store the one-time raw key with that client; do not store or commit it in this repository. When `TAV_API_KEYS` is set, it takes precedence over `TAV_API_KEY`.
-
-## MCP for AI agents
-
-Install the pinned MCP SDK 2.2.0 in a virtual environment from the committed lockfile:
-
-```powershell
-uv sync --locked
-.\.venv\Scripts\Activate.ps1
-```
-
-The stdio MCP server exposes one tool: `evaluate_answer(rubric, answer)`. Configure an MCP host with the absolute path to the environment's Python and `mcp_server.py`. Example Claude Desktop configuration (replace paths):
-
-```json
-{
-  "mcpServers": {
-    "technical-answer-validator": {
-      "command": "C:\\path\\to\\technical-answer-validator\\.venv\\Scripts\\python.exe",
-      "args": ["C:\\path\\to\\technical-answer-validator\\mcp_server.py"]
-    }
-  }
-}
-```
-
-After publishing to PyPI, run with `uvx --from technical-answer-validator tav-mcp`. For local development use the `.venv` Python plus `mcp_server.py`. For Codex CLI or another MCP host, use its stdio server configuration with that command and script path. Restart the host, then ask it to list tools and call `evaluate_answer`. The stdio transport is local to the user's agent host and needs no internet endpoint or API key.
-
-The Codex TOML template is `codex-mcp-config.example.toml`; the Claude Desktop JSON template is `claude-mcp-config.example.json`. Replace both placeholder paths with absolute paths. Merge the block into the host configuration; do not overwrite other MCP servers or global settings.
-
-## Request
-
-`POST /v1/evaluate`
-
-```json
-{
-  "rubric": {
-    "required_concepts": ["isolation", "lockout tag"],
-    "accepted_synonyms": {"isolation": ["energy isolation"]},
-    "numeric_requirements": [],
-    "required_count": 2
-  },
-  "answer": "Apply energy isolation and attach a lockout tag."
-}
-```
-
-`accepted_synonyms` keys must exactly match a concept. `numeric_requirements` is an optional array such as `[{"value":"10","unit":"kN","tolerance":"0"}]`. Numbers in an answer are only checked when explicit requirements are provided. Concept score is matched concepts / required_count (defaults to the number of concepts), capped at 1.0; numeric failures apply a 50% score penalty. The verdict thresholds are `correct >= 0.8`, `partial >= 0.4`, otherwise `wrong`.
-
-## Response and errors
-
-Successful requests return `api_version`, `status`, `score`, `verdict`, matched/missing concepts, numeric check details, and `review_required: true`.
-
-Errors use JSON `{ "error": { "code": "...", "message": "..." } }`. Statuses include 400 (invalid request), 401 (missing/invalid key), 404, 405, 413 (body over 64 KiB), and 429 (over 60 requests/minute per client ID). The rate limit is 60 requests/minute per authenticated client ID, in memory, and resets when the process restarts. Daily request/success/client-error/rate-limited counters are persisted in SQLite without answer text and expire after 90 days. `GET /v1/usage` returns only the caller's current UTC-day counts. Retain and back up the usage volume as desired; it contains client IDs and aggregates only.
-
-## Privacy and deployment limits
-
-The server does not log request bodies or answers. It stores daily counts keyed by client ID and request timestamps in process memory for REST rate limiting. The **stdio MCP option runs locally inside the agent host** and sends no requests to this HTTP server. The REST API is containerized and keeps usage counters in a persistent volume. Before public service, terminate TLS at a reverse proxy, set proxy-level rate/concurrency limits, deploy from a secret manager, monitor the host, and publish a data-retention/contact policy. The app-level per-client rate limit resets on restart and is not a substitute for edge controls.
-
-## Verify
-
-```powershell
-python -m unittest discover -s tests -v
-```
-
-The OpenAPI contract is in `openapi.yaml`; the draft official MCP Registry descriptor is `server.json`, with publication steps in `PUBLISHING.md`. Run locally with Docker Compose after copying `.env.example` to `.env` and adding a private key; Compose publishes the service only on loopback, so configure an HTTPS reverse proxy separately. `compose.yaml` persists aggregate usage in a named volume and applies a read-only root filesystem, dropped Linux capabilities, and resource limits.
-
-These tests check API and grading behavior; they do not establish professional exam accuracy.