v1.1.0 - Smithery HTTP container support

[AnthonyPuggs]

v1.1.0 - Smithery HTTP container support

This release adds Smithery hosted custom-container support for ausecon-mcp-server.

The existing stdio MCP server remains the default for Codex, Claude Desktop, PyPI, and MCP registry usage. The new HTTP entrypoint is additive and is intended for hosted Smithery deployment using Streamable HTTP at /mcp.

Added

• Added ausecon-mcp-http, a Streamable HTTP entrypoint for hosted MCP deployments.
• Added smithery.yaml for Smithery custom-container configuration.
• Added Dockerfile.smithery, using a multi-stage build and non-root runtime user.
• Added HTTP-only CORS middleware exposing mcp-session-id and mcp-protocol-version with credentials disabled.
• Added tests covering the HTTP entrypoint, Smithery metadata, Docker packaging, and HTTP safety validation.

Changed

• Raised the FastMCP dependency floor to an HTTP-capable version.
• Added Starlette as a direct dependency for CORS middleware.
• Updated README and documentation to describe Smithery as an additional hosted transport.
• Extended CI hygiene checks to cover Smithery packaging files.

Security

• Hardened ABS/RBA source-native identifiers and search inputs before HTTP exposure.
• Rejected schemes, slashes, query markers, fragments, control characters, and overlong source identifiers.
• Kept Smithery deployment unauthenticated only because the exposed tools are read-only and use public ABS/RBA data.
• Preserved stdio as the preferred local transport to avoid unnecessary local HTTP exposure.

Compatibility

• No breaking changes to the existing stdio CLI.
• Existing tool names and response shapes are preserved.
• ausecon-mcp-server remains the default console script.

---

This discussion was created from the release v1.1.0 - Smithery HTTP container support.