Other · Remote MCP server
Basinwise
Determines which NPDES stormwater permit governs a US site and its requirements, cited to source.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.maxbeech/basinwise- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-07-22
- Updated
- 2026-07-22
- Publisher
- maxbeech (GitHub) · 3 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/maxbeech) · how
- Website
- basinwise.vercel.app/developers/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://basinwise.vercel.app/api/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 404)
- Handshake
- HTTP 404
- Checked on
- 2026-10-05
How to connect Basinwise
Basinwise is a remote MCP server: there is nothing to install. Its endpoint is https://basinwise.vercel.app/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from maxbeech (GitHub)
| Server | Runs |
|---|---|
| DenialPathDeterministic CMS NCCI/MUE claim scrubbing and CARC/RARC denial explanations, cited to source. | Remote · HTTPLive check: ✗ no handshake |
| LodgeDeckSTR legality, permits and lodging tax by city, each field cited to its source jurisdiction. | Remote · HTTPLive check: ✗ no handshake |
More other servers
| Server | Runs |
|---|---|
| BasethreadOne shared context your team's AI tools read & write over MCP. No re-explaining. Free. | Remote · HTTPLive check: sign-in required |
| Bash Command MCPSophisticated bash command MCP server that runs and manages shell execution. | Local · stdio |
| Bashdog MCPSubmit & browse funny AI quotes on bash.dog - bash.org for the AI age. Agents self-register. | Local · stdio |
| BasinYour AI assistants coordinate with other people's in one shared library across tools and companies. | Remote · HTTPLive check: sign-in required |
| BassethoundCompany intelligence for AI agents: a five-layer domain dossier in one sniff_domain call. | Remote · HTTPLive check: sign-in required |
| Batchwatch MCPAsk batchwatch whether to batch a job and get the real measured queue evidence, not a guess. | Local · stdio |
| BatonHand off AI work with a signed Verification Receipt - an independent verifier proves it runs. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| BautaGive anything your AI makes a real, private-by-default link. Say "share this with Bauta.". | Remote · HTTPLive check: sign-in required |