FLOCORE Governed MCP
Server Details
Governed MCP front door to FLOCORE; write calls need human approval and signed receipts.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 4 tools
Each tool targets a clearly distinct action: screening text, registering an onboarding request, asking a support question, and verifying a counterparty receipt. There is no overlap in intent and the descriptions make the boundaries explicit. An agent can pick the right tool without hesitation.
Three tools follow a consistent 'flocore_verb_noun' snake_case pattern, and 'aegis_inspect' uses the same verb_noun shape with a different product prefix. The mix of a two-segment name against three-segment names is a minor deviation, not a readability problem.
Four tools is on the lean side but each maps to a distinct governance/trust capability (screen, onboard, support, verify), so nothing feels redundant. Slightly thin for a full governance lifecycle, but well-scoped for a public, tokenless surface.
Onboarding returns a request id and sandbox token but there is no tool to query request/approval status or check whether a live token has been issued, leaving a dead end in the primary workflow. Screening, support, and verification are self-contained, but the create-without-status gap is notable.
Available Tools
4 toolsaegis_inspectScreen for prompt injectionAIdempotentInspect
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.
Inputs: text (required), agent, referred_by.
flocore_onboard_requestRequest governance onboardingAInspect
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.
Inputs: agent (required), org, source, public_key, +5 more.
flocore_support_askAsk FLOCORE support, agent to agentARead-onlyInspect
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.
Inputs: question (required).
flocore_verify_counterpartyVerify a counterparty agentARead-onlyIdempotentInspect
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.
Inputs: agent_slug (required), receipt_canonical, receipt_signature_ed25519.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Governed MCP gateway for business apps: roles, previews, approvals and one audit log.
The first MCP governed by ICA. Every action is gated and sealed with a verifiable receipt.
Foliora MCP for public discovery, account reads, and agent execution of human-approved changes.
MCP policy creation, quality checks and guarded data handoffs before automated writes.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceProvides a governed execution boundary for AI agents, enforcing deterministic policy, one-shot human approvals, and signed receipts for MCP tool effects.MIT
- AlicenseAqualityBmaintenanceEnables MCP-speaking agents to execute tool calls through an authorization gate, producing signed decision records and reconciled effect rows for accountability.6Apache 2.0
- AlicenseAqualityDmaintenanceDefault-deny action registry, append-only spend ledger, and human sign-off audit trail (MCP tools).6MIT
- AlicenseNot gradedqualityBmaintenanceProvides a governance proxy layer for MCP servers, enforcing per-tool allowlists, human approval for write operations, quotas, secret redaction, and a hash-chained audit log of all calls.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.