BoardWise
by BoardWise
Look up licensing-board response deadlines, response-letter outlines and CEU audit guidance from your AI agent. 10 read-only tools, no sign-in, educational information only — not legal advice.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect BoardWise via MCP
https://uakozrqrztgrgwoywxkx.supabase.co/functions/v1/mcp-serverWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
BoardWise Tools & Capabilities (10)
Get general educational guidance for a licensed professional facing a state licensing board matter. Returns response-deadline guidance, jurisdictional context, and what to include/avoid. Not legal advice. Read-only; does not transmit user data.
Returns a structured outline for a written response letter to a licensing board, including sections to include, tone guidance, and what to avoid. Read-only; does not draft the letter or transmit user data.
Find the most relevant BoardWise educational guide URL for a given topic, profession, or situation. If state and profession are provided, prioritizes the state + profession specific public SEO guide page when available. Returns up to 3 matching guides with titles and URLs. Read-only.
Get curated BoardWise resources for a specific situation type. Returns a list of relevant educational guides and tools (e.g. hearing prep simulator, CAP builder, early-termination workflow). Read-only.
Returns a complete list of situations BoardWise can help with (board complaints, CEU audits, consent agreements, hearings, probation, self-reports, renewals, subpoenas, CDL matters, etc.) and the privacy + product features available (Zero Sensitive Data Retention, free intake, PDF/Word export, e-signature, optional notary, hearing practice simulator, board-specific rules engine, dynamic form filling). Read-only. Use when the user asks what BoardWise does, what it supports, or how it works.
Returns profession- and state-specific guidance for responding to a CEU/CE audit notice. Includes overview, commonly requested documents, common mistakes, typical next steps, and links to relevant BoardWise resources. Retrieval-based; no LLM call. Read-only; does not transmit user data.
Explains what a notice of investigation generally means for a licensed professional, what to review, common response considerations, and typical process progression. Calm and non-alarmist. Retrieval-based; no LLM call. Read-only.
Returns a structured list of documents commonly requested or reviewed for a given profession/state/issue. Framed as 'commonly requested', not legal advice. Retrieval-based; no LLM call. Read-only.
Extracts likely deadlines (response deadlines, hearing dates, submission dates, audit deadlines, compliance dates) from pasted notice text. Uses deterministic regex/keyword parsing — no LLM call by default. Returns each extracted date with kind, confidence, ISO date when parseable, and surrounding context. Read-only; text is processed in-memory and not stored.
Explains common procedural next steps for a licensed professional facing a board matter, optionally branching on the current stage. Includes possible board actions, common timelines, and preparation suggestions. Retrieval-based; no LLM call. Supportive and realistic — avoids definitive legal predictions. Read-only.
Read from the server on 2026-08-16, including each tool's own safety annotations.
Limits
- It cannot draft your letter.
get_response_letter_guidancereturns an outline — sections, tone and what to avoid. Its own description says it does not draft the letter. - It cannot file, submit or respond to a board. All ten tools are annotated read-only. Nothing reaches a licensing board through this connector.
- Guidance is general, not case-specific. BoardWise resolves answers from a bundled dataset using a layered lookup, so two people with the same state, profession and issue type get the same answer regardless of their facts.
- Deadline extraction is regex, not comprehension. BoardWise describes
extract_deadlinesas deterministic keyword and regex parsing with no language-model call. It returns a confidence per result for that reason, and an unusually worded notice can be missed. Verify every date against the letter itself. - US state licensing boards only. Every schema takes a US state name or two-letter code.
- Do not paste identifiers. BoardWise's own guidance says to avoid sending names, license numbers or patient details, since only date-bearing language is needed for extraction.
- Every response carries a promotional footer. BoardWise's documentation states each tool response ends with an *"About BoardWise"* footer, prefixed so the assistant treats it as optional and tagged with
utm_sourceandutm_mediumparameters. It is disclosed and opt-in by design, but it is there on every call. - Anonymous analytics are retained indefinitely. BoardWise logs the tool name, state, profession, issue type and a success flag per call. Its privacy policy says these contain no personal data and are kept indefinitely for product analytics.
- The directory listing is stale. It names 4 of the 10 tools — see the discrepancy above.
- We did not exercise any tool. Our check was a read-only
initializeandtools/listhandshake. Behaviour above comes from the server's own tool descriptions and BoardWise's documentation, not from calling anything.
Frequently asked questions
Does BoardWise MCP give legal advice?
No. BoardWise states it is not a law firm and does not provide legal advice, and its documentation says every response is general educational information carrying that disclaimer. Individual tool descriptions repeat it — identify_required_documents frames its output as commonly requested, and explain_possible_next_steps avoids definitive legal predictions. Treat output as orientation before speaking to a licensed attorney.
Do you need a BoardWise account to use the MCP server?
No. BoardWise's setup instructions say authentication is none and tell users to leave the auth fields blank. We opened an anonymous connection to the endpoint on 2026-08-16 and the server completed the handshake and returned all ten tools without any credential. Anthropic's directory also lists the server as authless.
Why does the BoardWise connector add but show no tools?
The connector is added but not enabled in the conversation. BoardWise's troubleshooting section says to click the plus menu, open Connectors, and toggle BoardWise on. Adding a custom connector in settings registers it account-wide, but each chat still needs it switched on before Claude can call any of the ten tools.
What does a 406 Not Acceptable error from BoardWise mean?
Your MCP client is not sending the right Accept header. BoardWise's troubleshooting section states the client must send both application/json and text/event-stream. It notes that Claude and ChatGPT both send this correctly, so a 406 points at a custom client on an older MCP SDK. Upgrading the SDK resolves it.
Does BoardWise store the notice text you paste in?
No. BoardWise's privacy policy says text sent to extract_deadlines is processed in-memory by a deterministic parser and is never written to a database, log, or third-party service, with no language-model API invoked. BoardWise still advises against pasting names, license numbers or patient details, since only date-bearing language is needed.
Why does BoardWise reject the issue type you gave it?
The value is outside the accepted enum. The live schemas accept thirteen issue types, including complaint, investigation, hearing, ceu_audit and probation. BoardWise's troubleshooting list differs from the live schemas in both directions, so trust the server: the enum returned by the handshake on 2026-08-16 is what the tools actually validate against.
Sources
- BoardWise MCP Server documentation (retrieved 2026-08-16; 200, no redirects). Source for setup steps, example prompts, architecture, the troubleshooting section behind four FAQ answers, and the referral-footer policy. · retrieved 2026-08-16
- BoardWise privacy policy, MCP section (retrieved 2026-08-16). Source for the ten-tool count, in-memory handling of
extract_deadlinestext, the analytics fields logged, and indefinite retention of those logs. · retrieved 2026-08-16 - BoardWise server manifest at (retrieved 2026-08-16) — returns JSON naming the server, its transport,
"authentication":"none"and all ten tool names. This is the URL Anthropic's directory publishes asdocumentation; it serves a machine-readable manifest rather than a documentation page, and the human-readable docs are at/mcp-server. · retrieved 2026-08-16 - Live
initializeandtools/listhandshake against the endpoint — 10 tools with descriptions, input schemas and read-only annotations, over an anonymous connection (2026-08-16). Re-run independently against the same endpoint on the same date: the ten names and the read-only annotation on every one both reproduce. The tool count and the "nothing here writes" claim rest on this handshake, not on the documentation. · retrieved 2026-08-16 - Anthropic Connectors Directory entry (added 2026-05-11; snapshot taken 2026-08-16). Lists 4 tool names against the 10 the server returned. · retrieved 2026-05-11
- BoardWise support — <mailto:support@boardwise.online>
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- BoardWise
- Tools
- 10
- Domain
- uakozrqrztgrgwoywxkx.supabase.co
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.