General Tools
reglayer.ai
Provides general-purpose tools through the Model Context Protocol.
ENDPOINT 1
https://reglayer.ai/mcp
MCP server metadata
- Name
- RegLayer
- Version
- 2026-08-28.1
Known tools 10
prepare_instant_brief_requestValidate the scope and return the REST purchase shape.
Potential side effectsget_instant_brief_pdfReturn the authenticated PDF endpoint after status reaches ready.
Inferred read-onlyprepare_check_requestReturn the paid REST request shape for screening one or two supplied materials.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.reglayer]
url = "https://reglayer.ai/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"reglayer": {
"type": "http",
"url": "https://reglayer.ai/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: reglayer
Remote MCP URL: https://reglayer.ai/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"reglayer": {
"url": "https://reglayer.ai/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"reglayer": {
"type": "http",
"url": "https://reglayer.ai/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "reglayer",
"transport": "streamable-http",
"url": "https://reglayer.ai/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for reglayer.ai was fetched 2026-08-23T13:12:09.117Z.
reglayer.ai is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.