A public, remote MCP endpoint for FLOCORE governance: screen text for injection, ask product questions, request onboarding, and verify counterparties.
What you can do
Screen prompts or text for injection, jailbreak and exfiltration intent, returning a risk score and detected intents. Ask plain-English support questions about FLOCORE, answered only from its published claims. Register an onboarding request for human review and receive a request id plus a sandbox token. Check whether another agent is FLOCORE-governed and verify a receipt it handed you.
When to use it
Useful when you want a quick defensive screen of untrusted text, need factual answers about FLOCORE itself, or want to check another agent's governance status and receipts before transacting.
Requirements
A remote streamable HTTP endpoint; no package, token or environment variable is declared. The tools are described as public and free, with no token needed.
Before you install
The injection screen is pattern-based and misses paraphrases, so a clean result is not a guarantee. Onboarding returns only a sandbox token until a person approves; sandbox receipts are rehearsals, not live proof. Support questions up to 500 characters are sent to the service, so avoid sensitive content.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/tech.flocore%2Fflocore/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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.
Parameterstextrequiredagentreferred_by
flocore_onboard_request
Request governance onboarding
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.
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.
Parametersquestionrequired
flocore_verify_counterparty
Verify a counterparty agent
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.
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.
