FLOCORE Governed MCP
REMOTE · FO.FLOCORE.TECH
Governed MCP front door to FLOCORE; write calls need human approval and signed receipts.
Available components
Last scanned (54 minutes ago)
Scores higher than 89% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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 Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 975 tokens (~243/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
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 current MCP spec version (2026-07-28).Pass
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.
- 31 Oct 26 +9
- Stability: fail → pass ▲ security
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 25 to 31.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 18 to 25.
- 10 Oct 26 +3
No change was recorded against any check on this day. Stability & Change Management went from 0 to 20.
- 7 Oct 26 −1
- Tool “flocore_onboard_request” rewrote its description, which is the text the model reads security
- Schema quality: 220 → 243 ▼ functional
- “flocore_onboard_request” added an optional parameter “rehearsal_only” cosmetic
- “flocore_onboard_request” reworded the description of “owner_contact” cosmetic
- “flocore_onboard_request” made “owner_contact” optional cosmetic
- 6 Oct 26 +1
No change was recorded against any check on this day. Schema Quality & AI Usability went from 68 to 73.
- 4 Oct 26 0
- Tool “flocore_support_ask” rewrote its description, which is the text the model reads security
- 2 Oct 26 0
- Schema quality: 194 → 215 ▼ functional
- “flocore_onboard_request” added an optional parameter “jurisdiction” cosmetic
- “flocore_onboard_request” added an optional parameter “source” cosmetic
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 5 Nov 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=YE2,O=Let's Encrypt,C=US | 13 Oct 2026 | 11 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6782cfa210661704d039bac446c415e510f |
| SANs: fo.flocore.tech | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://cdn.jsdelivr.net https://cdnjs.cloudflare.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://cdn.jsdelivr.net https://cdnjs.cloudflare.com; font-src 'self' https://fonts.gstatic.com https://cdn.jsdelivr.net https://cdnjs.cloudflare.com; img-src 'self' data: https:; connect-src 'self'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| 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://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 Screen for prompt injection ~159
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, no tenant data. A pattern screen: it misses paraphrases, so a clean result is not a guarantee. An anonymous call stores nothing; if you pass an agent name, that name and the score are recorded.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | optional: your agent name or a contact; if given, it is recorded with the score |
| 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_onboard_request Request governance onboarding ~420
Registers an onboarding request for human review (human-gated approval, Ed25519 signed receipts, EU AI Act Article 12 audit evidence). Public: no token needed. Returns a request id and a sandbox token (fc_test_...) immediately, to rehearse the loop; a live token is issued only after a person approves the application. Set rehearsal_only to true to get a sandbox token without applying.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | your agent name or identifier |
| intended_use | string | – | optional: what world-affecting actions you want governed |
| jurisdiction | string | – | optional: the legal jurisdiction that brought you here, a code from the Advatar pitch (eu, coe, za, kr, us, vn, ng, ke, mx, oecd). Recorded so we learn which law matters to builders |
| org | string | – | optional: the organisation the agent acts for |
| owner_contact | string | – | the email address of the person who owns the agent, so a person can approve it and be sent its token (required unless rehearsal_only is true) |
| public_key | string | – | optional: your agent's own Ed25519 PUBLIC key, raw 32 bytes as base64url or a public JWK as JSON text. Give it and, once a human approves you, your token is bound to it and your key's thumbprint appe… |
| referred_by | string | – | optional: the governed agent or partner that sent you here (recorded as the referral) |
| rehearsal_only | boolean | – | optional: true to get ONLY a sandbox token to rehearse the approval loop. Nothing is registered, no email is sent and no one is asked to review anything. Limits: 3 per hour per connection. To apply f… |
| source | string | – | optional: where you found us, for example a registry or the pitch (letters, digits, dots and dashes) |
No output schema declared.
No examples provided.
flocore_support_ask Ask FLOCORE support, agent to agent ~132
Ask a plain-English support/product question about FLOCORE itself, agent to agent, instead of a helpdesk. Public, no token needed. Answered only from FLOCORE's own real, published, reproducible claims: an answer not supported by them is refused, never invented. Privacy: your question (max 500 characters) is sent to a hosted language model provider, currently Groq in the United States, to choose which published sentences answer it; do not include personal information. See https://humanseal.world/privacy.html.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | your plain-English question about FLOCORE |
No output schema declared.
No examples provided.
flocore_verify_counterparty Verify a counterparty agent ~161
Before transacting with another agent, check whether it is FLOCORE-governed (a human-approval gate on its world-affecting actions, Ed25519 signed receipts) and, if it handed you a receipt, verify that receipt independently. Public, no token needed. A sandbox receipt is reported as a rehearsal and never as valid proof.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_slug | string | yes | the counterparty's FLOCORE agent/tenant slug |
| receipt_canonical | string | – | optional: the receipt's `canonical` field, if the counterparty handed you one to check |
| receipt_signature_ed25519 | string | – | optional: the receipt's `signature_ed25519` field, required together with receipt_canonical to verify it |
No output schema declared.
No examples provided.
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'
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 84 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 4 tools: aegis_inspect, flocore_onboard_request, flocore_support_ask, flocore_verify_counterparty. Their descriptions and schemas cost roughly 872 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.