Badge

io.github.payclawPublished by GitHub account payclawv0.4.0Updated Oct 24, 2026

Agents are not bots. Prove it. MCP-native identity declaration for authorized agents.

VerifiedSTDIODesktop onlySecurity & Monitoring Business & Commerce

Server details

Identifier: io.github.payclaw/badge
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account payclaw for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.payclaw%2Fbadge.svg)](https://sourceweft.com/mcp/io.github.payclaw%2Fbadge?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server that gives AI agents a persistent identity credential to declare visits and report outcomes to merchant sites.

What you can do: Declare agent visits to merchant sites with a run ID and URL, and report visit outcomes back to the service. Issue and cache a guest pass on first run so identity survives process restarts. Feed reported outcomes into a portable trust score across merchants. Wrap the Badge SDK so MCP clients get the same identity model, tokens and scoring.
When to use it: Use it when an agent interacts with merchant sites that check agent identity and you want visits and outcomes recorded under a persistent, portable identity rather than an anonymous bot session.
Requirements: Runs as a local process via npx, so Node.js is needed. A PayClaw API key is required in the PAYCLAW_API_KEY environment variable, and the API endpoint can be overridden with PAYCLAW_API_URL (default Network access to that endpoint is required.

Before you install

Requires a PayClaw API key stored in PAYCLAW_API_KEY, which is sent to the configured API endpoint. Visit declarations and outcomes are reported to a third-party service and feed a trust score, so merchant URLs and activity leave the machine. The README also describes a guest pass cached to disk, which persists identity between runs.

Installation

In SourceWeft

Open Badge in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Badge by kya labs

Persistent identity for AI agents across merchant sites. Badge gives agents a credential they carry on every request — merchants verify it, trust accumulates across visits, and agents that build history earn better treatment over time.

Framework-agnostic. Transport-agnostic. Zero runtime dependencies.

Badge SDK

The SDK is the primary integration surface. Three methods cover the full lifecycle:

typescript

import { Badge } from "@kyalabs/badge-sdk";
const badge = await Badge.init();const runId = badge.startRun();
await badge.declareVisit({  merchant: "store.example.com",  runId,  url: "https://store.example.com/cart",});
await badge.reportOutcome({  merchant: "store.example.com",  runId,  outcome: "not_denied",});

import { Badge } from "@kyalabs/badge-sdk";
const badge = await Badge.init();const runId = badge.startRun();
await badge.declareVisit({  merchant: "store.example.com",  runId,  url: "https://store.example.com/cart",});
await badge.reportOutcome({  merchant: "store.example.com",  runId,  outcome: "not_denied",});

No signup. No API key. Badge.init() issues a guest pass on first run and caches it to disk. Identity survives process restarts.

Full SDK documentation →

What the SDK covers

Identity model — three-tier ladder: guest pass (gp_v1_*) → badge token (kya_*) → authenticated identity
Lifecycle tracking — declare visits, report outcomes, correlate with run IDs
Offline resilience — never throws on network failure, deterministic fallback on every call
UCP integration — io.kyalabs.common.identity Credential Provider, published schemas, ES256-signed JWTs
Scoring — outcomes feed kyaScore (500–850), portable across merchants

[npm]

Badge MCP Server

For MCP client users (Claude Desktop, Cursor, Windsurf), Badge also ships as an MCP tool server. The MCP server wraps the SDK — same identity model, same tokens, same scoring.

The SDK is the canonical integration path for platform builders and agent frameworks. The MCP server is a convenience wrapper for end users working within MCP clients.

[npm]

License

MIT

Source: README.md at commit 829bf50

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.4.0LatestSep 16, 2026

Score

50% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts