Empeiria Documentation
  • Getting Started
    • Welcome to Empeiria
    • 5 minutes Quickstart
    • Tutorial: Credential Issuance & Verification
      • Overview
      • Understanding Key Concepts
      • Project Setup
      • Deploying the Issuer
      • Uploading the Credential Schema
      • Issuing Credentials
      • Frontend for Credential Issuance
      • Testing Credential Issuance
      • Deploying the Verifier
      • Setting Up the Verification Flow
      • Creating a Verification Endpoint
      • Creating a Protected Dashboard
      • Testing the Verification Flow
      • Summary & Next Steps
  • Understand
    • EVDI Architecture
    • Self-Sovereign Identity
      • Technical Foundations
      • Roles in the SSI framework
      • Protocols and Standards
  • Develop
    • One-click deployment
      • Introduction
      • Registration
      • Login
      • Creating an Issuer
      • Issuer Data Description
      • Creating a Verifier
      • Verifier Data Description
    • Issuer
      • Terminology and Concepts
      • DID Document Management
      • Schema Management
      • Issuing Credentials and Interacting With Wallets
      • Revocations
      • Security Considerations
      • Error Handling and Troubleshooting
      • Future Enhancements
      • References and Standards
      • MCP Server Integration
      • FAQ
      • API Reference
        • Token
        • Schema
        • Offering
        • Metadata
        • Credential
        • Blockchain
        • Authorization
    • Verifier
      • Terminology and Concepts
      • Architecture Overview
      • Core Responsibilities
      • Query Language
      • Client Configuration
      • Frontend Integration
      • Revocations
      • Server-Side VP Queries
      • Security Considerations
      • Error Handling and Troubleshooting
      • Future Enhancements
      • References and Standards
      • MCP Server Integration
      • FAQ
      • API Reference
        • VP Query
        • QR Code
        • Authorization
    • Wallet SDK (Coming soon)
    • Introduction to cosmwasm
  • Empe Blockchain
    • Overview
    • Chain Architecture
      • Auth
      • Authz
      • Bank
      • Distribution
      • Governance
      • Staking
      • IBC
      • DidDoc
      • Vesting
      • Minter
      • Stablefee
      • LinkedResources
    • Important links
    • Validators Guide
      • New validator
      • Hardware requirements
      • Required software installation
      • Go installation
      • Install prebuild binary
      • Install binary from source code (option B)
      • Configure a node
      • Cosmovisor setup
      • Install wasmvm
      • Sync with state-sync
      • Full state sync from archive snapshot
      • Latest snapshot
      • Run a Validator
      • Migration to v0.2.2
      • Migration to v0.3.0
      • Migration to v0.4.0
      • FAQ
  • User Guide
    • Empe DID Wallet
      • Intro
      • Download and first launch
      • Create or import did
      • Main screen overview
      • How to claim credential from issuer
      • How to use credential with verifier
      • Settings and other options
    • Keplr Wallet and Blockchain Operations
      • How to Connect Keplr Wallet
    • Ping Pub operation
    • Staking Tokens Guide
    • Voting on Governance Proposals Guide
    • Sending Tokens Guide
    • Airdrop
      • On-Chain Testnet Airdrop
      • Faucet Guide: How to Claim Testnet Tokens?
  • Appendix
    • Glossary
Powered by GitBook
On this page
  • What is MCP?
  • Available Verifier Operations
  • Verification Workflows
  • VP Query Management
  • Example Use Cases
  • Advanced Verification Examples
  • Real-Time Verification Flow
  • Setup Requirements
  • Configuration
  • Integration Benefits
  • Security Considerations
  • Workflow Integration
  1. Develop
  2. Verifier

MCP Server Integration

The Empe MCP Server enables AI systems like Claude to interact with the Verifier Service through natural language commands. This Model Context Protocol (MCP) server bridges conversational AI and verification operations, making credential verification accessible through simple prompts.

What is MCP?

MCP (Model Context Protocol) servers provide context, tools, and prompts to AI clients. They expose data sources like APIs and databases to make them accessible to AI systems. The Empe MCP server specifically focuses on Self-Sovereign Identity operations, including verification workflows.

Available Verifier Operations

The MCP server provides these verifier-related tools:

Verification Workflows

  • generate_verification_qr - Create QR codes for credential verification

  • generate_verification_qr_for_vp_query - Generate QR codes for specific VP query verification

  • check_verification_status - Monitor verification status in real-time

VP Query Management

  • create_vp_query - Create new Verifiable Presentation queries with complex logic

  • get_all_vp_queries - List all available VP queries in the system

  • get_vp_query_by_id - Retrieve specific VP query details

  • delete_vp_query - Remove unused VP queries

Example Use Cases

You can use natural language prompts like:

"Create a verification process that checks if someone has a valid driver's license 
and is over 21 years old."

"Generate a QR code to verify event tickets for the Annual Developer Conference."

"Set up verification that requires either a government ID or a membership card 
with Gold status."

"Check if anyone has scanned the verification QR code I generated earlier."

"Show me all the verification queries we have in the system."

Advanced Verification Examples

The MCP server supports complex verification logic:

"Create a verification that checks if someone has a MembershipCard credential 
with 'Gold' level that hasn't expired yet."

"I want to verify that someone has either a government ID showing they're over 21 
OR a driver's license with class A, B, or C."

"Set up age verification that accepts any credential type as long as the 
birthdate field shows the person is 18 or older."

Real-Time Verification Flow

The MCP server can manage complete verification workflows:

  1. Generate Verification Request: Create a QR code with specific requirements

  2. Monitor Status: Watch for users scanning the QR code

  3. Process Results: Handle successful or failed verifications

  4. Update Applications: Notify your systems of verification outcomes

Setup Requirements

Before using the MCP server with the Verifier Service:

  1. Deploy a Verifier Service via One-Click Deployment

  2. Configure external access (the verifier needs to be accessible from outside your network)

  3. Set up the MCP server with your verifier's endpoints and credentials

  4. Connect the MCP server to your AI client (like Claude)

Configuration

The MCP server requires these verifier-related environment variables:

VERIFIER_BASE_URL=https://your-verifier-instance.example.com
VERIFIER_CLIENT_URL=https://your-external-accessible-url.com
CLIENT_SECRET=your-verifier-client-secret
SSE_PORT=8080

For detailed setup instructions, see the MCP Server repository.

Integration Benefits

  • Rapid Verification Setup: Create complex verification logic through conversation

  • Dynamic Requirements: Modify verification criteria without code changes

  • Real-Time Monitoring: Track verification status through natural language queries

  • Testing and Debugging: Quickly test verification flows with different requirements

  • Business Logic Translation: Convert business requirements into technical VP queries

Security Considerations

When using the MCP server with production verifier services:

  • Use dedicated test environments for experimentation

  • Validate all AI-generated VP queries before production deployment

  • Monitor verification requests and results

  • Implement proper access controls for the MCP server

  • Ensure external verifier URLs use HTTPS and proper authentication

Workflow Integration

The MCP server can be integrated into larger workflows:

  1. Dynamic Access Control: Modify verification requirements based on context

  2. Event Management: Create time-limited verification flows for events

  3. Compliance Checking: Set up verification for regulatory requirements

  4. Multi-Step Verification: Chain multiple verification steps together

The MCP server makes credential verification more accessible while maintaining the security and standards compliance of the underlying Verifier Service.

PreviousReferences and StandardsNextFAQ

Last updated 2 days ago