guard-core-mcp 0.0.1__tar.gz

guard_core_mcp-0.0.1/.gitignore

@@ -0,0 +1,218 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml

guard_core_mcp-0.0.1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Renzo F
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

guard_core_mcp-0.0.1/PKG-INFO

@@ -0,0 +1,80 @@
+Metadata-Version: 2.4
+Name: guard-core-mcp
+Version: 0.0.1
+Summary: MCP server for the Guard ecosystem — config validation, docs search and live threat detection for fastapi-guard, guard-core and guard-agent.
+Project-URL: Homepage, https://github.com/rennf93/guard-core-mcp
+Author-email: Renzo Franceschini <rennf93@users.noreply.github.com>
+License-Expression: MIT
+License-File: LICENSE
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Security
+Requires-Python: <3.15,>=3.10
+Requires-Dist: mcp
+Provides-Extra: dev
+Requires-Dist: fastapi-guard; extra == 'dev'
+Requires-Dist: guard-agent; extra == 'dev'
+Requires-Dist: guard-core; extra == 'dev'
+Requires-Dist: mypy; extra == 'dev'
+Requires-Dist: pytest; extra == 'dev'
+Requires-Dist: pytest-asyncio; extra == 'dev'
+Requires-Dist: pytest-cov; extra == 'dev'
+Requires-Dist: ruff; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# Guard Core MCP
+
+An [MCP](https://modelcontextprotocol.io) server that lets AI coding agents answer questions
+about the Guard security ecosystem from the libraries themselves, instead of from memory.
+
+Covers [`fastapi-guard`](https://github.com/rennf93/fastapi-guard),
+[`guard-core`](https://github.com/rennf93/guard-core) and
+[`guard-agent`](https://github.com/rennf93/guard-agent).
+
+> **Status: 0.0.1, early scaffold.** Only the `versions` tool is implemented. The config,
+> documentation and detection tools described below are in progress.
+
+## Why
+
+Your agent can already read the docs. What it cannot do is tell you that the `redis_failopen`
+in your config is silently doing nothing because the real field is `redis_fail_open`, or that
+the flag you are reaching for did not exist until guard-core 3.5.0, or whether a given request
+would actually be blocked and by which pattern.
+
+This server answers those from the installed package: real pydantic validation, real field
+metadata, and the real detection engine.
+
+## Install
+
+Install it **into your project's environment**, not as an isolated tool:
+
+```bash
+uv add --dev guard-core-mcp
+claude mcp add guard-core -- uv run guard-core-mcp
+```
+
+`uvx guard-core-mcp` will start, but an isolated environment contains no `guard-core` or
+`fastapi-guard` for it to introspect, so it can only answer from bundled documentation. Running
+it inside your own environment is what makes the answers match the versions you actually ship.
+
+## Tools
+
+| Tool | Answers |
+|---|---|
+| `versions` | Which Guard libraries are installed here, and at what version |
+| `validate_config` | Is this config valid — including typo'd keys pydantic silently ignores |
+| `config_fields` | What is this setting, what does it default to, does a setting for X exist |
+| `search_docs` | Where do the docs cover this |
+| `get_doc` | The full text of one documentation page |
+| `check_payload` | Would this request be blocked, and by which pattern |
+
+## Licence
+
+MIT

guard_core_mcp-0.0.1/README.md

@@ -0,0 +1,49 @@
+# Guard Core MCP
+
+An [MCP](https://modelcontextprotocol.io) server that lets AI coding agents answer questions
+about the Guard security ecosystem from the libraries themselves, instead of from memory.
+
+Covers [`fastapi-guard`](https://github.com/rennf93/fastapi-guard),
+[`guard-core`](https://github.com/rennf93/guard-core) and
+[`guard-agent`](https://github.com/rennf93/guard-agent).
+
+> **Status: 0.0.1, early scaffold.** Only the `versions` tool is implemented. The config,
+> documentation and detection tools described below are in progress.
+
+## Why
+
+Your agent can already read the docs. What it cannot do is tell you that the `redis_failopen`
+in your config is silently doing nothing because the real field is `redis_fail_open`, or that
+the flag you are reaching for did not exist until guard-core 3.5.0, or whether a given request
+would actually be blocked and by which pattern.
+
+This server answers those from the installed package: real pydantic validation, real field
+metadata, and the real detection engine.
+
+## Install
+
+Install it **into your project's environment**, not as an isolated tool:
+
+```bash
+uv add --dev guard-core-mcp
+claude mcp add guard-core -- uv run guard-core-mcp
+```
+
+`uvx guard-core-mcp` will start, but an isolated environment contains no `guard-core` or
+`fastapi-guard` for it to introspect, so it can only answer from bundled documentation. Running
+it inside your own environment is what makes the answers match the versions you actually ship.
+
+## Tools
+
+| Tool | Answers |
+|---|---|
+| `versions` | Which Guard libraries are installed here, and at what version |
+| `validate_config` | Is this config valid — including typo'd keys pydantic silently ignores |
+| `config_fields` | What is this setting, what does it default to, does a setting for X exist |
+| `search_docs` | Where do the docs cover this |
+| `get_doc` | The full text of one documentation page |
+| `check_payload` | Would this request be blocked, and by which pattern |
+
+## Licence
+
+MIT

guard_core_mcp-0.0.1/guard_core_mcp/__init__.py

@@ -0,0 +1,3 @@
+__version__ = "0.0.1"
+
+__all__ = ["__version__"]

guard_core_mcp-0.0.1/guard_core_mcp/server.py

@@ -0,0 +1,37 @@
+import importlib.metadata
+from typing import Any
+
+from mcp.server.fastmcp import FastMCP
+
+from guard_core_mcp import __version__
+
+GUARD_DISTRIBUTIONS = ("guard-core", "fastapi-guard", "guard-agent")
+
+mcp = FastMCP("guard-core")
+
+
+def installed_guard_versions() -> dict[str, str | None]:
+    versions: dict[str, str | None] = {}
+    for distribution in GUARD_DISTRIBUTIONS:
+        try:
+            versions[distribution] = importlib.metadata.version(distribution)
+        except importlib.metadata.PackageNotFoundError:
+            versions[distribution] = None
+    return versions
+
+
+@mcp.tool()
+def versions() -> dict[str, Any]:
+    """Report which Guard libraries this server can introspect, and at what version.
+
+    A null version means that library is not installed in the interpreter running
+    this server, so any answer about it would be a guess rather than introspection.
+    """
+    return {
+        "guard_core_mcp": __version__,
+        "installed": installed_guard_versions(),
+    }
+
+
+def main() -> None:
+    mcp.run()

guard_core_mcp-0.0.1/pyproject.toml

@@ -0,0 +1,100 @@
+[project]
+name = "guard-core-mcp"
+version = "0.0.1"
+description = "MCP server for the Guard ecosystem — config validation, docs search and live threat detection for fastapi-guard, guard-core and guard-agent."
+authors = [
+    {name = "Renzo Franceschini", email = "rennf93@users.noreply.github.com"}
+]
+readme = "README.md"
+license = "MIT"
+license-files = ["LICENSE"]
+requires-python = ">=3.10,<3.15"
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Intended Audience :: Developers",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Programming Language :: Python :: 3.14",
+    "Topic :: Security",
+]
+dependencies = [
+    "mcp",
+]
+
+[project.scripts]
+guard-core-mcp = "guard_core_mcp.server:main"
+
+[project.urls]
+Homepage = "https://github.com/rennf93/guard-core-mcp"
+
+[project.optional-dependencies]
+dev = [
+    "fastapi-guard",
+    "guard-agent",
+    "guard-core",
+    "mypy",
+    "pytest",
+    "pytest-asyncio",
+    "pytest-cov",
+    "ruff",
+]
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["guard_core_mcp"]
+
+[tool.hatch.build.targets.sdist]
+exclude = [
+    ".env",
+    ".envrc",
+    ".venv/",
+    ".github/",
+    ".claude/",
+    "CLAUDE.md",
+    ".pre-commit-config.yaml",
+    "Makefile",
+    "tests/",
+]
+
+[tool.ruff]
+target-version = "py310"
+exclude = [".venv"]
+
+[tool.ruff.lint]
+select = [
+    "E",
+    "F",
+    "UP",
+    "B",
+    "I",
+]
+
+[tool.pytest.ini_options]
+asyncio_mode = "auto"
+testpaths = ["tests"]
+python_files = ["test_*.py"]
+asyncio_default_fixture_loop_scope = "function"
+addopts = "--cov=guard_core_mcp --cov-branch --cov-report=term-missing"
+
+[tool.mypy]
+python_version = "3.10"
+warn_return_any = true
+warn_unused_configs = true
+disallow_untyped_defs = true
+disallow_incomplete_defs = true
+check_untyped_defs = true
+disallow_untyped_decorators = true
+no_implicit_optional = true
+strict_optional = true
+warn_redundant_casts = true
+warn_unused_ignores = true
+warn_no_return = true
+warn_unreachable = true
+exclude = [".venv"]