FPE Demo FAQs

Question 1

What authentication modes are available with FPE Demo?

Accepted Answer

FPE Demo supports multiple authentication modes: `authless` for quick tests, `debug`, `test` (using a shared secret or JWT), and `production` (using JWT only) to cater to various security requirements and environments.

Question 2

What is FPE Demo and its primary use case?

Accepted Answer

FPE Demo is a lightweight MCP (Model Context Protocol) server that demonstrates secure FF3 format-preserving encryption (radix-10) and multi-mode authentication for sensitive data within LLM interactions. It's ideal for learning, prototyping, and securely integrating external tools with LLMs.

Question 3

What type of encryption does FPE Demo use?

Accepted Answer

It utilizes FF3 (Format-Preserving Encryption) over radix-10 (digits only), meaning it encrypts numeric strings while preserving their original length and format, which is crucial for sensitive identifiers like SSNs or phone numbers.

Question 4

Why do encrypted values include the `ENC_FPE:` prefix?

Accepted Answer

The `ENC_FPE:` prefix is a visual aid for demonstration and learning purposes. It makes it explicitly clear in logs or demos that a particular value has been encrypted. In a real-world production system, this prefix would typically be omitted.

Question 5

How does FPE Demo integrate with LLMs and other tools?

Accepted Answer

It integrates via the Model Context Protocol (MCP), supporting both stdio (for local LLM clients like Claude Desktop) and HTTP transports (for web-based LLMs or remote server integrations). It exposes `fpe_encrypt` and `fpe_decrypt` tools.

FPE Demo

About

Key Features

Use Cases