nepa-mcp 0.1.0__tar.gz

nepa_mcp-0.1.0/.gitignore

@@ -0,0 +1,53 @@
+# Python
+__pycache__/
+*.py[cod]
+*.so
+*.egg-info/
+build/
+dist/
+.venv/
+venv/
+.ruff_cache/
+.pytest_cache/
+.playwright-cli/
+.playwright-mcp/
+.mypy_cache/
+.coverage
+coverage.xml
+htmlcov/
+*.log
+
+# Local environment and credentials
+.env
+.env.*
+!.env.example
+credentials.env
+config.toml
+handoffs/
+
+# Generated MCP client backups and interrupted writes
+*.nepa-mcp.bak
+.mcp.json.tmp
+.vscode/mcp.json.tmp
+
+# Legacy deployment-generated files
+*/.bedrock_agentcore.yaml
+*/.bedrock_agentcore/
+
+# Local outputs
+output/
+tmp/
+
+# Pre-release review material that must stay out of the public repository
+docs/*.docx
+EIDR/
+
+# OS and editor files
+.DS_Store
+.claude/
+.vscode/
+!.vscode/
+.vscode/*
+!.vscode/mcp.json
+.idea/
+*.swp

nepa_mcp-0.1.0/CITATION.cff

@@ -0,0 +1,26 @@
+cff-version: 1.2.0
+message: "If you use this software, please cite it using the metadata in this file."
+title: "PermitAI NEPA MCP Toolkit: Federal Environmental Data, Regulatory Research, and Geospatial Screening"
+type: software
+authors:
+  - family-names: Chaturvedi
+    given-names: Sarthak
+    website: "https://sarthakchat.github.io/"
+  - family-names: Chintalapati
+    given-names: Renuka
+  - family-names: Nally
+    given-names: Daniel
+    website: "https://www.pnnl.gov/people/dan-nally"
+  - family-names: Parker
+    given-names: Mike
+    website: "https://www.pnnl.gov/people/mike-parker"
+  - family-names: Munikoti
+    given-names: Sai
+    website: "https://www.pnnl.gov/people/sai-munikoti"
+  - family-names: Horawalavithana
+    given-names: Sameera
+    website: "https://www.pnnl.gov/people/sameera-horawalavithana"
+version: 0.1.0
+date-released: 2026-08-18
+repository-code: "https://github.com/pnnl/nepa-mcp"
+license: BSD-3-Clause

nepa_mcp-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,171 @@
+# Contributor Covenant 3.0 Code of Conduct
+
+## Our Pledge
+
+We pledge to make our community welcoming, safe, and equitable for all.
+
+We are committed to fostering an environment that respects and promotes the
+dignity, rights, and contributions of all individuals, regardless of
+characteristics including race, ethnicity, caste, color, age, physical
+characteristics, neurodiversity, disability, sex or gender, gender identity or
+expression, sexual orientation, language, philosophy or religion, national or
+social origin, socio-economic position, level of education, or other status.
+The same privileges of participation are extended to everyone who participates
+in good faith and in accordance with this Covenant.
+
+## Encouraged Behaviors
+
+While acknowledging differences in social norms, we all strive to meet our
+community's expectations for positive behavior. We also understand that our
+words and actions may be interpreted differently than we intend based on
+culture, background, or native language.
+
+With these considerations in mind, we agree to behave mindfully toward each
+other and act in ways that center our shared values, including:
+
+1. Respecting the **purpose of our community**, our activities, and our ways of
+   gathering.
+2. Engaging **kindly and honestly** with others.
+3. Respecting **different viewpoints** and experiences.
+4. **Taking responsibility** for our actions and contributions.
+5. Gracefully giving and accepting **constructive feedback**.
+6. Committing to **repairing harm** when it occurs.
+7. Behaving in other ways that promote and sustain the **well-being of our
+   community**.
+
+## Restricted Behaviors
+
+We agree to restrict the following behaviors in our community. Instances,
+threats, and promotion of these behaviors are violations of this Code of
+Conduct.
+
+1. **Harassment.** Violating explicitly expressed boundaries or engaging in
+   unnecessary personal attention after any clear request to stop.
+2. **Character attacks.** Making insulting, demeaning, or pejorative comments
+   directed at a community member or group of people.
+3. **Stereotyping or discrimination.** Characterizing anyone’s personality or
+   behavior on the basis of immutable identities or traits.
+4. **Sexualization.** Behaving in a way that would generally be considered
+   inappropriately intimate in the context or purpose of the community.
+5. **Violating confidentiality**. Sharing or acting on someone's personal or
+   private information without their permission.
+6. **Endangerment.** Causing, encouraging, or threatening violence or other
+   harm toward any person or group.
+7. Behaving in other ways that **threaten the well-being** of our community.
+
+### Other Restrictions
+
+1. **Misleading identity.** Impersonating someone else for any reason, or
+   pretending to be someone else to evade enforcement actions.
+2. **Failing to credit sources.** Not properly crediting the sources of content
+   you contribute.
+3. **Promotional materials**. Sharing marketing or other commercial content in
+   a way that is outside the norms of the community.
+4. **Irresponsible communication.** Failing to responsibly present content
+   which includes, links or describes any other restricted behaviors.
+
+## Reporting an Issue
+
+Tensions can occur between community members even when they are trying their
+best to collaborate. Not every conflict represents a code of conduct violation,
+and this Code of Conduct reinforces encouraged behaviors and norms that can
+help avoid conflicts and minimize harm.
+
+When an incident does occur, it is important to report it promptly. To report a
+possible violation, email
+[policyai@pnnl.gov](mailto:policyai@pnnl.gov?subject=NEPA%20MCP%20Code%20of%20Conduct%20Report)
+with the subject `NEPA MCP Code of Conduct Report`. Do not submit Code of
+Conduct reports through public issues.
+
+For this project, Community Moderators are Sarthak Chaturvedi, as primary
+project maintainer, and designated recipients of the PermitAI mailbox. A report
+concerning the primary maintainer will be handled by designated PermitAI
+mailbox recipients without involving the subject of the report.
+
+Community Moderators take reports of violations seriously and will make every
+effort to respond in a timely manner. They will investigate all reports of code
+of conduct violations, reviewing messages, logs, and recordings, or
+interviewing witnesses and other participants. Community Moderators will keep
+investigation and enforcement actions as transparent as possible while
+prioritizing safety and confidentiality. In order to honor these values,
+enforcement actions are carried out in private with the involved parties, but
+communicating to the whole community may be part of a mutually agreed upon
+resolution.
+
+## Addressing and Repairing Harm
+
+If an investigation by the Community Moderators finds that this Code of Conduct
+has been violated, the following enforcement ladder may be used to determine
+how best to repair harm, based on the incident's impact on the individuals
+involved and the community as a whole. Depending on the severity of a
+violation, lower rungs on the ladder may be skipped.
+
+1. Warning
+   1. Event: A violation involving a single incident or series of incidents.
+   2. Consequence: A private, written warning from the Community Moderators.
+   3. Repair: Examples of repair include a private written apology,
+      acknowledgement of responsibility, and seeking clarification on
+      expectations.
+2. Temporarily Limited Activities
+   1. Event: A repeated incidence of a violation that previously resulted in a
+      warning, or the first incidence of a more serious violation.
+   2. Consequence: A private, written warning with a time-limited cooldown
+      period designed to underscore the seriousness of the situation and give
+      the community members involved time to process the incident. The cooldown
+      period may be limited to particular communication channels or
+      interactions with particular community members.
+   3. Repair: Examples of repair may include making an apology, using the
+      cooldown period to reflect on actions and impact, and being thoughtful
+      about re-entering community spaces after the period is over.
+3. Temporary Suspension
+   1. Event: A pattern of repeated violation which the Community Moderators
+      have tried to address with warnings, or a single serious violation.
+   2. Consequence: A private written warning with conditions for return from
+      suspension. In general, temporary suspensions give the person being
+      suspended time to reflect upon their behavior and possible corrective
+      actions.
+   3. Repair: Examples of repair include respecting the spirit of the
+      suspension, meeting the specified conditions for return, and being
+      thoughtful about how to reintegrate with the community when the
+      suspension is lifted.
+4. Permanent Ban
+   1. Event: A pattern of repeated code of conduct violations that other steps
+      on the ladder have failed to resolve, or a violation so serious that the
+      Community Moderators determine there is no way to keep the community safe
+      with this person as a member.
+   2. Consequence: Access to all community spaces, tools, and communication
+      channels is removed. In general, permanent bans should be rarely used,
+      should have strong reasoning behind them, and should only be resorted to
+      if working through other remedies has failed to change the behavior.
+   3. Repair: There is no possible repair in cases of this severity.
+
+This enforcement ladder is intended as a guideline. It does not limit the
+ability of Community Moderators to use their discretion and judgment, in
+keeping with the best interests of our community.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public or other
+spaces. Examples of representing our community include using an official email
+address, posting via an official social media account, or acting as an
+appointed representative at an online or offline event.
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 3.0,
+permanently available at
+[https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/).
+
+Contributor Covenant is stewarded by the Organization for Ethical Source and
+licensed under CC BY-SA 4.0. To view a copy of this license, visit
+[https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/).
+
+For answers to common questions about Contributor Covenant, see the FAQ at
+[https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq).
+Translations are provided at
+[https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations).
+Additional enforcement and community guideline resources can be found at
+[https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources).
+The enforcement ladder was inspired by the work of
+[Mozilla’s code of conduct team](https://github.com/mozilla/inclusion).

nepa_mcp-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,137 @@
+# Contributing to NEPA MCP
+
+Thank you for contributing to NEPA MCP. This project provides research and
+screening tools for environmental and regulatory workflows. Contributions
+should preserve the distinction between screening information and formal
+agency, legal, consultation, jurisdictional, or permitting determinations.
+
+Please review the [Code of Conduct](CODE_OF_CONDUCT.md),
+[Security policy](SECURITY.md), [Support policy](SUPPORT.md), and
+[project roles](MAINTAINERS.md) before participating.
+
+## Development setup
+
+NEPA MCP requires Python 3.12 or newer. The development environment uses
+[`uv`](https://docs.astral.sh/uv/):
+
+```bash
+git clone https://github.com/pnnl/nepa-mcp.git
+cd nepa-mcp
+uv sync --all-groups
+```
+
+Do not commit credentials or private project data. Optional Census and EPA AQS
+credentials should be supplied through environment variables or the private
+per-user configuration described in the README. Repository `.env` files,
+generated credential files, and client-config backups are ignored by Git.
+
+## Repository structure
+
+Each domain server has its own top-level directory:
+
+```text
+server_name/
+├── requirements.txt
+├── server.py
+└── src/
+    ├── apis/
+    └── core/
+```
+
+The installable command, server registry, loader, client configuration, and
+aggregate test proxy live in `nepa_mcp/`. Shared HTTP, ArcGIS, spatial, and
+validation utilities live in `nepa_mcp_common/`.
+
+When adding or renaming a server or tool, update every affected distribution
+surface: the registry, package configuration, client examples, plugin
+configuration, documentation, and tests.
+
+## Generated files
+
+`docs/mcp-tool-catalog.md` is generated from the live MCP contracts. Do not
+edit it manually. Regenerate and verify it with:
+
+```bash
+uv run python scripts/generate_tool_catalog.py
+uv run python scripts/generate_tool_catalog.py --check
+```
+
+`uv.lock` is generated by `uv`. Commit lockfile changes when project or
+development dependencies change, and avoid unrelated dependency refreshes.
+
+## Tests and quality checks
+
+Run the following checks before opening a pull request:
+
+```bash
+uv run ruff format --check .
+uv run ruff check .
+uv run python -m compileall -q .
+uv run pytest -q
+uv run pip-audit --progress-spinner off
+```
+
+Add focused tests for behavioral changes. Tests should cover relevant MCP tool
+contracts, validation and failure behavior, and partial or empty upstream
+responses. Keep the default test suite reproducible without optional API
+credentials.
+
+Changes to external data integrations should preserve source URLs, retrieval
+status, truncation or partial-result warnings, and other provenance needed to
+review the result. Do not convert unavailable or incomplete source retrieval
+into an apparently authoritative no-feature result.
+
+## Pull requests
+
+Keep pull requests scoped and explain:
+
+- the user or analyst problem being addressed;
+- the affected servers, tools, and external sources;
+- important behavioral or schema changes;
+- tests and manual validation performed; and
+- known limitations or follow-up work.
+
+Update user-facing documentation when installation, configuration, tool
+contracts, data behavior, or package metadata changes. Avoid combining
+unrelated formatting, generated-file, and behavioral changes when they can be
+reviewed independently.
+
+Maintainers may request changes before merging. Submitting a contribution does
+not imply that it will be accepted or included in a release.
+
+## Developer Certificate of Origin
+
+Every commit must include a `Signed-off-by` line certifying compliance with the
+[Developer Certificate of Origin 1.1](https://developercertificate.org/).
+Sign off a commit with:
+
+```bash
+git commit -s -m "Describe the change"
+```
+
+The resulting commit message includes:
+
+```text
+Signed-off-by: Your Name <your.email@example.com>
+```
+
+The sign-off certifies that you have the right to submit the contribution under
+the project's open-source license. It is not a copyright assignment or a
+Contributor License Agreement. The name and email in the sign-off become part
+of the public Git history.
+
+If a commit is missing the sign-off, amend it before review:
+
+```bash
+git commit --amend --signoff --no-edit
+```
+
+## Reporting concerns
+
+Use public issues only for non-sensitive bugs and usage questions. Do not place
+credentials, controlled information, private project data, suspected
+vulnerability details, or Code of Conduct reports in a public issue.
+
+Code of Conduct reports should follow the private contact instructions in
+`CODE_OF_CONDUCT.md`. Suspected vulnerabilities should follow the private
+reporting instructions in `SECURITY.md`.

nepa_mcp-0.1.0/LICENSE

@@ -0,0 +1,28 @@
+BSD 3-Clause License
+
+Copyright Battelle Memorial Institute 2026
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this
+list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice,
+this list of conditions and the following disclaimer in the documentation
+and/or other materials provided with the distribution.
+
+3. Neither the name of the copyright holder nor the names of its contributors
+may be used to endorse or promote products derived from this software without
+specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

nepa_mcp-0.1.0/MAINTAINERS.md

@@ -0,0 +1,25 @@
+# Project Roles
+
+This file records current repository-governance roles. It does not determine
+legal inventorship, employment authority, or ownership.
+
+## Maintainer
+
+### Sarthak Chaturvedi
+
+Primary maintainer, responsible for technical direction, reviewing and merging
+changes, and coordinating package releases.
+
+## Contributor
+
+### Renuka Chintalapati
+
+Project contributor. Contributor status recognizes development contributions
+but does not by itself grant authority to merge changes or publish releases.
+
+## Updating roles
+
+Changes to maintainer or release authority should be recorded through a
+reviewed repository change. Security reports are received through the route in
+`SECURITY.md`; the primary maintainer coordinates technical triage with
+designated recipients of the PermitAI project mailbox.

nepa_mcp-0.1.0/NOTICE

@@ -0,0 +1,23 @@
+DISCLAIMER
+This material was prepared as an account of work sponsored by an agency of the
+United States Government.  Neither the United States Government nor the United
+States Department of Energy, nor Battelle, nor any of their employees, nor any
+jurisdiction or organization that has cooperated in the development of these
+materials, makes any warranty, express or implied, or assumes any legal
+liability or responsibility for the accuracy, completeness, or usefulness or
+any information, apparatus, product, software, or process disclosed, or
+represents that its use would not infringe privately owned rights.
+
+Reference herein to any specific commercial product, process, or service by
+trade name, trademark, manufacturer, or otherwise does not necessarily
+constitute or imply its endorsement, recommendation, or favoring by the United
+States Government or any agency thereof, or Battelle Memorial Institute. The
+views and opinions of authors expressed herein do not necessarily state or
+reflect those of the United States Government or any agency thereof.
+
+                PACIFIC NORTHWEST NATIONAL LABORATORY
+                             operated by
+                               BATTELLE
+                               for the
+                  UNITED STATES DEPARTMENT OF ENERGY
+                   under Contract DE-AC05-76RL01830