jgrants-util-mcp-server 0.1.0__tar.gz

jgrants_util_mcp_server-0.1.0/.gitignore

@@ -0,0 +1,220 @@
+# 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
+*.lcov
+.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/*
+!.pixi/config.toml
+
+# 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/Zensical 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

jgrants_util_mcp_server-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 GotoAI Inc.
+
+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.

jgrants_util_mcp_server-0.1.0/PKG-INFO

@@ -0,0 +1,121 @@
+Metadata-Version: 2.5
+Name: jgrants-util-mcp-server
+Version: 0.1.0
+Summary: A skill-style MCP server for the Jグランツ (jGrants) public subsidy API
+License-Expression: MIT
+License-File: LICENSE
+Requires-Python: >=3.11
+Requires-Dist: httpx>=0.27
+Requires-Dist: mcp<3,>=2.3
+Requires-Dist: pypdf>=5
+Provides-Extra: dev
+Requires-Dist: pytest-asyncio>=0.24; extra == 'dev'
+Requires-Dist: pytest>=8; extra == 'dev'
+Requires-Dist: ruff>=0.6; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# jgrants-util-mcp-server
+
+An MCP server for the public API of [Jグランツ (jGrants)](https://www.jgrants-portal.go.jp/),
+Japan's government subsidy portal: search subsidies, read their details, and read the text
+of their application guidelines.
+
+Jグランツの公開APIを使って、補助金の検索・詳細の確認・公募要領の閲覧ができる MCP サーバーです。
+
+> **Unofficial.** This project is not affiliated with or endorsed by the Digital Agency
+> (デジタル庁), which operates Jグランツ. It is written from scratch against the
+> [published API specification](https://developers.digital.go.jp/documents/jgrants/api/);
+> it is not a fork of the Digital Agency's
+> [jgrants-mcp-server](https://github.com/digital-go-jp/jgrants-mcp-server).
+
+## Tools
+
+| Tool | What it does |
+|---|---|
+| `load_guideline` | The usage guideline for the whole tool set: search strategy, details, attachments, what Jグランツ covers, and the conditions of use. It takes no arguments and always returns the whole guideline. |
+| `search_subsidies` | Search by one keyword plus filters (area, industry, purpose, employee count); paged. |
+| `get_subsidy_detail` | One subsidy's overview, eligibility, rate, amounts, dates, portal URL and attachment list. |
+| `read_attachment` | The text of a PDF attachment, in pieces, with `next_offset` to continue; image-only pages are listed in `pages_without_text`. |
+
+The server follows a *skill-style* layout. Its MCP `instructions` are one sentence
+saying what the tools are for and to call `load_guideline` first. Everything that
+concerns the tool set as a whole — including the conditions of use — lives in the
+guideline, and each tool's description covers only that tool. Agents that load many MCP
+servers keep only a short entry per server in their prompt, and read the guideline when
+they need it.
+
+## Run
+
+Python 3.11 or later.
+
+```bash
+pip install -e .
+python -m jgrants_util_mcp_server                                  # stdio, the default
+jgrants-util-mcp-server --transport streamable-http --port 8000    # HTTP at /mcp
+```
+
+stdio is the default because a client that installed the package starts the process
+itself: no port, no host name, nothing to put behind a proxy. Serving it over HTTP is
+the deliberate case, so it is the one that has to say so.
+
+The package declares what to run in the `kari.mcp_servers` entry-point group, so a client
+that installs the wheel can fill its own command field in — the distribution is named
+`jgrants-util-mcp-server` while the module is `jgrants_util_mcp_server`, and guessing one
+from the other is exactly the mistake that group avoids.
+
+Behind a reverse proxy, accept the public host name as well; otherwise the server's DNS
+rebinding protection rejects requests whose `Host` is not localhost:
+
+```bash
+jgrants-util-mcp-server --transport streamable-http --host 127.0.0.1 --port 8000 \
+    --allowed-host demo.mcp.gotoai.com
+```
+
+`--host`, `--port` and `--allowed-host` apply only to HTTP; given without
+`--transport streamable-http`, the server refuses to start rather than ignore them.
+
+When bound to a non-loopback address (for example `--host 0.0.0.0` on a LAN), that
+protection is off; restrict access with a firewall or a proxy.
+
+### In Kari
+
+Two ways, depending on whether the server runs on the user's own machine or on a host.
+
+**As a Python package (the server runs on the user's machine).** Build a wheel with
+`python -m build --wheel`, then in Kari: MCPサーバー追加 → type **Python パッケージ（STDIO）**
+→ ローカル wheel ファイル → the `.whl` → インストール. The command field fills itself in from
+the entry-point group above. Kari installs it into its own bundled Python, so the user
+needs no Python of their own. Once it is on PyPI, the pypi.org option takes the name
+instead.
+
+**Over HTTP (the server runs on a host).** Add a custom extension of type **Streamable
+HTTP** with the URL `http://<host>:<port>/mcp`, and start the server with
+`--transport streamable-http`.
+
+Either way, give it an ASCII name such as `jgrants` — the name becomes part of every tool
+name the agent sees.
+
+## Conditions of use
+
+These are in the guideline the agent reads; they apply to anyone presenting the results:
+
+- Credit the source as 「出典：Jグランツ（jGrants）」.
+- Treat the information as a reference; confirm the latest details on the subsidy's
+  official page (`portal_url`) before applying.
+- Avoid excessive repeated access to the API.
+
+The Jグランツ API's own terms are published by the Digital Agency at
+<https://www.jgrants-portal.go.jp/open-api>; they apply to whoever runs this server.
+
+## Development
+
+```bash
+pip install -e ".[dev]"
+pytest                    # offline tests
+JGRANTS_LIVE=1 pytest     # also the live test against the real API
+ruff check src tests
+```
+
+## License
+
+MIT — see [LICENSE](LICENSE).

jgrants_util_mcp_server-0.1.0/README.md

@@ -0,0 +1,105 @@
+# jgrants-util-mcp-server
+
+An MCP server for the public API of [Jグランツ (jGrants)](https://www.jgrants-portal.go.jp/),
+Japan's government subsidy portal: search subsidies, read their details, and read the text
+of their application guidelines.
+
+Jグランツの公開APIを使って、補助金の検索・詳細の確認・公募要領の閲覧ができる MCP サーバーです。
+
+> **Unofficial.** This project is not affiliated with or endorsed by the Digital Agency
+> (デジタル庁), which operates Jグランツ. It is written from scratch against the
+> [published API specification](https://developers.digital.go.jp/documents/jgrants/api/);
+> it is not a fork of the Digital Agency's
+> [jgrants-mcp-server](https://github.com/digital-go-jp/jgrants-mcp-server).
+
+## Tools
+
+| Tool | What it does |
+|---|---|
+| `load_guideline` | The usage guideline for the whole tool set: search strategy, details, attachments, what Jグランツ covers, and the conditions of use. It takes no arguments and always returns the whole guideline. |
+| `search_subsidies` | Search by one keyword plus filters (area, industry, purpose, employee count); paged. |
+| `get_subsidy_detail` | One subsidy's overview, eligibility, rate, amounts, dates, portal URL and attachment list. |
+| `read_attachment` | The text of a PDF attachment, in pieces, with `next_offset` to continue; image-only pages are listed in `pages_without_text`. |
+
+The server follows a *skill-style* layout. Its MCP `instructions` are one sentence
+saying what the tools are for and to call `load_guideline` first. Everything that
+concerns the tool set as a whole — including the conditions of use — lives in the
+guideline, and each tool's description covers only that tool. Agents that load many MCP
+servers keep only a short entry per server in their prompt, and read the guideline when
+they need it.
+
+## Run
+
+Python 3.11 or later.
+
+```bash
+pip install -e .
+python -m jgrants_util_mcp_server                                  # stdio, the default
+jgrants-util-mcp-server --transport streamable-http --port 8000    # HTTP at /mcp
+```
+
+stdio is the default because a client that installed the package starts the process
+itself: no port, no host name, nothing to put behind a proxy. Serving it over HTTP is
+the deliberate case, so it is the one that has to say so.
+
+The package declares what to run in the `kari.mcp_servers` entry-point group, so a client
+that installs the wheel can fill its own command field in — the distribution is named
+`jgrants-util-mcp-server` while the module is `jgrants_util_mcp_server`, and guessing one
+from the other is exactly the mistake that group avoids.
+
+Behind a reverse proxy, accept the public host name as well; otherwise the server's DNS
+rebinding protection rejects requests whose `Host` is not localhost:
+
+```bash
+jgrants-util-mcp-server --transport streamable-http --host 127.0.0.1 --port 8000 \
+    --allowed-host demo.mcp.gotoai.com
+```
+
+`--host`, `--port` and `--allowed-host` apply only to HTTP; given without
+`--transport streamable-http`, the server refuses to start rather than ignore them.
+
+When bound to a non-loopback address (for example `--host 0.0.0.0` on a LAN), that
+protection is off; restrict access with a firewall or a proxy.
+
+### In Kari
+
+Two ways, depending on whether the server runs on the user's own machine or on a host.
+
+**As a Python package (the server runs on the user's machine).** Build a wheel with
+`python -m build --wheel`, then in Kari: MCPサーバー追加 → type **Python パッケージ（STDIO）**
+→ ローカル wheel ファイル → the `.whl` → インストール. The command field fills itself in from
+the entry-point group above. Kari installs it into its own bundled Python, so the user
+needs no Python of their own. Once it is on PyPI, the pypi.org option takes the name
+instead.
+
+**Over HTTP (the server runs on a host).** Add a custom extension of type **Streamable
+HTTP** with the URL `http://<host>:<port>/mcp`, and start the server with
+`--transport streamable-http`.
+
+Either way, give it an ASCII name such as `jgrants` — the name becomes part of every tool
+name the agent sees.
+
+## Conditions of use
+
+These are in the guideline the agent reads; they apply to anyone presenting the results:
+
+- Credit the source as 「出典：Jグランツ（jGrants）」.
+- Treat the information as a reference; confirm the latest details on the subsidy's
+  official page (`portal_url`) before applying.
+- Avoid excessive repeated access to the API.
+
+The Jグランツ API's own terms are published by the Digital Agency at
+<https://www.jgrants-portal.go.jp/open-api>; they apply to whoever runs this server.
+
+## Development
+
+```bash
+pip install -e ".[dev]"
+pytest                    # offline tests
+JGRANTS_LIVE=1 pytest     # also the live test against the real API
+ruff check src tests
+```
+
+## License
+
+MIT — see [LICENSE](LICENSE).

jgrants_util_mcp_server-0.1.0/pyproject.toml

@@ -0,0 +1,46 @@
+[project]
+name = "jgrants-util-mcp-server"
+version = "0.1.0"
+description = "A skill-style MCP server for the Jグランツ (jGrants) public subsidy API"
+readme = "README.md"
+license = "MIT"
+license-files = ["LICENSE"]
+requires-python = ">=3.11"
+dependencies = [
+    "mcp>=2.3,<3",
+    "httpx>=0.27",
+    "pypdf>=5",
+]
+
+[project.optional-dependencies]
+dev = [
+    "pytest>=8",
+    "pytest-asyncio>=0.24",
+    "ruff>=0.6",
+]
+
+[project.scripts]
+jgrants-util-mcp-server = "jgrants_util_mcp_server.server:main"
+
+# What to run, declared so a client that installs this wheel does not have to be
+# told. Kari reads this group after installing a Python Package MCP server and
+# fills its command field from it; the module is runnable with `-m`, which is
+# what that field holds.
+[project.entry-points."kari.mcp_servers"]
+default = "jgrants_util_mcp_server:main"
+
+[build-system]
+requires = ["hatchling>=1.26"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/jgrants_util_mcp_server"]
+
+[tool.pytest.ini_options]
+asyncio_mode = "auto"
+testpaths = ["tests"]
+markers = ["live: calls the real Jグランツ API (set JGRANTS_LIVE=1 to run)"]
+
+[tool.ruff]
+line-length = 100
+target-version = "py311"

jgrants_util_mcp_server-0.1.0/src/jgrants_util_mcp_server/__init__.py

@@ -0,0 +1,5 @@
+"""A skill-style MCP server for the Jグランツ (jGrants) public subsidy API."""
+
+from .server import main
+
+__all__ = ["main"]

jgrants_util_mcp_server-0.1.0/src/jgrants_util_mcp_server/__main__.py

@@ -0,0 +1,7 @@
+"""`python -m jgrants_util_mcp_server`, which is how a client that installed the
+wheel starts the server: no console script on PATH, no absolute path to bake into
+a configuration file."""
+
+from .server import main
+
+main()