Dock Certs

@dock-certs list all active API keys for our account and show me which ones have IP restrictions configured

Found 4 API keys for your Dock Certs account. Two keys have IP allowlists: 'Production API' (restricted to 203.0.113.0/24) created March 2024, and 'Staging Access' (restricted to 198.51.100.42) created January 2024. Two keys have no IP restrictions: 'Development Key' and 'CI Pipeline Key', both created in February 2024. The production key was last used 2 hours ago; the staging key hasn't been accessed in 14 days.

This example shows the MCP's read capability for API key management. Requires an API key with admin scope to list all keys. The response structure depends on what metadata Dock Certs returns — some accounts may see additional fields like usage timestamps or permission levels.

@dock-certs create a new webhook that sends credential issuance events to https://our-app.example.com/webhooks/dock and include the credential payload in each notification

Created webhook endpoint with ID 'wh_8x3k9m2p'. Dock Certs will now POST to https://our-app.example.com/webhooks/dock whenever a credential is issued. Events include: credential.created, credential.issued, credential.revoked. Each payload contains the full credential JSON. Your endpoint must respond with 200 OK within 10 seconds or Dock will retry up to 3 times with exponential backoff. Webhook secret for signature verification: whsec_7j4n2k8m (store this securely).

Demonstrates the MCP's write capability for event subscriptions. This action has side-effects: your endpoint will immediately start receiving POST requests from Dock's servers. Ensure your webhook URL is publicly accessible and can handle Dock's retry logic. You'll need to implement signature verification using the provided secret.

@dock-certs review all credentials we've issued in the last 30 days and flag any that are missing a 'department' tag so we can audit our tagging compliance

Analyzed 47 credentials issued since December 15. Found 12 credentials without a 'department' tag: 8 employee verification credentials (IDs: cred_4k2m, cred_5n8p, cred_7j3q, cred_9r2s, cred_1t4u, cred_3v6w, cred_5x8y, cred_7z1a), 3 contractor certifications (cred_2b4c, cred_6d8e, cred_9f1g), and 1 training completion badge (cred_4h6i). All 12 were issued by API key 'HR Automation' between Dec 18-22. The remaining 35 credentials have proper department tags: 22 tagged 'Engineering', 9 tagged 'Sales', 4 tagged 'Operations'.

Shows how the MCP pairs with AI reasoning to audit credential metadata. This requires the MCP to fetch credential lists and the AI to filter/categorize results. Dock Certs may paginate large result sets, so the actual query might involve multiple API calls. Tagging schemas are account-specific — your 'department' tag may not exist or may use different values.

When Dock Certs works for audit-ready credential tracking

A 6-person compliance team at a healthcare SaaS company issues verifiable credentials to contractors after security training. They need an audit trail showing who issued what, when, and whether credentials were revoked. Dock Certs wins here because the 15 tools cover the full lifecycle: create, retrieve, delete credentials, plus webhook subscriptions for real-time revocation alerts. The API key management tools let you rotate keys quarterly without breaking integrations. The threshold: if you're issuing fewer than 50 credentials per month, the setup overhead (learning verifiable credential schemas, configuring webhooks) might outweigh the benefit. But once you hit that volume, the audit log alone justifies the integration. Use this when credential provenance matters more than speed.

Dock Certs for multi-org credential exchange at scale

A 12-person partner ops team at an ed-tech platform issues completion badges to learners across 40 partner organizations. Each partner needs to verify badges without calling the platform's API every time. Dock Certs handles this because verifiable credentials are cryptographically signed—partners verify locally, no live lookup required. The webhook tools let you push revocation events when a learner disputes a badge. The tag tools help you segment credentials by cohort or partner. The catch: if your partners aren't set up to verify W3C credentials, you'll spend weeks on integration support. This MCP is the right call when your partners already speak the verifiable credential standard, or when you're willing to invest in that education upfront. Otherwise, stick with a simpler badge API.

When Dock Certs' key management justifies the integration

A 3-person security team at a fintech startup rotates API keys monthly across 8 internal services. They need programmatic key creation, retrieval, and deletion without touching the Dock dashboard. The Create API Key, Retrieve API Key, and Delete API Key tools let them script the rotation in a GitHub Action. The IP allowlist parameter means they can lock keys to specific service IPs. The trade-off: if you're only using Dock Certs for key management and not issuing credentials, you're paying for 12 unused tools. This scenario works when you're already committed to Dock for credential issuance and need the key rotation as a side benefit. If key management is your only need, a secrets manager like Vault is cheaper and more focused.