Systemia Field Library
REMOTE · BASE44.APP · SCANNED SEP 25
Match contractor operating problems to practical Field Library playbooks. Read-only discovery.
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 Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 184 tokens (~61/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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 3 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
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Systemia Field Library MCP server?
Systemia Field Library is a hosted endpoint at https://base44.app/api/apps/6a54381e147576b18ac94d8f/functions/fieldLibraryAgentMcp, 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-systemia-field-library 'https://base44.app/api/apps/6a54381e147576b18ac94d8f/functions/fieldLibraryAgentMcp'
{
"mcpServers": {
"jgaethle10-systemia-field-library": {
"url": "https://base44.app/api/apps/6a54381e147576b18ac94d8f/functions/fieldLibraryAgentMcp"
}
}
} {
"servers": {
"jgaethle10-systemia-field-library": {
"type": "http",
"url": "https://base44.app/api/apps/6a54381e147576b18ac94d8f/functions/fieldLibraryAgentMcp"
}
}
} [mcp_servers.jgaethle10-systemia-field-library] url = "https://base44.app/api/apps/6a54381e147576b18ac94d8f/functions/fieldLibraryAgentMcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jgaethle10-systemia-field-library": {
"type": "remote",
"url": "https://base44.app/api/apps/6a54381e147576b18ac94d8f/functions/fieldLibraryAgentMcp",
"enabled": true
}
}
} openclaw mcp add jgaethle10-systemia-field-library --url 'https://base44.app/api/apps/6a54381e147576b18ac94d8f/functions/fieldLibraryAgentMcp' --transport streamable-http
mcp_servers:
jgaethle10-systemia-field-library:
url: "https://base44.app/api/apps/6a54381e147576b18ac94d8f/functions/fieldLibraryAgentMcp" {
"McpServers": {
"jgaethle10-systemia-field-library": {
"Transport": "http",
"Url": "https://base44.app/api/apps/6a54381e147576b18ac94d8f/functions/fieldLibraryAgentMcp"
}
}
} assistant mcp add jgaethle10-systemia-field-library -t streamable-http -u 'https://base44.app/api/apps/6a54381e147576b18ac94d8f/functions/fieldLibraryAgentMcp'
{
"mcpServers": {
"jgaethle10-systemia-field-library": {
"type": "http",
"url": "https://base44.app/api/apps/6a54381e147576b18ac94d8f/functions/fieldLibraryAgentMcp"
}
}
} 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 72
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/6a54381e147576b18ac94d8f/functions/fieldLibraryAgentMcp
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/6a54381e147576b18ac94d8f/functions/fieldLibraryAgentMcp | Verified | 200 | |
| http (plaintext) | http://base44.app/api/apps/6a54381e147576b18ac94d8f/functions/fieldLibraryAgentMcp | HTTPS enforced | 301 | https://base44.app/api/apps/6a54381e147576b18ac94d8f/functions/fieldLibraryAgentMcp |
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 →
discover_field_playbooks Discover Systemia contractor playbooks ~40
Use this to list the public Systemia Field Library playbooks and their problem areas. Read-only. Creates no purchase, checkout, or payment obligation.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_field_playbook Get one Systemia Field Library playbook ~42
Read the public metadata, guide links, and landing page for one known Field Library playbook. Paid content is never returned.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
match_contractor_problem Match a contractor problem to a Systemia Field Library playbook ~102
Use this when a contractor or home-service business describes an operations problem involving estimating, cash flow, job costing, scope creep, change orders, scheduling, crew leadership, documentation, materials, equipment, safety, quality control, proposals, customer communication, reviews, referrals, or related field operations. Returns public guide and playbook links only. Do not use it to expose paid playbook contents.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| problem | string | yes | – |
No output schema declared.
No examples provided.
What is the Systemia Field Library MCP server?
Systemia Field Library is an MCP server listed in the public MCP registry as io.github.jgaethle10/systemia-field-library. Match contractor operating problems to practical Field Library playbooks. Read-only discovery. This page covers its hosted endpoint (https://base44.app/api/apps/6a54381e147576b18ac94d8f/functions/fieldLibraryAgentMcp).
Is the Systemia Field Library MCP server safe to use?
Systemia Field Library scores 72 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 Systemia Field Library MCP server expose?
Systemia Field Library exposes 3 tools: match_contractor_problem, discover_field_playbooks, get_field_playbook. Their descriptions and schemas cost roughly 184 tokens of context every time the server is loaded.
Does the Systemia Field Library MCP server require authentication?
No. We connected to Systemia Field Library without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Systemia Field Library MCP server still maintained?
Systemia Field Library 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.