
Basinwise
io.github.maxbeechPublished by GitHub account maxbeechv1.0.0Updated Oct 24, 2026
Determines which NPDES stormwater permit governs a US site and its requirements, cited to source.
Overview
Looks up which US NPDES stormwater permit applies to a site and what that permit requires, with citations.
- What you can do
- Basinwise is a remote MCP server that helps an assistant identify the NPDES stormwater permit governing a given US site and summarize the requirements that permit imposes. Its answers are cited back to source material, so the assistant can point to the underlying permit text rather than assert requirements on its own. The manifest lists no tools, so the exact tool names and inputs are not documented here.
- When to use it
- Useful when you need to check stormwater permitting obligations for a US construction or industrial site, or want an assistant to explain which permit applies and what it demands. It is aimed at permit screening and requirement lookup rather than general environmental research.
- Requirements
- A remote streamable HTTP endpoint at the provider's hosted address; no local package or runtime is needed. The manifest declares no authentication, environment variables, or headers, so no credentials appear to be required.
Installation
In SourceWeft
- Open Basinwise in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.maxbeech%2Fbasinwise/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"basinwise": {
"type": "http",
"url": "https://basinwise.vercel.app/api/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.