K-Work Trust

io.github.hycore220Published by GitHub account hycore220v0.1.0Updated Nov 2, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsBusiness & Commerce

Overview

AI-generated overview

Remote MCP demo endpoint for K-Work Trust, a Korean business-record trust gate; its exposed tools are only echo, add and server_time.

What you can do
  • Echo text back to the caller
  • Add two numbers and return the sum
  • Return the current server time in ISO 8601 UTC
  • Discovery calls (initialize, tools/list) are public; tool calls use the same API key, quota and abuse-guard policies as the protected REST workflow calls
When to use it
Only as a connectivity or discovery test for the K-Work Trust remote endpoint. The vendor-onboarding and payment/invoice release gates described in the README are REST endpoints, not tools exposed over MCP, so do not add it expecting those checks.
Requirements
A remote Streamable HTTP endpoint; no local package or runtime. An Authorization header with a Bearer KWT API key from the self-serve signup flow is required for tools/call and optional for initialize and tools/list. Network access to the hosted service.
Before you install
The API key is a secret sent in the Authorization header; keep it out of logs and reports. Tool calls consume quota and are subject to abuse blocking. The README warns against posting API keys, verification codes, customer records or sensitive business data.

Installation

In SourceWeft

  1. Open K-Work Trust in the dashboard and add it to a workspace.
  2. 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/io.github.hycore220%2Fk-work-trust/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "k-work-trust": {
      "type": "http",
      "url": "https://k-work-trust-api.fly.dev/mcp"
    }
  }
}

README

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

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

Source: README.md at commit c106eb3

Tools

3

echo

Echo

Echoes the provided text back to the caller.

Parameterstextrequired

add

Add

Adds two numbers and returns the sum.

Parametersarequiredbrequired

server_time

Server time

Returns the current server time (ISO 8601, UTC).

Takes no parameters.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

90% of the applicable checks met

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
  • License10 pts

    Declare a license in the repository or the registry entry.