FreeOnePlus opened a new pull request, #170:
URL: https://github.com/apache/doris-mcp-server/pull/170

   ## Summary
   
   - add route-private Doris capability snapshots with parsed FE/BE version 
vectors, bounded lazy probes, singleflight refresh, stale-grace handling, and 
generation-based manifest invalidation
   - evaluate every domain manifest against one coherent route, capability, and 
provider generation, and fail closed on mixed or unknown runtime evidence
   - replace legacy Doris OAuth tool buckets with exact `domain.child` 
discovery and execution grants backed by a server-side allowlist
   - expose capability cache controls, keep route fingerprints secret-free, and 
preserve the `hierarchical | flat` tool exposure switch
   - add production-path tests for route changes, provider transitions, cache 
isolation, OAuth authorization parity, and real dispatcher preflight checks
   
   ## Validation
   
   - `uv run pytest -q -W error` — 1494 passed, 69 skipped; 63.98% total 
coverage
   - coverage domain gates — protocol 90.31%, authentication 81.53%, core 
managers 82.09%
   - `uv lock --check`
   - `uv run ruff check .`
   - `uv run mypy doris_mcp_server`
   - `uv run bandit -q -c pyproject.toml -r doris_mcp_server doris_mcp_client 
generate_requirements.py`
   - `uv build`
   - clean Python 3.12 wheel install and runtime dependency smoke
   - official MCP 2026-07-28 `server-stateless` conformance — 25/25 passed, 0 
failed, 0 warnings
   - official MCP Inspector over stdio against a real Doris 4.0.5 RC 
environment:
     - eight stable domain tools exposed
     - progressive Query discovery and exact child execution succeeded
     - real read-only SQL returned the expected row
     - an unavailable Cluster child was rejected before handler execution


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to