RegLayer Instant Decision Briefs
REMOTE · REGLAYER.AI · SCANNED SEP 24
Company-specific regulatory assessments for concrete business questions, as structured data or PDF.
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 Security63
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 534 tokens (~53/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 56% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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 RegLayer Instant Decision Briefs MCP server?
RegLayer Instant Decision Briefs is a hosted endpoint at https://reglayer.ai/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 · reglayer.ai
claude mcp add --transport http ai-reglayer-instant-decision-briefs 'https://reglayer.ai/mcp'
{
"mcpServers": {
"ai-reglayer-instant-decision-briefs": {
"url": "https://reglayer.ai/mcp"
}
}
} {
"servers": {
"ai-reglayer-instant-decision-briefs": {
"type": "http",
"url": "https://reglayer.ai/mcp"
}
}
} [mcp_servers.ai-reglayer-instant-decision-briefs] url = "https://reglayer.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-reglayer-instant-decision-briefs": {
"type": "remote",
"url": "https://reglayer.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-reglayer-instant-decision-briefs --url 'https://reglayer.ai/mcp' --transport streamable-http
mcp_servers:
ai-reglayer-instant-decision-briefs:
url: "https://reglayer.ai/mcp" {
"McpServers": {
"ai-reglayer-instant-decision-briefs": {
"Transport": "http",
"Url": "https://reglayer.ai/mcp"
}
}
} assistant mcp add ai-reglayer-instant-decision-briefs -t streamable-http -u 'https://reglayer.ai/mcp'
{
"mcpServers": {
"ai-reglayer-instant-decision-briefs": {
"type": "http",
"url": "https://reglayer.ai/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.
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 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 24 Sept 2026 · Probed https://reglayer.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=reglayer.ai | CN=WE1,O=Google Trust Services,C=US | 27 Aug 2026 | 25 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 6f30de32eec4fe501336328a8f6953df |
| SANs: reglayer.ai, signals.reglayer.ai, *.signals.reglayer.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 reglayer.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| reglayer.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://reglayer.ai/mcp | Verified | 200 | |
| http (plaintext) | http://reglayer.ai/mcp | Inconclusive | 405 |
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 →
get_check_pdf Get Check PDF URL ~36
Return the authenticated PDF endpoint after the Check is ready.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | yes | – |
| order_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | string | – | The version of the RegLayer agent delivery contract. |
| authentication | string | yes | The authorization header required to download the PDF. |
| brief_id | string | – | The Decision Brief identifier used in the finished artifact. |
| connection_required | boolean | – | Whether the original connection must remain open. |
| delivery_instructions | string | – | Instructions for retrieving the result without relying on email. |
| delivery_mode | string | – | The asynchronous delivery pattern used for this order. |
| error | string | – | A machine-readable error label when the request cannot be completed. |
| message | string | – | A human-readable status, authentication, or not-ready message. |
| notice | string | – | The notice that must travel with RegLayer research outputs. |
| ok | boolean | – | Whether the private status request succeeded. |
| order_id | string | – | The private RegLayer order identifier. |
| pdf_url | string | yes | The authenticated endpoint for downloading the finished PDF. |
| poll_after_seconds | – | – | Seconds to wait before the next status check, or null when no further polling is needed. |
| product | string | – | The purchased Instant Brief product code. |
| reference | string | – | The customer-facing brief reference. |
| status | string | – | The current order state, such as researching, ready, or failed. |
No examples provided.
get_check_result Get structured Check ~35
Retrieve the structured Check result after status reaches ready.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | yes | – |
| order_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | string | – | The version of the RegLayer agent delivery contract. |
| brief_id | string | – | The Decision Brief identifier used in the finished artifact. |
| connection_required | boolean | – | Whether the original connection must remain open. |
| delivery_instructions | string | – | Instructions for retrieving the result without relying on email. |
| delivery_mode | string | – | The asynchronous delivery pattern used for this order. |
| error | string | – | A machine-readable error label when the request cannot be completed. |
| message | string | – | A human-readable status, authentication, or not-ready message. |
| notice | string | – | The notice that must travel with RegLayer research outputs. |
| ok | boolean | – | Whether the private status request succeeded. |
| order_id | string | – | The private RegLayer order identifier. |
| poll_after_seconds | – | – | Seconds to wait before the next status check, or null when no further polling is needed. |
| product | string | – | The purchased Instant Brief product code. |
| published_at | string | – | The timestamp when the result became available. |
| reference | string | – | The customer-facing brief reference. |
| result | object | – | The complete structured Decision Brief when research is ready. |
| result_kind | string | – | The type of structured artifact returned. |
| result_version | – | – | The version of the stored structured result. |
| status | string | – | The current order state, such as researching, ready, or failed. |
No examples provided.
get_check_status Get Check status ~30
Read private Check status.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | yes | – |
| order_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | string | – | The version of the RegLayer agent delivery contract. |
| brief_id | string | – | The Decision Brief identifier used in the finished artifact. |
| connection_required | boolean | – | Whether the original connection must remain open. |
| delivery_instructions | string | – | Instructions for retrieving the result without relying on email. |
| delivery_mode | string | – | The asynchronous delivery pattern used for this order. |
| error | string | – | A machine-readable error label when the request cannot be completed. |
| message | string | – | A human-readable status, authentication, or not-ready message. |
| notice | string | – | The notice that must travel with RegLayer research outputs. |
| ok | boolean | – | Whether the private status request succeeded. |
| order_id | string | – | The private RegLayer order identifier. |
| poll_after_seconds | – | – | Seconds to wait before the next status check, or null when no further polling is needed. |
| product | string | – | The purchased Instant Brief product code. |
| reference | string | – | The customer-facing brief reference. |
| status | string | – | The current order state, such as researching, ready, or failed. |
No examples provided.
get_instant_brief_pdf Get Instant Brief PDF URL ~83
Return the authenticated PDF endpoint after status reaches ready. Use the same bearer token when downloading it.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | yes | The private RegLayer access token returned with the order. Send it only to RegLayer and never expose it to the end user. |
| order_id | string | yes | The order_id returned by the paid Instant Brief purchase request. |
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | string | – | The version of the RegLayer agent delivery contract. |
| authentication | string | yes | The authorization header required to download the PDF. |
| brief_id | string | – | The Decision Brief identifier used in the finished artifact. |
| connection_required | boolean | – | Whether the original connection must remain open. |
| delivery_instructions | string | – | Instructions for retrieving the result without relying on email. |
| delivery_mode | string | – | The asynchronous delivery pattern used for this order. |
| error | string | – | A machine-readable error label when the request cannot be completed. |
| message | string | – | A human-readable status, authentication, or not-ready message. |
| notice | string | – | The notice that must travel with RegLayer research outputs. |
| ok | boolean | – | Whether the private status request succeeded. |
| order_id | string | – | The private RegLayer order identifier. |
| pdf_url | string | yes | The authenticated endpoint for downloading the finished PDF. |
| poll_after_seconds | – | – | Seconds to wait before the next status check, or null when no further polling is needed. |
| product | string | – | The purchased Instant Brief product code. |
| reference | string | – | The customer-facing brief reference. |
| status | string | – | The current order state, such as researching, ready, or failed. |
No examples provided.
get_instant_brief_result Get structured Instant Brief ~87
Read the structured result after status reaches ready. If still researching, close the call and retry after 20 seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | yes | The private RegLayer access token returned with the order. Send it only to RegLayer and never expose it to the end user. |
| order_id | string | yes | The order_id returned by the paid Instant Brief purchase request. |
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | string | – | The version of the RegLayer agent delivery contract. |
| brief_id | string | – | The Decision Brief identifier used in the finished artifact. |
| connection_required | boolean | – | Whether the original connection must remain open. |
| delivery_instructions | string | – | Instructions for retrieving the result without relying on email. |
| delivery_mode | string | – | The asynchronous delivery pattern used for this order. |
| error | string | – | A machine-readable error label when the request cannot be completed. |
| message | string | – | A human-readable status, authentication, or not-ready message. |
| notice | string | – | The notice that must travel with RegLayer research outputs. |
| ok | boolean | – | Whether the private status request succeeded. |
| order_id | string | – | The private RegLayer order identifier. |
| poll_after_seconds | – | – | Seconds to wait before the next status check, or null when no further polling is needed. |
| product | string | – | The purchased Instant Brief product code. |
| published_at | string | – | The timestamp when the result became available. |
| reference | string | – | The customer-facing brief reference. |
| result | object | – | The complete structured Decision Brief when research is ready. |
| result_kind | string | – | The type of structured artifact returned. |
| result_version | – | – | The version of the stored structured result. |
| status | string | – | The current order state, such as researching, ready, or failed. |
No examples provided.
get_instant_brief_status Get Instant Brief status ~87
Read private order status. If status is researching, close the call and invoke this tool again after 20 seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | yes | The private RegLayer access token returned with the order. Send it only to RegLayer and never expose it to the end user. |
| order_id | string | yes | The order_id returned by the paid Instant Brief purchase request. |
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | string | – | The version of the RegLayer agent delivery contract. |
| brief_id | string | – | The Decision Brief identifier used in the finished artifact. |
| connection_required | boolean | – | Whether the original connection must remain open. |
| delivery_instructions | string | – | Instructions for retrieving the result without relying on email. |
| delivery_mode | string | – | The asynchronous delivery pattern used for this order. |
| error | string | – | A machine-readable error label when the request cannot be completed. |
| message | string | – | A human-readable status, authentication, or not-ready message. |
| notice | string | – | The notice that must travel with RegLayer research outputs. |
| ok | boolean | – | Whether the private status request succeeded. |
| order_id | string | – | The private RegLayer order identifier. |
| poll_after_seconds | – | – | Seconds to wait before the next status check, or null when no further polling is needed. |
| product | string | – | The purchased Instant Brief product code. |
| reference | string | – | The customer-facing brief reference. |
| status | string | – | The current order state, such as researching, ready, or failed. |
No examples provided.
list_instant_brief_products List RegLayer Instant Briefs ~20
List the Instant Brief available to agents.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| connection_required | boolean | yes | Whether the purchase connection must remain open while research runs. |
| delivery_instructions | string | yes | Instructions for storing credentials, polling, and retrieving the finished brief. |
| delivery_mode | string | yes | The delivery pattern used after payment. |
| notice | string | yes | The notice that must travel with RegLayer research outputs. |
| payment_protocol | string | yes | The machine-payment protocol used at the purchase endpoint. |
| poll_after_seconds | integer | yes | The recommended interval between private status checks. |
| products | array | yes | The Instant Brief products currently available to agents. |
| purchase_endpoint | string | yes | The REST endpoint that accepts the paid brief request. |
No examples provided.
list_reglayer_products List RegLayer agent products ~33
List the regulatory research products available to agents. Use an Instant Brief for a question and Check for supplied working materials.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
prepare_check_request Prepare a Check purchase ~59
Return the paid REST request shape for screening one or two supplied materials. The agent price is $0.99.
| Name | Type | Req | Description |
|---|---|---|---|
| material_count | integer | yes | – |
| total_characters | integer | yes | Combined readable-text character count after extracting the supplied materials. |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
prepare_instant_brief_request Prepare a RegLayer brief purchase ~64
Validate the scope and return the REST purchase shape. Payment occurs through HTTP 402 on the REST endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdictions | array | yes | The distinct regulatory geographies the Decision Brief should cover. |
| product | string | yes | The RegLayer Instant Brief product code. |
| Name | Type | Req | Description |
|---|---|---|---|
| after_payment | object | yes | What the agent must do after payment succeeds. |
| endpoint | string | yes | The REST endpoint to call to create and pay for the brief. |
| error | – | yes | A scope correction message, or null when the request is valid. |
| jurisdictions | array | yes | The normalized scope supplied for validation. |
| notice | string | yes | The notice that must travel with RegLayer research outputs. |
| price | object | yes | The selected product, price, and geographic limits. |
| product | string | yes | The RegLayer Instant Brief product code. |
| required_body_fields | array | yes | Fields that must be present in the purchase request body. |
| required_headers | object | yes | HTTP headers required by the purchase endpoint. |
| valid | boolean | yes | Whether the selected product and jurisdictions form a valid purchasable scope. |
No examples provided.
What is the RegLayer Instant Decision Briefs MCP server?
RegLayer Instant Decision Briefs is an MCP server listed in the public MCP registry as ai.reglayer/instant-decision-briefs. Company-specific regulatory assessments for concrete business questions, as structured data or PDF. This page covers its hosted endpoint (https://reglayer.ai/mcp).
Is the RegLayer Instant Decision Briefs MCP server safe to use?
RegLayer Instant Decision Briefs scores 79 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 RegLayer Instant Decision Briefs MCP server expose?
RegLayer Instant Decision Briefs exposes 10 tools: list_reglayer_products, list_instant_brief_products, prepare_instant_brief_request, get_instant_brief_status, get_instant_brief_result, and 5 more. Their descriptions and schemas cost roughly 534 tokens of context every time the server is loaded.
Does the RegLayer Instant Decision Briefs MCP server require authentication?
No. We connected to RegLayer Instant Decision Briefs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RegLayer Instant Decision Briefs MCP server still maintained?
RegLayer Instant Decision Briefs is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.