Developer Tools
forgo.cloud
Automates the extraction, modeling, verification, and documentation of technical requirements using formal methods.
ENDPOINT 1
https://forgo.cloud/mcp
MCP server metadata
- Name
- forgo-trd
- Version
- 0.1.0
Known tools 5
forgo_trd_extract_requirementsExtract normalized requirement records from a markdown source document or an imported requirement list.
Inferred read-onlyforgo_trd_generate_topologyMap a requirements dataset onto the minimum FORGO service model and emit the GG topology contract.
Inferred read-onlyforgo_trd_verify_topologyRun formal Gnosis analysis plus GG temporal checks over a topology source or the synthesized FORGO minimum topology.
Inferred read-onlyforgo_trd_hydrate_documentHydrate the normalized requirements and minimum service model into a Technical Requirements Doc.
Inferred read-onlyforgo_trd_pipelineRun the full TRD development process: extract requirements, synthesize the minimum topology, formally verify it, and hydrate the resulting technical requirements doc.
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.forgo-trd]
url = "https://forgo.cloud/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"forgo-trd": {
"type": "http",
"url": "https://forgo.cloud/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: forgo-trd
Remote MCP URL: https://forgo.cloud/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": {
"forgo-trd": {
"url": "https://forgo.cloud/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"forgo-trd": {
"type": "http",
"url": "https://forgo.cloud/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "forgo-trd",
"transport": "streamable-http",
"url": "https://forgo.cloud/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 forgo.cloud was fetched 2026-07-26T19:26:27.452Z and is being refreshed.
forgo.cloud 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.