@bind-protocol/mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log verbosity (fatal, error, warn, info, debug, trace). | info |
| BIND_API_URL | No | Bind Protocol API endpoint used to fetch issuer JWKS. | https://api.bindprotocol.xyz |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| 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. |
| bind_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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.