BuildFlow Enterprise Operations
REMOTE · BASE44.APP · SCANNED SEP 25
Discover, route, and hand off enterprise operations problems without exposing private records.
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 174 tokens (~58/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the BuildFlow Enterprise Operations MCP server?
BuildFlow Enterprise Operations is a hosted endpoint at https://base44.app/api/apps/6ab26dc00debf9a25bca5f3e/functions/enterpriseOpsMcp, 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 · base44.app
claude mcp add --transport http jgaethle10-buildflow 'https://base44.app/api/apps/6ab26dc00debf9a25bca5f3e/functions/enterpriseOpsMcp'
{
"mcpServers": {
"jgaethle10-buildflow": {
"url": "https://base44.app/api/apps/6ab26dc00debf9a25bca5f3e/functions/enterpriseOpsMcp"
}
}
} {
"servers": {
"jgaethle10-buildflow": {
"type": "http",
"url": "https://base44.app/api/apps/6ab26dc00debf9a25bca5f3e/functions/enterpriseOpsMcp"
}
}
} [mcp_servers.jgaethle10-buildflow] url = "https://base44.app/api/apps/6ab26dc00debf9a25bca5f3e/functions/enterpriseOpsMcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jgaethle10-buildflow": {
"type": "remote",
"url": "https://base44.app/api/apps/6ab26dc00debf9a25bca5f3e/functions/enterpriseOpsMcp",
"enabled": true
}
}
} openclaw mcp add jgaethle10-buildflow --url 'https://base44.app/api/apps/6ab26dc00debf9a25bca5f3e/functions/enterpriseOpsMcp' --transport streamable-http
mcp_servers:
jgaethle10-buildflow:
url: "https://base44.app/api/apps/6ab26dc00debf9a25bca5f3e/functions/enterpriseOpsMcp" {
"McpServers": {
"jgaethle10-buildflow": {
"Transport": "http",
"Url": "https://base44.app/api/apps/6ab26dc00debf9a25bca5f3e/functions/enterpriseOpsMcp"
}
}
} assistant mcp add jgaethle10-buildflow -t streamable-http -u 'https://base44.app/api/apps/6ab26dc00debf9a25bca5f3e/functions/enterpriseOpsMcp'
{
"mcpServers": {
"jgaethle10-buildflow": {
"type": "http",
"url": "https://base44.app/api/apps/6ab26dc00debf9a25bca5f3e/functions/enterpriseOpsMcp"
}
}
} 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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 63
First indexed and scored.
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 25 Sept 2026 · Probed https://base44.app/api/apps/6ab26dc00debf9a25bca5f3e/functions/enterpriseOpsMcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.base44.app | CN=YR2,O=Let's Encrypt,C=US | 12 Sept 2026 | 11 Dec 2026 | RSA 2048 | SHA256-RSA | 5b99279f037a30a0bbe8d284eab58237ba3 |
| SANs: *.base44.app, base44.app | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of base44.app. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| base44.app. | present | 2371 | 13 | Verified |
| base44.app. | Verified address RRset verified with the apex keys |
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 |
| content-security-policy | script-src 'none'; object-src 'none'; |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://base44.app/api/apps/6ab26dc00debf9a25bca5f3e/functions/enterpriseOpsMcp | Verified | 200 | |
| http (plaintext) | http://base44.app/api/apps/6ab26dc00debf9a25bca5f3e/functions/enterpriseOpsMcp | HTTPS enforced | 301 | https://base44.app/api/apps/6ab26dc00debf9a25bca5f3e/functions/enterpriseOpsMcp |
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 →
buildflow_discover_capabilities ~27
Return BuildFlow's public currently wired enterprise-operations capabilities and safety boundaries.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
buildflow_prepare_handoff ~60
Prepare a privacy-preserving human handoff bundle. Does not transmit customer data or execute business actions.
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | array | – | – |
| data_shape | string | – | – |
| goal | string | – | – |
| problem | string | – | – |
No output schema declared.
No examples provided.
buildflow_route_intent ~67
Match an enterprise-operations problem to the smallest current BuildFlow capability. Never send private customer records.
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | array | – | – |
| data_shape | string | – | – |
| goal | string | – | – |
| intent | string | – | – |
| problem | string | – | – |
No output schema declared.
No examples provided.
What is the BuildFlow Enterprise Operations MCP server?
BuildFlow Enterprise Operations is an MCP server listed in the public MCP registry as io.github.jgaethle10/buildflow. Discover, route, and hand off enterprise operations problems without exposing private records. This page covers its hosted endpoint (https://base44.app/api/apps/6ab26dc00debf9a25bca5f3e/functions/enterpriseOpsMcp).
Is the BuildFlow Enterprise Operations MCP server safe to use?
BuildFlow Enterprise Operations scores 63 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 BuildFlow Enterprise Operations MCP server expose?
BuildFlow Enterprise Operations exposes 3 tools: buildflow_discover_capabilities, buildflow_route_intent, buildflow_prepare_handoff. Their descriptions and schemas cost roughly 154 tokens of context every time the server is loaded.
Does the BuildFlow Enterprise Operations MCP server require authentication?
No. We connected to BuildFlow Enterprise Operations without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BuildFlow Enterprise Operations MCP server still maintained?
BuildFlow Enterprise Operations is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.