Agent skill

Bind MCP

by LeoYeAI in LeoYeAI/openclaw-master-skills

Bind Protocol MCP server for credential verification, policy authoring, and zero-knowledge proof generation.

MITAuto-check passedAgent Workflows

Install Bind MCP

skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill bind-mcp -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LeoYeAI/openclaw-master-skills bind-mcp --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/bind-protocol-mcp .claude/skills/bind-mcp && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
bind-mcp
GitHub stars
2.2k
Token cost
~4.5k tokens
SKILL.md length
1,574 words
Files
2
Skills in repo
972
Repo updated
First seen
Licence
MIT

At a glance

Bind Protocol MCP server for credential verification, policy authoring, and zero-knowledge proof generation.

  • Works in 4 steps: Sign in at… → Navigate to Settings > Agent Keys → Select which tool categories the key can… → …
  • Tasks that involve MCP servers
  • SKILL.md covers Prerequisites & Installation, Architecture & Data Flow, Tool Inventory and Workflow 1: Full Credential…, plus 7 more sections
  • Reaches api.bindprotocol.xyz; needs BIND_API_KEY

What it does

Bind MCP is an agent skill from LeoYeAI/openclaw-master-skills. Bind Protocol MCP server for credential verification, policy authoring, and zero-knowledge proof generation.

Its SKILL.md is about 4.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `_meta.json`).

It sits in Agent Workflows, covering MCP servers and Cryptography. It works with Model Context Protocol. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.

When your agent uses it

  • Tasks that involve MCP servers
  • Tasks that involve Cryptography

Example prompts

  • “/bind-mcp”

Requirements

  • Node.js
  • A credential in BIND_API_KEY

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Sign in at https://dashboard.bindprotocol.xyz
  2. Navigate to Settings > Agent Keys
  3. Select which tool categories the key can access (e.g., credential verification only, or policy authoring + verification)
  4. Copy the key — it is shown only once

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are json).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • api.bindprotocol.xyz

    Also links to:

    • dashboard.bindprotocol.xyz

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • BIND_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Bind MCP loads about 4.5k tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 1,574 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~29
When it runs · the whole SKILL.md, loaded when a task matches
~4.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,574 words, ~4,508 tokens.

Download SKILL.mdSave it as .claude/skills/bind-mcp/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
bind-mcp
description
Bind Protocol MCP server for credential verification, policy authoring, and zero-knowledge proof generation.
version
2.0.0

Bind MCP Server — Agent Skill Guide

You have access to the Bind Protocol MCP server. This document teaches you how to use it.

Prerequisites & Installation

Requirements
  • Node.js >= 18 — Required to run the server (npx handles package installation automatically)
  • Bind account — Required for API-backed tools. Create one at https://dashboard.bindprotocol.xyz
  • Agent key (idbr_agent_...) — Required for API-backed tools. Regular API keys (idbr_) are not supported for MCP.
Credential Setup

Bind uses agent keys for MCP authentication. Agent keys are scoped API keys that let org admins control exactly which tools are available, set daily rate limits, and get audit logs.

Key typeFormatMCP supported
Agent keyidbr_agent_<keyId>_<secret>Yes — required for API-backed tools
Regular API keyidbr_<keyId>_<secret>No — rejected by MCP server

To create an agent key:

  1. Sign in at https://dashboard.bindprotocol.xyz
  2. Navigate to Settings > Agent Keys
  3. Select which tool categories the key can access (e.g., credential verification only, or policy authoring + verification)
  4. Copy the key — it is shown only once
MCP Server Configuration

Add the server to your MCP client configuration. The exact file depends on your tool:

ToolConfig file
Claude Code.mcp.json in your project root, or ~/.claude/claude_desktop_config.json
Claude DesktopSettings > Developer > Edit Config
Cursor.cursor/mcp.json in your project root
WindsurfMCP settings

Configuration JSON:

json
{
  "mcpServers": {
    "bind": {
      "command": "npx",
      "args": ["@bind-protocol/mcp-server"],
      "env": {
        "BIND_API_KEY": "${BIND_API_KEY}"
      }
    }
  }
}

The BIND_API_KEY environment variable must be set in your shell to your agent key before launching your AI tool. Never hardcode the key directly in config files — always use environment variable references to avoid accidental credential leakage in shared configs or repositories.

Environment variables:

VariableRequiredDefaultDescription
BIND_API_KEYFor API-backed tools—Agent key (idbr_agent_...). Without this, only local tools are available.
BIND_API_URLNohttps://api.bindprotocol.xyzBase URL for API calls
BIND_RECEIPTS_PATHNo~/.bind/receiptsDirectory for receipt chain data
LOG_LEVELNoinfoLogging verbosity (debug, info, warn, error)
Verifying the Setup

If you do not have bind tools available, prompt the user to complete the setup above. You can test connectivity by calling bind_whoami — if it returns org info, the agent key is authenticated. Without a BIND_API_KEY, only local tools (parse, verify, hash) are available.


Architecture & Data Flow

The server runs locally via npx and communicates with your AI tool over stdio. It provides both local tools (always available) and API-backed tools (require an agent key). You just call the tool by name — routing is handled automatically.

Tool typeAuthPurpose
Local toolsNoneParse, verify, and hash VC-JWTs on-device
API-backed toolsAgent key via BIND_API_KEYPolicies, proofs, issuers, revocation, and more
What stays local vs. what calls the API

This is critical for understanding the privacy model:

Local tools (credential data NEVER leaves the machine):

  • bind_parse_credential — Decodes the JWT entirely on your machine
  • bind_verify_credential — Fetches the issuer's public JWKS from the Bind API (public keys only), then verifies the signature locally. The credential itself is never sent.
  • bind_hash_credential — Computes a SHA-256 hash locally. Only the irreversible hash is used for revocation checks.

API-backed tools (send requests to api.bindprotocol.xyz):

  • bind_check_revocation — Sends only the credential hash (not the credential). The hash is not reversible.
  • bind_resolve_issuer — Fetches public keys for an org. No credential data involved.
  • bind_explain_policy, bind_list_policies, bind_list_circuits — Read-only public metadata. No credential data involved.
  • bind_submit_prove_job — Sends circuit inputs to the Bind proving service. These are the raw values being proven (e.g., income amount, mileage count).
  • bind_issue_credential — Requests the Bind API to sign and issue a VC-JWT from a completed proof.
  • bind_create_policy, bind_validate_policy — Sends policy spec JSON to Bind for validation/storage.
  • bind_share_proof — Shares a proof record with a verifier org via the Bind API.

In short: Raw credentials are local-only. Hashes, policy specs, proof inputs, and metadata go to the API.


Tool Inventory

Local Tools (no auth required, credential data stays on-machine)
ToolWhat it does
bind_parse_credentialDecode a VC-JWT into header + payload + signature without verification
bind_verify_credentialFull verification: parse, fetch issuer JWKS, verify ES256 signature, check expiration. Does NOT check revocation.
bind_hash_credentialSHA-256 hash a VC-JWT. Use the hash with bind_check_revocation.
API-Backed Tools (require agent key via BIND_API_KEY)

Discovery & Inspection

ToolWhat it does
bind_resolve_issuerFetch an org's public signing keys (JWKS) by org ID
bind_explain_policyGet the public spec for a policy by policy ID
bind_check_revocationCheck if a credential is revoked by its hash (hash only — not the credential)
bind_list_policiesList available policies (supports limit/offset pagination)
bind_list_circuitsList available ZK circuits

Proof Generation & Credential Issuance

ToolWhat it does
bind_submit_prove_jobSubmit a ZK proof generation job with circuit ID and inputs
bind_get_prove_jobPoll a prove job's status by job ID
bind_list_prove_jobsList prove jobs, optionally filtered by status
bind_issue_credentialIssue a verifiable credential from a completed prove job
bind_share_proofShare a completed proof with a verifier org
bind_list_shared_proofsList proofs shared with/by your org

Policy Authoring

ToolWhat it does
bind_whoamiGet authenticated org info, tier, policy limits, and agent key permissions
bind_validate_policyDry-run validation of a policy spec (catches errors before creation)
bind_create_policyCreate a new verification policy
bind_generate_circuitTrigger ZK circuit compilation for a saved policy
bind_get_circuit_statusPoll circuit compilation job status

Workflow 1: Full Credential Verification

When to use: A user gives you a VC-JWT string (starts with eyJ...) and wants to know if it's valid.

Steps:

  1. bind_parse_credential — Decode the JWT to inspect claims
  2. bind_verify_credential — Verify signature and expiration
  3. bind_hash_credential — Compute SHA-256 hash
  4. bind_check_revocation — Send the hash (not the credential) to check revocation

Steps 1 and 2 can be combined (verify includes parsing), but parsing first lets you show the user what the credential contains before the full check. Steps 1–3 run locally; step 4 sends only the hash to the API.

Important: bind_verify_credential does NOT check revocation. You must always follow up with hash + revocation check for a complete verification.

parse → verify → hash → check_revocation
Show full SKILL.md (637 more words)Show less

Workflow 2: Investigate an Issuer

When to use: A user wants to know about an organization's keys or policies.

  1. bind_resolve_issuer(orgId) — Fetch their JWKS
  2. bind_list_policies or bind_explain_policy — Look up their policies

Workflow 3: Create a Policy

When to use: A user wants to define a new verification policy.

Steps:

  1. bind_whoami — Check org name, tier, and limits. You need the org name for the namespace.
  2. Build the policy spec (see Policy Spec Reference below)
  3. bind_validate_policy — Dry-run to catch errors before creation
  4. Fix any validation errors and re-validate
  5. bind_create_policy — Save the policy
  6. bind_generate_circuit — Queue ZK circuit compilation
  7. bind_get_circuit_status — Poll until status is completed or failed

Critical rules:

  • metadata.namespace MUST start with your org's slugified name (from bind_whoami). The namespaces bind and system are reserved.
  • The policy id MUST start with the namespace (e.g., acme.finance.creditCheck for namespace acme).
  • ALWAYS validate before creating. Fix all errors first.
  • String inputs MUST have an encoding block mapping values to numbers (ZK circuits only work with numbers).

Workflow 4: Generate a Proof and Issue a Credential

When to use: A user wants to generate a ZK proof and get a verifiable credential.

  1. bind_list_policies or bind_explain_policy — Find the right policy/circuit
  2. bind_submit_prove_job(circuitId, inputs) — Submit the proof job
  3. bind_get_prove_job(jobId) — Poll until status is completed
  4. bind_issue_credential(proveJobId) — Issue the VC from the completed proof
  5. Optionally: bind_share_proof(proveJobId, verifierOrgId) — Share with a verifier

Policy Spec Reference

A policy is a JSON object with this structure. All fields shown are required unless marked optional.

json
{
  "id": "<namespace>.<category>.<name>",
  "version": "0.1.0",
  "metadata": {
    "title": "Human-readable title",
    "description": "What this policy verifies",
    "category": "finance|mobility|identity|demo",
    "namespace": "your-org-name"
  },
  "subject": {
    "type": "individual|organization|vehicle|device",
    "identifier": "wallet_address|did|vin|vehicleTokenId"
  },

  "inputs": [
    {
      "id": "input_name",
      "source": { "kind": "static|api", "api": "optional_api_name" },
      "signal": "input_name",
      "valueType": "number|boolean|string",
      "unit": "USD|count|months",
      "time": { "mode": "point|range|relative", "lookback": "30d" },
      "aggregation": { "op": "latest|sum|mean|count" },
      "encoding": {
        "type": "enum",
        "values": { "label1": 1, "label2": 2 }
      }
    }
  ],

  "rules": [
    {
      "id": "rule_name",
      "description": "Human-readable description",
      "assert": { /* expression — see below */ },
      "severity": "fail|warn|info"
    }
  ],

  "evaluation": {
    "kind": "PASS_FAIL|SCORE",
    "scoreRange": { "min": 0, "max": 100 },
    "baseline": 50,
    "contributions": [
      { "ruleId": "rule_name", "points": 30, "whenPasses": true }
    ]
  },

  "outputs": [
    {
      "name": "output_name",
      "type": "boolean|enum|number",
      "derive": {
        "kind": "PASS_FAIL|SCORE|BAND|CONST",
        "from": "SCORE|input_id",
        "bands": [
          { "label": "LOW", "minInclusive": 0, "maxExclusive": 40 },
          { "label": "HIGH", "minInclusive": 40, "maxExclusive": 101 }
        ],
        "value": 42
      },
      "disclosed": true
    }
  ],

  "validity": { "ttl": "P30D" },
  "disclosure": {
    "default": "SELECTIVE",
    "exposeClaims": ["output_name"]
  },

  "proving": {
    "circuitId": "<namespace>.<name>.v<version>",
    "inputTypes": { "input_name": "u32" },
    "outputType": "u8"
  }
}
Expression Types (used in rules[].assert)
TypeShapeExample
ref{ "type": "ref", "inputId": "<input_id>" }Reference an input value
const{ "type": "const", "value": <number|boolean> }Literal number or boolean (never strings)
cmp{ "type": "cmp", "cmp": ">=|<=|>|<|==|!=", "left": <expr>, "right": <expr> }Comparison
op{ "type": "op", "op": "+|-|*|/", "args": [<expr>, ...] }Arithmetic
and{ "type": "and", "args": [<expr>, ...] }Logical AND
or{ "type": "or", "args": [<expr>, ...] }Logical OR
not{ "type": "not", "arg": <expr> }Logical NOT

Field name gotchas:

  • Use "inputId" in ref expressions, NOT "path"
  • Use "cmp" for the comparison operator, NOT "operator"
  • Use "args" for operand lists, NOT "children"
  • Use "arg" (singular) for not, NOT "expr"
  • const values must be numbers or booleans, never strings
Evaluation Kinds

PASS_FAIL: All severity: "fail" rules must pass. No scoring.

SCORE: Starts at baseline, adds/subtracts points from rule contributions.

json
{
  "kind": "SCORE",
  "scoreRange": { "min": 0, "max": 100 },
  "baseline": 50,
  "contributions": [
    { "ruleId": "has_high_income", "points": 25, "whenPasses": true },
    { "ruleId": "has_delinquencies", "points": -20, "whenPasses": true }
  ]
}
Output Derive Kinds
KindUse forRequired fields
PASS_FAILBoolean pass/fail from evaluationNone
SCORERaw numeric scorefrom: "SCORE"
BANDMap score to labeled bandsfrom: "SCORE", bands array
CONSTFixed valuevalue
Working with String Inputs

ZK circuits only work with numbers. When a policy uses string inputs (employer names, country codes, etc.), you MUST include an encoding block:

json
{
  "id": "employer",
  "source": { "kind": "static" },
  "signal": "employer",
  "valueType": "string",
  "encoding": {
    "type": "enum",
    "values": {
      "Acme Corp": 1,
      "Globex Inc": 2,
      "Initech": 3
    }
  }
}
Proving Section

The proving section maps inputs to Noir types for the ZK circuit:

json
{
  "proving": {
    "circuitId": "acme.safe_driver.v0_1_0",
    "inputTypes": {
      "miles_driven": "u32",
      "hard_brake_pct": "u8",
      "is_commercial": "bool"
    },
    "outputType": "u8"
  }
}

Available Noir types: u8, u16, u32, u64, i8, i16, i32, i64, bool, Field


Tier Restrictions

Policy authoring is gated by organization tier. Always call bind_whoami first to check limits.

TierCan Create PoliciesNotes
BasicNoVerification only
PremiumYesLimited inputs/rules/outputs
ScaleYesExpanded limits, can create extractors
EnterpriseYesUnlimited
VerifierNoCannot create proofs or policies

Common Errors and Fixes

ErrorCauseFix
NAMESPACE_MISMATCHPolicy namespace doesn't match your orgUse your org name from bind_whoami as the namespace prefix
TIER_LIMIT_EXCEEDEDYour tier doesn't allow this operationCheck bind_whoami for limits
INVALID_EXPRESSIONMalformed rule assertionCheck expression field names (inputId, cmp, args, arg)
MISSING_ENCODINGString input without encodingAdd encoding.type: "enum" with values map
CIRCUIT_COMPILATION_FAILEDCircuit couldn't compileCheck the error in bind_get_circuit_status, fix the policy, recreate, and regenerate

Example: Complete Policy Creation

Here is a complete example of creating a credit score policy for org acme:

json
{
  "id": "acme.finance.credit-check",
  "version": "0.1.0",
  "metadata": {
    "title": "Credit Eligibility Check",
    "description": "Evaluates creditworthiness based on income and debt ratio",
    "category": "finance",
    "namespace": "acme"
  },
  "subject": {
    "type": "individual",
    "identifier": "wallet_address"
  },
  "inputs": [
    {
      "id": "annual_income",
      "source": { "kind": "static" },
      "signal": "annual_income",
      "valueType": "number",
      "unit": "USD"
    },
    {
      "id": "debt_ratio",
      "source": { "kind": "static" },
      "signal": "debt_ratio",
      "valueType": "number",
      "unit": "percent"
    }
  ],
  "rules": [
    {
      "id": "min_income",
      "description": "Annual income must be at least $30,000",
      "assert": {
        "type": "cmp",
        "cmp": ">=",
        "left": { "type": "ref", "inputId": "annual_income" },
        "right": { "type": "const", "value": 30000 }
      },
      "severity": "fail"
    },
    {
      "id": "max_debt_ratio",
      "description": "Debt-to-income ratio must be under 40%",
      "assert": {
        "type": "cmp",
        "cmp": "<",
        "left": { "type": "ref", "inputId": "debt_ratio" },
        "right": { "type": "const", "value": 40 }
      },
      "severity": "fail"
    }
  ],
  "evaluation": {
    "kind": "PASS_FAIL"
  },
  "outputs": [
    {
      "name": "eligible",
      "type": "boolean",
      "derive": { "kind": "PASS_FAIL" },
      "disclosed": true
    }
  ],
  "validity": { "ttl": "P30D" },
  "disclosure": {
    "default": "SELECTIVE",
    "exposeClaims": ["eligible"]
  },
  "proving": {
    "circuitId": "acme.credit_check.v0_1_0",
    "inputTypes": {
      "annual_income": "u32",
      "debt_ratio": "u8"
    },
    "outputType": "u8"
  }
}

Agent workflow for this:

  1. bind_whoami — Confirm org is acme and tier allows policy creation
  2. bind_validate_policy(policy) — Dry-run validation
  3. bind_create_policy(policy) — Create the policy
  4. bind_generate_circuit("acme.finance.credit-check") — Compile the circuit
  5. bind_get_circuit_status(jobId) — Poll until complete

© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/bind-protocol-mcp of LeoYeAI/openclaw-master-skills.

  • SKILL.md
  • _meta.json

Open the folder on GitHubat commit e5199b5

Compare with similar skills

Bind MCP next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Bind MCP compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bind MCP this skillLeoYeAI/openclaw-master-skills2.2k—~4.5kAutomated safety check: PassMIT
X Use Setupihuzaifashoukat/x-use171—~731Automated safety check: WarnMIT
Protect MCP Setupwshobson/agents40k—~2.1kAutomated safety check: PassMIT
Webcrypt MCPputervision/state-memory-mcp111—~847Automated safety check: PassMIT
MCP Server Builderanthropics/skills180k64 repos~2.3kAutomated safety check: PassApache-2.0
MCP Server BuildershareAI-lab/learn-claude-code78k5 repos~1.2kAutomated safety check: PassMIT

Similar skills

  • X Use Setup

    ihuzaifashoukat/x-use

    Zero-knowledge onboarding for x-use that verifies the install, registers the MCP server, then interviews the user to configure their first X account (cookies, niche, keywords, persona).

    171 GitHub stars~731 tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check: warnings
  • Protect MCP Setup

    wshobson/agents

    Configure Cedar policy enforcement and Ed25519 signed receipts for Claude Code tool calls.

    40k GitHub stars~2.1k tokensUpdated 3 days ago
    Agent WorkflowsAuto-check passed
  • Webcrypt MCP

    putervision/state-memory-mcp

    Teaches the agent to use the WebCrypt MCP server for AES-256-GCM symmetric encryption, RSA-4096 hybrid encryption, key generation, digital signatures, hashing, and post-quantum cryptography.

    111 GitHub stars~847 tokensUpdated 5 days ago
    SecurityAuto-check passed
  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 64 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • MCP Server Builder

    shareAI-lab/learn-claude-code

    Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.

    78k GitHub starsUsed in 5 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    38k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed

More from LeoYeAI/openclaw-master-skills

All 972 skills in this repo
  • DevOps Pipeline Management

    LeoYeAI/openclaw-master-skills

    Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.

    2.2k GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check: notes
  • Feishu Document Collaboration

    LeoYeAI/openclaw-master-skills

    Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.

    2.2k GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed
  • Files Memory System

    LeoYeAI/openclaw-master-skills

    Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.

    2.2k GitHub stars~3.8k tokensUpdated 2 mo ago
    Auto-check passed
  • GEO-Claw AI Visibility Agent

    LeoYeAI/openclaw-master-skills

    Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed
  • Google Workspace CLI

    LeoYeAI/openclaw-master-skills

    Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.

    2.2k GitHub stars~2.6k tokensUpdated 2 mo ago
    Auto-check: notes
  • HealthFit Health Advisors

    LeoYeAI/openclaw-master-skills

    Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.

    2.2k GitHub stars~4.4k tokensUpdated 2 mo ago
    Auto-check passed

Categories

Questions about Bind MCP

What does Bind MCP do?

Bind Protocol MCP server for credential verification, policy authoring, and zero-knowledge proof generation. Bind MCP is an agent skill from LeoYeAI/openclaw-master-skills. Bind Protocol MCP server for credential verification, policy authoring, and zero-knowledge proof generation.

When should I use Bind MCP?

Bind MCP fits situations like: tasks that involve MCP servers; tasks that involve Cryptography.

How do I install Bind MCP in Claude Code?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill bind-mcp -a claude-code`. Or copy the skill folder (skills/bind-protocol-mcp in LeoYeAI/openclaw-master-skills) into .claude/skills/bind-mcp in your project. Claude Code loads it when a task matches its description.

How do I install Bind MCP in Codex?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill bind-mcp -a codex`. Or copy the skill folder (skills/bind-protocol-mcp in LeoYeAI/openclaw-master-skills) into .agents/skills/bind-mcp in your project. Codex loads it when a task matches its description.

Can I use Bind MCP in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill bind-mcp -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bind-mcp, .gemini/skills/bind-mcp, .github/skills/bind-mcp and .opencode/skills/bind-mcp in your project.

What does Bind MCP need to run?

Going by SKILL.md and its folder, Bind MCP needs credentials named BIND_API_KEY. Our summary lists: Node.js; A credential in BIND_API_KEY.

Does Bind MCP access the network?

SKILL.md names 2 domains. In commands or code: api.bindprotocol.xyz; the agent is likely to contact it when it follows the instructions. As links in the text: dashboard.bindprotocol.xyz. This is read from the text; nothing was executed.

Is Bind MCP safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Bind MCP use?

Bind MCP is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Bind MCP use?

About 4.5k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Bind MCP?

Skills that share tags, products or a category with Bind MCP: X Use Setup (ihuzaifashoukat/x-use, 171 stars), Protect MCP Setup (wshobson/agents, 40k stars), Webcrypt MCP (putervision/state-memory-mcp, 111 stars) and MCP Server Builder (anthropics/skills, 180k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bind MCP?

LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,159 GitHub stars. The repository holds 972 skills in this directory. The repository was last updated on July 20, 2026.

Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.