# FLOCORE Governed MCP (remote · fo.flocore.tech)

Governed MCP front door to FLOCORE; write calls need human approval and signed receipts.

- Trust score: 71/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `fo.flocore.tech`: 71/100 (this document), [markdown](https://verifymcp.io/servers/tech-flocore-flocore/fo.md), [page](https://verifymcp.io/servers/tech-flocore-flocore/fo)

## Channel facts

- Endpoint: `https://fo.flocore.tech/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 884 tokens (~80/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 65% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http tech-flocore-flocore 'https://fo.flocore.tech/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tech-flocore-flocore": {
      "url": "https://fo.flocore.tech/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tech-flocore-flocore": {
      "type": "http",
      "url": "https://fo.flocore.tech/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tech-flocore-flocore]
url = "https://fo.flocore.tech/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tech-flocore-flocore": {
      "type": "remote",
      "url": "https://fo.flocore.tech/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tech-flocore-flocore --url 'https://fo.flocore.tech/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tech-flocore-flocore:
    url: "https://fo.flocore.tech/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tech-flocore-flocore": {
      "Transport": "http",
      "Url": "https://fo.flocore.tech/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tech-flocore-flocore -t streamable-http -u 'https://fo.flocore.tech/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 71, +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.

### 2026-09-18 (score 70, +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.

### 2026-09-16 (score 69, +1)

- [functional regression] Schema quality: 759 → 884
- [functional] New tool “flocore_ask”

### 2026-09-14 (score 68, +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.

### 2026-09-12 (score 67, +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.

### 2026-09-11 (score 66, 0)

- [cosmetic] “aegis_inspect” added an optional parameter “referred_by”

### 2026-09-10 (score 66, +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.

### 2026-09-09 (score 65, +1)

- [functional regression] Schema quality: 63 → 73
- [functional improvement] Tool coverage: 42% → 59%
- [functional] New tool “flocore_onboard_request”

## MCP tools (11)

### `aegis_inspect` (~134 tokens)

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.

Input parameters:

- `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, required): the prompt or text to screen

### `flocore_onboard_request` (~166 tokens)

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.

Input parameters:

- `agent` (string, required): 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, required): 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)

### `flocore_list_tenants` (~27 tokens)

List the tenants (customer/app operating boundaries) visible to your scoped token.

### `flocore_ontology_entities` (~31 tokens)

Read the FLOCORE ontology: entity types, their semantic meaning, allowed relationships and lifecycle states.

### `flocore_list_tickets` (~45 tokens)

List operational tickets for a tenant, optionally filtered by status.

Input parameters:

- `status` (string): optional status filter
- `tenant_slug` (string, required): tenant to read

### `flocore_orch_board` (~58 tokens)

Read the FLOCORE orchestration board (W113 active mesh): lanes + liveness, work-queue summary, and governance caps + runaway flags. Read-only control-plane state.

Input parameters:

- `tenant_slug` (string): optional scope

### `flocore_queue_summary` (~55 tokens)

Read the FLOCORE work-queue summary: open items by status, depth, oldest-queued age, awaiting-human, dead-letter, stuck. Optionally scoped to a tenant.

Input parameters:

- `tenant_slug` (string)

### `flocore_mesh_lanes` (~32 tokens)

List the FLOCORE mesh lanes with kind, capabilities and liveness (live | stale | offline).

### `flocore_recall` (~79 tokens)

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.

Input parameters:

- `limit` (integer)
- `query` (string, required)
- `scope` (string)

### `flocore_ask` (~125 tokens)

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.

Input parameters:

- `question` (string, required): your plain-English question
- `tenant_slug` (string, required): the tenant to ask about

### `flocore_create_ticket` (~60 tokens)

Raise an operational ticket. WORLD-AFFECTING: this is gated on a human approval and will return APPROVAL_REQUIRED rather than executing.

Input parameters:

- `description` (string)
- `tenant_slug` (string, required)
- `title` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tech-flocore-flocore/fo#diagnostics

## Score history

- 2026-09-20: 71
- 2026-09-19: 70
- 2026-09-18: 70
- 2026-09-17: 69
- 2026-09-16: 69
- 2026-09-15: 68
- 2026-09-14: 68
- 2026-09-13: 67
- 2026-09-12: 67
- 2026-09-11: 66
- 2026-09-10: 66
- 2026-09-09: 65
- 2026-09-08: 64
- 2026-09-07: 63
- 2026-09-06: 63

## Common questions

### 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.

## Links

- Remote endpoint: https://fo.flocore.tech/mcp
- Website: https://fo.flocore.tech/
- Changelog RSS feed: https://verifymcp.io/servers/tech-flocore-flocore/fo.xml
- Changelog JSON feed: https://verifymcp.io/servers/tech-flocore-flocore/fo.json
- HTML version of this page: https://verifymcp.io/servers/tech-flocore-flocore/fo