build.fabricate/fabricate
REMOTE · FABRICATE.BUILD · SCANNED OCT 2
Public Fabricate pricing and documentation tools.
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 Security83
- 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 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 Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 676 tokens (~169/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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 build.fabricate/fabricate MCP server?
build.fabricate/fabricate is a hosted endpoint at https://fabricate.build/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 · fabricate.build
claude mcp add --transport http build-fabricate-fabricate 'https://fabricate.build/mcp'
{
"mcpServers": {
"build-fabricate-fabricate": {
"url": "https://fabricate.build/mcp"
}
}
} {
"servers": {
"build-fabricate-fabricate": {
"type": "http",
"url": "https://fabricate.build/mcp"
}
}
} [mcp_servers.build-fabricate-fabricate] url = "https://fabricate.build/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"build-fabricate-fabricate": {
"type": "remote",
"url": "https://fabricate.build/mcp",
"enabled": true
}
}
} openclaw mcp add build-fabricate-fabricate --url 'https://fabricate.build/mcp' --transport streamable-http
mcp_servers:
build-fabricate-fabricate:
url: "https://fabricate.build/mcp" {
"McpServers": {
"build-fabricate-fabricate": {
"Transport": "http",
"Url": "https://fabricate.build/mcp"
}
}
} assistant mcp add build-fabricate-fabricate -t streamable-http -u 'https://fabricate.build/mcp'
{
"mcpServers": {
"build-fabricate-fabricate": {
"type": "http",
"url": "https://fabricate.build/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.
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 28 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
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 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 2 Oct 2026 · Probed https://fabricate.build/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fabricate.build | CN=WE1,O=Google Trust Services,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | dce5c1dfa01537b1130626ec9a484368 |
| SANs: fabricate.build | ||||||
| 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 secure
Validation of fabricate.build. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| build. | present | 30770, 38839 | 8, 8 | Verified |
| fabricate.build. | present | 2371 | 13 | Verified |
| fabricate.build. | 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; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), usb=(), magnetometer=(), gyroscope=(), accelerometer=(), tools=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fabricate.build/mcp | Verified | 200 | |
| http (plaintext) | http://fabricate.build/mcp | HTTPS enforced | 301 | https://fabricate.build/mcp |
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 →
fabricate_get_agent_guide ~26
Learn public access, signed-in browser workflows, permissions and truthful referral attribution.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fabricate_get_plans ~31
Get current Fabricate plans, prices in USD, monthly credits and per-generation credit limits from billing configuration.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fabricate_read_page ~39
Read a canonical public page as Markdown. Use a path returned by fabricate_search_pages, e.g. /pricing.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
fabricate_search_pages ~40
Find canonical public Fabricate pages by URL keywords. No private apps or account data.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
What is the build.fabricate/fabricate MCP server?
build.fabricate/fabricate is an MCP server listed in the public MCP registry as build.fabricate/fabricate. Public Fabricate pricing and documentation tools. This page covers its hosted endpoint (https://fabricate.build/mcp).
Is the build.fabricate/fabricate MCP server safe to use?
build.fabricate/fabricate scores 80 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 build.fabricate/fabricate MCP server expose?
build.fabricate/fabricate exposes 4 tools: fabricate_get_plans, fabricate_search_pages, fabricate_read_page, fabricate_get_agent_guide. Their descriptions and schemas cost roughly 136 tokens of context every time the server is loaded.
Does the build.fabricate/fabricate MCP server require authentication?
No. We connected to build.fabricate/fabricate without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the build.fabricate/fabricate MCP server still maintained?
build.fabricate/fabricate is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.