Skip to main content
Glama

legitify-mcp

MCP server for Legitify (LegitimizeAI.com) — Human Attestation (Approval Receipts) for AI actions.

What this is

This server exposes MCP tools that let an agent:

  • submit an attestation request

  • check status

  • fetch policy/templates

Related MCP server: Cryptair MCP Server

Tools

  • legitify.submit_attestation_request

  • legitify.get_attestation_status

  • legitify.get_policy

  • legitify.list_pending_requests

  • legitify.get_pending_request_details

  • legitify.review_request

Quickstart (local)

cd projects/legitify-mcp
npm i
npm run dev

Configure in mcporter / OpenClaw

Add to your mcporter config (example):

{
  "mcpServers": {
    "legitify": {
      "command": "node /ABS/PATH/legitify-mcp/src/server.js"
    }
  }
}

Example calls

mcporter call --server legitify --tool "legitify.get_policy" --output json

mcporter call --server legitify --tool "legitify.submit_attestation_request" \
  --args '{"kind":"deploy","title":"Deploy v1.2.3","summary":"Ship release","risk_level":"medium","links":["https://example.com/pr/123"]}' \
  --output json

mcporter call --server legitify --tool "legitify.list_pending_requests" --args '{"limit":10}' --output json

mcporter call --server legitify --tool "legitify.review_request" \
  --args '{"attestation_request_id":"attreq_...","decision":"approved","scope":"deploy_release","notes":"staging verified","reviewed_by":"neely"}' \
  --output json

mcporter call --server legitify --tool "legitify.get_attestation_status" \
  --args '{"attestation_request_id":"attreq_..."}' \
  --output json

Config

Set environment variables:

  • LEGITIFY_BASE_URL (optional) — API base (future)

  • LEGITIFY_API_KEY (optional)

Notes

MVP can run without a remote API by writing requests to a local queue (JSONL) and returning needs_info / pending.

Available Tools

6 tools
legitify.get_attestation_statusB

Get status for an attestation_request_id (MVP: pending unless manually processed).

Inputs: attestation_request_id (required).

legitify.get_pending_request_detailsA

Fetch full details for a pending request by id (including evidence).

Inputs: attestation_request_id (required).

legitify.get_policyA

Get default policy info (caps, required evidence expectations).

Inputs: no named parameters.

legitify.list_pending_requestsC

List pending attestation requests (from local queue).

Inputs: limit.

legitify.review_requestB

Write a human attestation receipt for an existing attestation_request_id (approved/denied/needs_info).

Inputs: decision (required), attestation_request_id (required), notes, scope, +1 more.

legitify.submit_attestation_requestB

Submit a request for human attestation (approval receipt). Returns attestation_request_id and status=pending.

Inputs: title (required), summary (required), kind, links, +5 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    Six tools is well-scoped for an attestation workflow. Each tool maps to a meaningful step in the request lifecycle without unnecessary duplication.

    Completeness4/5

    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.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Human-in-the-loop approval gate for AI agents. Your agent calls submit_approval before any irreversible action; a human reviews on a branded page; a signed webhook fires back with the decision.
      1
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to certify documents, prove agreements, and verify counterparty claims with on-chain receipts on Hedera Hashgraph. Provides tools for document certification, two-party attestation, and agent registration with zero-config setup.
      6
      42 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Gives AI agents verifiable, tamper-evident receipts for their actions — attest_action signs a cryptographic receipt for what the agent did (email sent, payment made, form filed), verify_receipt checks it offline, get_identity returns the agent's did:key. Sign locally, verify anywhere, zero backend.
      3
      MIT