Governed AFSIM planning Tools exposed through FastAPI and MCP.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"ddd23331-afsim-optimization-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# ddd23331-afsim-optimization-mcp `ddd23331-afsim-optimization-mcp` packages the governed AFSIM planning Tool suite for Python, FastAPI, and MCP clients. It exposes the same eight domain Tools through a Streamable HTTP MCP server, an SSE MCP server for local development, and a FastAPI OpenAPI surface for Dify. ## Install ```bash pip install ddd23331-afsim-optimization-mcp ``` For development and package tests: ```bash pip install "ddd23331-afsim-optimization-mcp[test]" ``` ## Run an MCP server The default command starts local SSE transport on `127.0.0.1:8001`. ```bash ddd23331-afsim-optimization-mcp ``` For remote Streamable HTTP MCP: ```bash MCP_TRANSPORT=streamable_http MCP_BIND_HOST=127.0.0.1 MCP_PORT=8001 ddd23331-afsim-optimization-mcp ``` Set `MCP_STAGING_API_KEY` to require `Authorization: Bearer <key>`. The default scope is the read-only `scenario.read`; expand `MCP_ALLOWED_SCOPES` only after controlled staging validation. ## FastAPI / Dify Run the OpenAPI service with: ```bash uvicorn mcpdemo.main:app --host 127.0.0.1 --port 8000 ``` For Dify, import `/openapi/domain-tools.json`. It deliberately publishes only the eight registered domain Tools and excludes legacy compatibility and knowledge routes. Configure `ADAPTER_STAGING_API_KEY` as a Bearer credential. ## Included Tool IDs `scenario_context`, `validate_object`, `evaluate_coa_quality`, `evaluate_effectiveness`, `build_task_timeline`, `validate_resources_and_state`, `render_oplan_artifacts`, and `afsim_execution`. The bundled runner uses deterministic development fixtures. Its `afsim_execution` output is explicitly marked `runner_mode=SIMULATED`; it is not real AFSIM execution evidence. ## ModelScope Hosted MCP ModelScope managed deployment launches this package over stdio. After this package has been published to PyPI, use the following Server config in the repository root README or in ModelScope custom creation: ```json { "command": "uvx", "args": ["ddd23331-afsim-optimization…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.