Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
bind-protocol-mcp 1.0.2 Changelog - Updated documentation to reflect a unified MCP server (local and remote servers are now a single local server with API access). - Now requires an Agent key (`idbr_agent_...`) via the `BIND_API_KEY` environment variable for API-backed tools; regular API keys are no longer supported for MCP. - Clarified privacy model: all credential data remains local; only hashes, policy specs, proof inputs, and metadata are sent to the API. - Simplified setup instructions; the user configures only one server instance in their MCP client. - Expanded environment variable support and documented optional configuration paths and logging. - Tool inventory and workflow sections updated for clarity and alignment with new API key requirements and architecture.
What This Skill Does
Bind Protocol MCP server for working with verifiable credentials (VC-JWTs). Supports on-device credential parsing and signature verification, plus API-backed tools for zero-knowledge proof generation, policy authoring, and revocation checks. Credential data never leaves the machine; only hashes and proof inputs are sent to the Bind API.
Raw credential contents stay local during verification — only an irreversible SHA-256 hash is sent for revocation checks, which is a stronger privacy guarantee than sending credentials to a remote validator.
When to use it
- Verify a VC-JWT credential before granting a user access to a resource
- Check whether a previously issued credential has been revoked
- Create and compile a ZK verification policy for income or identity checks
- Generate a zero-knowledge proof and issue a verifiable credential from it
- Inspect an organization's public signing keys and available policies
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: verify this VC-JWT and tell me if it's still valid
- 1Call bind_parse_credential to decode the JWT and display the claims to the user
- 2Call bind_verify_credential to check the ES256 signature and expiration against the issuer's public JWKS
- 3Call bind_hash_credential to compute a SHA-256 hash of the credential
- 4Call bind_check_revocation with the hash to confirm the credential has not been revoked
Credential is valid: signature verified, not expired, not revoked. Claims: {subject, issuer, expiry, ...}
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.