legitify-mcp
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@legitify-mcp submit attestation request to deploy v1.2.3"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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_requestlegitify.get_attestation_statuslegitify.get_policylegitify.list_pending_requestslegitify.get_pending_request_detailslegitify.review_request
Quickstart (local)
cd projects/legitify-mcp
npm i
npm run devConfigure 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 jsonConfig
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 toolslegitify.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
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.
Related MCP Connectors
Supervised API-write gateway for AI agents with policy, human approval and execution receipts.
Authorize AI agent tool calls before they run: policy-as-code, human approval, signed receipts.
Human-in-the-loop approval for agent actions, with verifiable action-bound receipts.
Give any AI agent a way to ask a person — for approval, a decision, an answer or a review.
Related MCP Servers
- AlicenseAqualityDmaintenanceHuman-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.11MIT
- AlicenseAqualityDmaintenanceEnables 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.642 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to request human approvals with customizable forms, webhooks, and team features.MIT
- AlicenseAqualityDmaintenanceGives 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.3MIT