English Français العربية

K-Work Trust

Registre officiel IA et agents

Korean business record validation and workflow safety gates for AI agents.

Code source Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http k-work-trust 'https://k-work-trust-api.fly.dev/mcp' --header 'Authorization: <Bearer KWT API key issued through the public self-serve signup flow. Optional for initialize/tools/list and required for tools/call.>'
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "k-work-trust": {
            "type": "http",
            "url": "https://k-work-trust-api.fly.dev/mcp",
            "headers": {
                "Authorization": "<Bearer KWT API key issued through the public self-serve signup flow. Optional for initialize/tools/list and required for tools/call.>"
            }
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. K-Work Trust Public Demo
  2. Public Demo
  3. What To Test
  4. Safe Reporting Fields
  5. Synthetic Payload
  6. Minimal Metadata Fetch
  7. Remote MCP
  8. Product Gates
  9. Why This Exists
  10. Scope

K-Work Trust Public Demo

K-Work Trust is a remote MCP/API trust gate for AI agents before they write Korean business workflow records.

It helps an external AI agent inspect whether it should continue, pause, retry, stop, or escalate before registering vendors, checking invoice readiness, releasing payment or invoice steps, updating CRM, or touching ecommerce back-office records.

Public Demo

What To Test

  1. Read the public readiness endpoint.
  2. Read the agent manifest, skill instructions, and OpenAPI.
  3. Use POST https://k-work-trust-api.fly.dev/mcp if your client supports MCP Streamable HTTP.
  4. Use provisional signup if your agent has no inbox, or email-verified signup if it can read email.
  5. Call /v1/auth/whoami before spending quota.
  6. Run one synthetic /v1/vendor-onboarding/validate call.
  7. Report only non-secret debugging fields.

Safe Reporting Fields

  • request_id
  • endpoint called
  • HTTP status
  • response status and decision
  • first blocked step
  • confusing or missing response field

Do not post API keys, proof solutions, email verification codes, private customer records, production screenshots, or sensitive business data.

Synthetic Payload

See examples/synthetic-vendor.json. It is fake test data and is safe to copy into a local agent experiment.

Minimal Metadata Fetch

node examples/fetch-public-metadata.js

The script reads public metadata only. It does not require an API key.

Remote MCP

Remote MCP supports initialize, tools/list, and tools/call over JSON-response Streamable HTTP. initialize and tools/list are public for discovery; MCP tools/call uses the same API key, quota, official-source, and abuse-guard policies as protected REST workflow calls.

Product Gates

  • validate_vendor_onboarding: decide whether a Korean vendor/customer record can be registered.
  • validate_payment_or_invoice_release: decide whether an agent can release a payment, invoice, settlement, or purchase step, or whether it must prepare a human review packet first.

Why This Exists

Mature KYB platforms are broad compliance systems for onboarding, UBO, sanctions, adverse media, and case review. K-Work Trust is narrower: a small agent-readable pre-action gate with stable JSON decisions, public MCP discovery, low-quota test keys, and Korean business-field logic.

The core response contract is meant for another agent to use directly:

  • decision
  • blocking_issues
  • warnings
  • evidence
  • agent_next_action

Scope

This public demo repo intentionally excludes private operating memory, API usage logs, credentials, .env, local model files, and customer data. The production service enforces authentication, low beta quotas, and behavior-based abuse blocking for protected workflow calls.

Questions fréquentes

Qu'est-ce que K-Work Trust ?

Korean business record validation and workflow safety gates for AI agents.

Comment installer K-Work Trust ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http k-work-trust 'https://k-work-trust-api.fly.dev/mcp' --header 'Authorization: <Bearer KWT API key issued through the public self-serve signup flow. Optional for initialize/tools/list and required for tools/call.>'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour K-Work Trust ?

Oui. Il attend Authorization, à renseigner dans sa configuration.

K-Work Trust est-il open source ?

Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.

Qui maintient K-Work Trust ?

Il est publié par hycore220. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.