ai.bizmoon/regulatory
REMOTE · BIZMOON.AI
Live US federal and state regulatory changes and grant programs, every result cited.
Available components
Last scanned (19 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 11 Oct 2026.
Category Education and Research
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HTTPS
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 18 Oct 26 −18
The score moved with no change recorded against any check. We would rather say so than guess.
- 17 Oct 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Oct 26 −18
The score moved with no change recorded against any check. We would rather say so than guess.
- 15 Oct 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 14 Oct 26 −18
The score moved with no change recorded against any check. We would rather say so than guess.
- 12 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 5 Oct 26 +1
- Stability: 0.97 → pass security
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 18 Oct 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 | 30 Sept 2026 | 29 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 5e7ea33907d00aec13aed91c9cefdf09 |
| 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. | DS published | 3799 | 8 | Verified |
| bizmoon.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
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 | Unreachable | ||
| http (plaintext) | http://bizmoon.ai/api/mcp | HTTPS enforced |
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.
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'
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 0 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?
Its publisher declares no required credentials for ai.bizmoon/regulatory. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the ai.bizmoon/regulatory MCP server still maintained?
ai.bizmoon/regulatory has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 11 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the ai.bizmoon/regulatory MCP server?
VerifyMCP ran 4 checks on ai.bizmoon/regulatory, covering TLS certificate, HTTPS, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about ai.bizmoon/regulatory: Authorization, HSTS header, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.