legitify-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LEGITIFY_API_KEY | No | API key for authentication (optional) | |
| LEGITIFY_BASE_URL | No | API base URL (optional, future use) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| legitify.submit_attestation_requestB | Submit a request for human attestation (approval receipt). Returns attestation_request_id and status=pending. |
| legitify.get_attestation_statusB | Get status for an attestation_request_id (MVP: pending unless manually processed). |
| legitify.get_policyA | Get default policy info (caps, required evidence expectations). |
| legitify.list_pending_requestsC | List pending attestation requests (from local queue). |
| legitify.review_requestB | Write a human attestation receipt for an existing attestation_request_id (approved/denied/needs_info). |
| legitify.get_pending_request_detailsA | Fetch full details for a pending request by id (including evidence). |
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 6 tools
Most tools have clear boundaries: submit, review, list, and policy are distinct. get_attestation_status and get_pending_request_details both retrieve information by id, but the descriptions separate status lookup from full details reasonably well.
All tool names use a lowercase snake_case verb_noun pattern, which is consistent. Minor inconsistency exists between attestation_request, pending_request, and request as object names, but the verb pattern keeps the set predictable.
Six tools is well-scoped for an attestation workflow. Each tool maps to a meaningful step in the request lifecycle without unnecessary duplication.
The core submit, review, status, list, and detail flows are covered. Missing capabilities like canceling a request or resubmitting after needs_info are notable but not fatal, since the main workflow is fully represented.