FAIE
REMOTE · FABRIC.SYSTEMIACOMMANDCENTERS.COM
Evidence-first food-infrastructure and resilience intelligence on owned Evercraft Fabric.
Available components
Last scanned (15 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 18 Oct 2026.
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 Security74
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 343 tokens (~85/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage69
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 6% of tool parameters carry a description.Partial
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
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +42
- HSTS header: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- Authorization: unverified → partial ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.27 ▲ functional
- 14 Oct 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 13 Oct 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 12 Oct 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 10 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Tool safety: pass → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- First check of Schema quality: unverified functional
- 9 Oct 26 65
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 18 Oct 2026 · Probed https://fabric.systemiacommandcenters.com/mcp/faie
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fabric.systemiacommandcenters.com | CN=YE1,O=Let's Encrypt,C=US | 30 Sept 2026 | 29 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6c56c9ec620ddfc9211d22e8121574db06a |
| SANs: fabric.systemiacommandcenters.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of fabric.systemiacommandcenters.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| systemiacommandcenters.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fabric.systemiacommandcenters.com/mcp/faie | Verified | 200 | |
| http (plaintext) | http://fabric.systemiacommandcenters.com/mcp/faie | HTTPS enforced | 308 | https://fabric.systemiacommandcenters.com/mcp/faie |
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 →
compare_faie_candidates Compare candidate food-infrastructure or agriculture scopes by evidence readiness ~112
Run the same bounded FAIE evidence rubric across 2 to 8 candidate regions or sites. The returned rank is evidence-readiness only, not site suitability or an investment recommendation.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_types | array | – | – |
| candidates | array | yes | – |
| crop | string | – | – |
| horizon_days | integer | – | – |
| include_weak_evidence | boolean | – | – |
| question | string | yes | – |
| thesis_assumptions | array | – | – |
| water_source | string | – | – |
No output schema declared.
No examples provided.
get_faie_health Read FAIE runtime health ~28
Return FAIE resident, source-health, and signal-count status without exposing private investigation content.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_faie_signal_snapshot Read the current FAIE signal field ~36
Return the latest public-safe FAIE signal snapshot. Read-only and non-transactional.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
investigate_faie_evidence Investigate agriculture, land, water, production, or resilience evidence ~111
Run a bounded FAIE evidence investigation. Public MCP investigations are ephemeral previews and do not persist the caller question into the shared investigation archive.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_types | array | – | – |
| crop | string | – | – |
| horizon_days | integer | – | – |
| include_weak_evidence | boolean | – | – |
| question | string | yes | The bounded evidence question to investigate. |
| region_keys | array | – | – |
| thesis_assumptions | array | – | – |
| water_source | string | – | – |
No output schema declared.
No examples provided.
How do I install the FAIE MCP server?
FAIE is a hosted endpoint at https://fabric.systemiacommandcenters.com/mcp/faie, 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 · fabric.systemiacommandcenters.com
claude mcp add --transport http jgaethle10-faie 'https://fabric.systemiacommandcenters.com/mcp/faie'
What is the FAIE MCP server?
FAIE is an MCP server listed in the public MCP registry as io.github.jgaethle10/faie. Evidence-first food-infrastructure and resilience intelligence on owned Evercraft Fabric. This page covers its hosted endpoint (https://fabric.systemiacommandcenters.com/mcp/faie).
Is the FAIE MCP server safe to use?
FAIE scores 70 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 FAIE MCP server expose?
FAIE exposes 4 tools: investigate_faie_evidence, compare_faie_candidates, get_faie_signal_snapshot, get_faie_health. Their descriptions and schemas cost roughly 287 tokens of context every time the server is loaded.
Does the FAIE MCP server require authentication?
No. We connected to FAIE without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FAIE MCP server still maintained?
FAIE is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.