ai.bizmoon/regulatory
REMOTE · BIZMOON.AI · SCANNED SEP 22
Live US federal and state regulatory changes and grant programs, every result cited.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 792 tokens (~158/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the ai.bizmoon/regulatory MCP server?
ai.bizmoon/regulatory is a hosted endpoint at https://bizmoon.ai/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · bizmoon.ai
claude mcp add --transport http ai-bizmoon-regulatory 'https://bizmoon.ai/api/mcp'
{
"mcpServers": {
"ai-bizmoon-regulatory": {
"url": "https://bizmoon.ai/api/mcp"
}
}
} {
"servers": {
"ai-bizmoon-regulatory": {
"type": "http",
"url": "https://bizmoon.ai/api/mcp"
}
}
} [mcp_servers.ai-bizmoon-regulatory] url = "https://bizmoon.ai/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-bizmoon-regulatory": {
"type": "remote",
"url": "https://bizmoon.ai/api/mcp",
"enabled": true
}
}
} openclaw mcp add ai-bizmoon-regulatory --url 'https://bizmoon.ai/api/mcp' --transport streamable-http
mcp_servers:
ai-bizmoon-regulatory:
url: "https://bizmoon.ai/api/mcp" {
"McpServers": {
"ai-bizmoon-regulatory": {
"Transport": "http",
"Url": "https://bizmoon.ai/api/mcp"
}
}
} assistant mcp add ai-bizmoon-regulatory -t streamable-http -u 'https://bizmoon.ai/api/mcp'
{
"mcpServers": {
"ai-bizmoon-regulatory": {
"type": "http",
"url": "https://bizmoon.ai/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
- Tool “changes_since” rewrote its description, which is the text the model reads security
- Tool “search_funding_programs” rewrote its description, which is the text the model reads security
- Tool “search_regulatory_changes” rewrote its description, which is the text the model reads security
- Schema quality: 179 → 158 ▲ functional
- “search_funding_programs” reworded the description of “limit” cosmetic
- “search_regulatory_changes” reworded the description of “limit” cosmetic
- 19 Sept 26 +1
- “changes_since” reworded the description of “jurisdiction” cosmetic
- “search_funding_programs” reworded the description of “jurisdiction” cosmetic
- “search_regulatory_changes” reworded the description of “jurisdiction” cosmetic
3 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://bizmoon.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bizmoon.ai | CN=WE1,O=Google Trust Services,C=US | 1 Aug 2026 | 30 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 56c88742c378372513c535db84ef1b93 |
| SANs: bizmoon.ai, *.bizmoon.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bizmoon.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| bizmoon.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bizmoon.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://bizmoon.ai/api/mcp | HTTPS enforced | 301 | https://bizmoon.ai/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
changes_since Regulatory changes since a date ~175
Everything published since a given date, optionally for one jurisdiction, newest first. Designed for scheduled or recurring agents: store the newest publishedDate you have seen and pass it back as `since` on the next run. Covers the last 90 days, up to 25 results per call.
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction | string | – | Jurisdiction: "US_FED" for federal, or a US state as a two-letter code like "CA", "NY", "TX" (full names and "US_STATE_CA" also work). Omit for all jurisdictions. |
| limit | integer | – | Max results. Default 20. |
| offset | integer | – | Pagination offset. Default 0. Combine with total in the response to page. |
| since | string | yes | ISO date or timestamp. Returns documents published on or after this moment. |
No output schema declared.
No examples provided.
get_regulatory_change Get regulatory change ~63
Fetch one regulatory document by id: title, jurisdiction, agencies, category, published and effective dates, AI summary, full description, and the canonical source URL to cite.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The document id returned by search_regulatory_changes or changes_since. |
No output schema declared.
No examples provided.
list_jurisdictions List covered jurisdictions ~45
List every jurisdiction and official register Bizmoon monitors, with the most recent publication date, and when the source was last checked. Call this first to learn coverage and freshness.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_funding_programs Search grants and funding programs ~228
Search federal and state grant and incentive programs (grants.gov plus state economic development agencies) by keyword, jurisdiction, agency, and date. Each result includes a summary and the official program URL. Covers the last 90 days, up to 25 results per call.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Case-insensitive substring match on the issuing agency name. |
| from | string | – | ISO date (YYYY-MM-DD). Only documents published on or after this date. |
| jurisdiction | string | – | Jurisdiction: "US_FED" for federal, or a US state as a two-letter code like "CA", "NY", "TX" (full names and "US_STATE_CA" also work). Omit for all jurisdictions. |
| keyword | string | – | Case-insensitive substring matched against title, AI summary, and description. |
| limit | integer | – | Max results per call. Default 20. |
| offset | integer | – | Pagination offset. Default 0. |
| to | string | – | ISO date (YYYY-MM-DD). Only documents published on or before this date. |
No output schema declared.
No examples provided.
search_regulatory_changes Search regulatory changes ~281
Search US federal and state regulatory documents ingested from official registers, with AI summaries, agencies, effective dates, and source URLs. Funding opportunities are excluded unless you pass category "funding"; use search_funding_programs for grants and incentive programs. Results are sorted newest first and every result includes a citation URL. Covers the last 90 days, up to 25 results per call.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Case-insensitive substring match on the issuing agency name. |
| category | string | – | Document category: "regulation" or "funding". Omit to include all documents, including unclassified ones. |
| from | string | – | ISO date (YYYY-MM-DD). Only documents published on or after this date. |
| jurisdiction | string | – | Jurisdiction: "US_FED" for federal, or a US state as a two-letter code like "CA", "NY", "TX" (full names and "US_STATE_CA" also work). Omit for all jurisdictions. |
| keyword | string | – | Case-insensitive substring matched against title, AI summary, and description. |
| limit | integer | – | Max results per call. Default 20. |
| offset | integer | – | Pagination offset. Default 0. |
| to | string | – | ISO date (YYYY-MM-DD). Only documents published on or before this date. |
No output schema declared.
No examples provided.
What is the ai.bizmoon/regulatory MCP server?
ai.bizmoon/regulatory is an MCP server listed in the public MCP registry as ai.bizmoon/regulatory. Live US federal and state regulatory changes and grant programs, every result cited. This page covers its hosted endpoint (https://bizmoon.ai/api/mcp).
Is the ai.bizmoon/regulatory MCP server safe to use?
ai.bizmoon/regulatory scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ai.bizmoon/regulatory MCP server expose?
ai.bizmoon/regulatory exposes 5 tools: search_regulatory_changes, get_regulatory_change, list_jurisdictions, changes_since, search_funding_programs. Their descriptions and schemas cost roughly 792 tokens of context every time the server is loaded.
Does the ai.bizmoon/regulatory MCP server require authentication?
No. We connected to ai.bizmoon/regulatory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ai.bizmoon/regulatory MCP server still maintained?
ai.bizmoon/regulatory is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.