FLOCORE Governed MCP
REMOTE · FO.FLOCORE.TECH · SCANNED SEP 20
Governed MCP front door to FLOCORE; write calls need human approval and signed receipts.
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 Security57
- 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 11 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
- 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 Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 884 tokens (~80/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 65% 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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 FLOCORE Governed MCP server?
FLOCORE Governed MCP is a hosted endpoint at https://fo.flocore.tech/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 · fo.flocore.tech
claude mcp add --transport http tech-flocore-flocore 'https://fo.flocore.tech/mcp'
{
"mcpServers": {
"tech-flocore-flocore": {
"url": "https://fo.flocore.tech/mcp"
}
}
} {
"servers": {
"tech-flocore-flocore": {
"type": "http",
"url": "https://fo.flocore.tech/mcp"
}
}
} [mcp_servers.tech-flocore-flocore] url = "https://fo.flocore.tech/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tech-flocore-flocore": {
"type": "remote",
"url": "https://fo.flocore.tech/mcp",
"enabled": true
}
}
} openclaw mcp add tech-flocore-flocore --url 'https://fo.flocore.tech/mcp' --transport streamable-http
mcp_servers:
tech-flocore-flocore:
url: "https://fo.flocore.tech/mcp" {
"McpServers": {
"tech-flocore-flocore": {
"Transport": "http",
"Url": "https://fo.flocore.tech/mcp"
}
}
} assistant mcp add tech-flocore-flocore -t streamable-http -u 'https://fo.flocore.tech/mcp'
{
"mcpServers": {
"tech-flocore-flocore": {
"type": "http",
"url": "https://fo.flocore.tech/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.
- 20 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.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
- Schema quality: 759 → 884 ▼ functional
- New tool “flocore_ask” functional
- 14 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.
- 12 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.
- 11 Sept 26 0
- “aegis_inspect” added an optional parameter “referred_by” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
- Schema quality: 63 → 73 ▼ functional
- Tool coverage: 42% → 59% ▲ functional
- New tool “flocore_onboard_request” functional
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 20 Sept 2026 · Probed https://fo.flocore.tech/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fo.flocore.tech | CN=YE1,O=Let's Encrypt,C=US | 14 Aug 2026 | 12 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 615057e54bbb1989d19c7da4ca853455d36 |
| SANs: fo.flocore.tech | ||||||
| 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 fo.flocore.tech. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tech. | present | 2185 | 13 | Verified |
| flocore.tech. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fo.flocore.tech/mcp | Verified | 200 | |
| http (plaintext) | http://fo.flocore.tech/mcp | HTTPS enforced | 301 | https://fo.flocore.tech/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 →
aegis_inspect ~134
Screen a prompt or text for injection, jailbreak and exfil intent. Free, public, defensive-only: returns a risk score (0..1), the detected intents, and whether it is suspicious. No token needed, nothing stored, no tenant data.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | optional: your agent name or a contact, to register interest and be onboarded to governed (human-gated, signed-receipt) actions |
| referred_by | string | – | optional: the agent id that referred you, so the referral is attributed to them |
| text | string | yes | the prompt or text to screen |
No output schema declared.
No examples provided.
flocore_ask ~125
Ask a plain-English question about a tenant's FLOCORE operations (tickets, queue, state). Answered by FLOCORE's Smart Switch Sentinel (routes across our hosted-LLM suite, cost-capped, on-box backup; every answer distilled into our own models), grounded on the tenant's real data and validated: an answer not supported by the data is refused, never invented. Read-only, tenant-scoped, AEGIS-screened.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | your plain-English question |
| tenant_slug | string | yes | the tenant to ask about |
No output schema declared.
No examples provided.
flocore_create_ticket ~60
Raise an operational ticket. WORLD-AFFECTING: this is gated on a human approval and will return APPROVAL_REQUIRED rather than executing.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| tenant_slug | string | yes | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
flocore_list_tenants ~27
List the tenants (customer/app operating boundaries) visible to your scoped token.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
flocore_list_tickets ~45
List operational tickets for a tenant, optionally filtered by status.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | optional status filter |
| tenant_slug | string | yes | tenant to read |
No output schema declared.
No examples provided.
flocore_mesh_lanes ~32
List the FLOCORE mesh lanes with kind, capabilities and liveness (live | stale | offline).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
flocore_onboard_request ~166
Request onboarding to FLOCORE governance for your world-affecting actions (human-gated approval, Ed25519 signed receipts, EU AI Act Article 12 audit evidence). Public: no token needed. This registers a request for HUMAN review and issues NO token; you get a request id and are contacted once approved.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | your agent name or identifier |
| intended_use | string | – | optional: what world-affecting actions you want governed |
| org | string | – | optional: the organisation the agent acts for |
| owner_contact | string | yes | an email or handle we can reach to confirm onboarding |
| referred_by | string | – | optional: the governed agent or partner that sent you here (so credit flows to whoever brought you) |
No output schema declared.
No examples provided.
flocore_ontology_entities ~31
Read the FLOCORE ontology: entity types, their semantic meaning, allowed relationships and lifecycle states.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
flocore_orch_board ~58
Read the FLOCORE orchestration board (W113 active mesh): lanes + liveness, work-queue summary, and governance caps + runaway flags. Read-only control-plane state.
| Name | Type | Req | Description |
|---|---|---|---|
| tenant_slug | string | – | optional scope |
No output schema declared.
No examples provided.
flocore_queue_summary ~55
Read the FLOCORE work-queue summary: open items by status, depth, oldest-queued age, awaiting-human, dead-letter, stuck. Optionally scoped to a tenant.
| Name | Type | Req | Description |
|---|---|---|---|
| tenant_slug | string | – | – |
No output schema declared.
No examples provided.
flocore_recall ~79
Ask FLOCORE's MEMORY: 'what do I know about X?'. Hybrid-lite retrieval over the semantic world-model; every result is PROVENANCE-STAMPED (who / source / trust). Read-only, silo-scoped.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| scope | string | – | – |
No output schema declared.
No examples provided.
What is the FLOCORE Governed MCP server?
FLOCORE Governed MCP is listed in the public MCP registry as tech.flocore/flocore. Governed MCP front door to FLOCORE; write calls need human approval and signed receipts. This page covers its hosted endpoint (https://fo.flocore.tech/mcp).
Is the FLOCORE Governed MCP server safe to use?
FLOCORE Governed MCP scores 71 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 FLOCORE Governed MCP server expose?
FLOCORE Governed MCP exposes 11 tools: aegis_inspect, flocore_onboard_request, flocore_list_tenants, flocore_ontology_entities, flocore_list_tickets, and 6 more. Their descriptions and schemas cost roughly 812 tokens of context every time the server is loaded.
Does the FLOCORE Governed MCP server require authentication?
No. We connected to FLOCORE Governed MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FLOCORE Governed MCP server still maintained?
FLOCORE Governed MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.