MystoraX MCP Server
# mystorax-host
The front-neutral distribution package for MystoraX.
For Claude Science, import this GitHub repository once. It intentionally
publishes exactly two skills:
- `use-mystorax` — universal provider/CLI access
- `use-mystorax-science` — the single consolidated Science capability
The skills contain no duplicated model, connector, tool, or specialist lists.
They discover the current catalog from MystoraX at execution time.
The NVIDIA BioNeMo Agent Toolkit remains a separate imported scientific-model
toolkit. `Codex Delegate` also remains separate because it is a narrow handoff
helper, not a duplicate Science product.
Retired names such as Axiom, CompBio, and Science OS are not separate products
or skills.
TDQS
Scored across 10 tools
Most tools target clearly distinct concerns: routing guide vs surfaces vs goal/job lifecycle vs science/axiom operations. However, some boundary overlap exists between mystorax_surfaces, mystorax_capability_lookup, and mystorax_axiom_tool_search—all three concern lookup/discovery of capabilities, and an agent could easily confuse which returns what. mystorax_axiom_tool_search vs mystorax_axiom_tool_call are distinct but could be misselected at the edge.
All tool names follow a consistent mystorax_ snake_case prefix pattern. However, the post-prefix names mix conventions: some are verb_noun (submit_goal, call_tool, search), some are noun-oriented (surfaces, job_status, science_status, routing_guide), and 'wait_stream_hint' and 'capability_lookup' vary in style. There's no consistent verb-first pattern across the set, making it less predictable.
10 tools is a well-scoped count for a platform orchestration server covering routing doctrine, capability discovery, goal/job submission, and science operations. Each tool serves a distinct functional area and the count feels appropriate—not bloated, not thin.
The surface covers the core lifecycle: routing doctrine, capability discovery, goal submission, job status polling, wait-stream handling, science readiness, and tool execution. The main gap is the absence of any cancellation, update, or error-recovery tool for submitted goals/jobs, so agents cannot abort or modify a running job. Minor gaps for resume campaign control, but core workflows are covered.