@bind-protocol/mcp-server
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@bind-protocol/mcp-server Parse the VC-JWT from my last message."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
━━━╸ 888888b. 8888888888b 8888888888b.
━━━━━╸ 888 "88b 888 8888b 888888 "Y88b
━━━━━━━╸ 888 .88P 888 88888b 888888 888
━━━━━━━━━╸ 8888888K. 888 888Y88b 888888 888
━━━━━━━━━━━╸ 888 "Y88b 888 888 Y88b888888 888
━━━━━━━━━━━━━╸ 888 888 888 888 Y88888888 888
━━━━━━━━━━━━━━━╸ 888 d88P 888 888 Y8888888 .d88P
━━━━━━━━━━━━━━━━━╸ 8888888P"8888888888 Y8888888888P"
P R O T O C O L@bind-protocol/mcp-server
Local MCP server for Bind Protocol — credential parsing, verification, and hashing tools for AI agents.
Overview
This MCP (Model Context Protocol) server enables AI agents to work with Bind Protocol Verifiable Credentials (VC-JWTs). It provides tools to decode, cryptographically verify, and hash credentials without requiring direct access to keys or the Bind Protocol API.
Related MCP server: aip-identity
Tools
Tool | Description |
| Decode a VC-JWT into its header, payload, and signature without verifying the signature. |
| Parse a VC-JWT, fetch the issuer's JWKS, verify the ES256 signature, and check expiration. Does not check revocation. |
| Compute the SHA-256 hash of a VC-JWT (for use with |
Installation
npm install @bind-protocol/mcp-serverOr clone and build from source:
git clone <repo-url>
cd mcp-server
npm install
npm run buildRequirements
Node.js >= 18.0.0
Configuration
Add the server to your MCP client config. For Claude Desktop, edit claude_desktop_config.json:
{
"mcpServers": {
"bind-protocol": {
"command": "npx",
"args": ["@bind-protocol/mcp-server"]
}
}
}Or point directly to the built binary:
{
"mcpServers": {
"bind-protocol": {
"command": "bind-mcp-server"
}
}
}Environment variables
Variable | Default | Description |
|
| Bind Protocol API endpoint used to fetch issuer JWKS. |
|
| Log verbosity ( |
Development
npm run dev # Build in watch mode
npm run build # Production build
npm run typecheck # Type-check without emitting
npm run test # Run tests
npm run test:watch # Run tests in watch modeLicense
MIT
mcp-server
Available Tools
3 toolsbind_hash_credentialA
Compute the SHA-256 hash of a VC-JWT. The resulting hash can be passed to bind_check_revocation to check revocation status.
Inputs: jwt (required).
bind_parse_credentialA
Decode a Bind Protocol VC-JWT into its header, payload, and signature without verifying the signature. Use this to inspect a credential before verification.
Inputs: jwt (required).
bind_verify_credentialA
Verify a Bind Protocol VC-JWT: parse the JWT, fetch the issuer JWKS, verify the ES256 signature, and check expiration. Does NOT check revocation status — use bind_check_revocation separately for that. Returns the verified claims on success.
Inputs: jwt (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool serves a distinct purpose: bind_verify_credential performs full signature verification, bind_hash_credential computes a hash for revocation lookup, and bind_parse_credential decodes without verification. There is no overlap or ambiguity between these actions.
All tool names follow a consistent 'bind_verb_noun' pattern: bind_verify_credential, bind_hash_credential, bind_parse_credential. The prefix and verb ordering are uniform, making the set predictable and easy to navigate.
The server has only 3 tools, each focused on a specific credential operation (verify, hash, parse). This is a well-scoped set for a credential utility, falling within the typical 3-15 tool range and avoiding redundancy.
The tools cover parsing, hashing, and verification, but verification explicitly does not check revocation and relies on a separate 'bind_check_revocation' tool that is not included. This creates a notable gap in the credential validation workflow, as the hash tool is only useful if the revocation check is available elsewhere.
Maintenance
Related MCP Connectors
MCP server for the Z1N Protocol - on-chain identity for AI agents on Polygon
MCP server bridging holepunchto/keet-identity-key to the Hive agentic identity network
MCP server for OnceAsk, the AI-native current-address layer for people and agents.
MCP server for Boson Protocol — on-chain agentic commerce for physical & digital goods.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA lightweight, fast MCP server that provides onchain capabilities for the LLMs and Agents.37 npm255MIT
- AlicenseAqualityDmaintenanceMCP server for AI agent identity — verify agents with Ed25519 signatures, check trust scores, sign and verify content, exchange encrypted messages. Built on the Agent Identity Protocol (AIP).81MIT
- AlicenseAqualityCmaintenanceLocal-first MCP server for per-agent key management, generating and using signing keys without external KMS.841 npm1MIT
- AlicenseNot gradedqualityDmaintenanceMCP Server for AI agent identity and authorization. Create, verify, and manage agent identities with trust scores and scoped authorization tokens.48 PyPIMIT