Server Details
Tamper-proof audit trail for AI decisions. 6 tools to record, verify, and export cryptographic proof chains. SHA-256 hash chain, JSON-LD v2 export, public verification.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
7 toolsproof_chain_verifyInspect
Verifies the entire SHA-256 hash chain integrity for a domain. Performs O(n) sequential verification of all Decision Proof Units and reports the first broken index if tampering is detected.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | The domain to verify (e.g. rehab_care, market, edu) | |
| toIndex | No | End verification at this chain index | |
| batchSize | No | Number of DPUs to process per batch | |
| fromIndex | No | Start verification from this chain index |
proof_export_jsonldInspect
Exports a Decision Proof Unit as a JSON-LD v2.0 proof document conforming to Cronozen Evidence Ontology. Includes compliance status, 6W extraction (Who/What/Where/When/How/Why), hash chain info, and policy snapshot.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The DPU ID to export as JSON-LD |
proof_getInspect
Retrieves a Decision Proof Unit by ID with full details including hash chain position, AI involvement, human control, evidence level, and compliance information.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The DPU ID to retrieve |
proof_public_verifyInspect
Publicly verifies a DPU's cryptographic integrity without authentication. Checks SHA-256 hash validity, previous/next chain link integrity, and returns verification status. Anyone can verify — no credentials required.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The DPU ID to publicly verify |
proof_recordInspect
Records an AI execution as a Decision Proof Unit (DPU). Creates a cryptographically chained proof record with SHA-256 hash chain. Returns the created DPU with decision_id and chain hash.
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | Tags for categorization | |
| domain | Yes | Business domain (e.g. rehab_care, market, edu, mentor, welfare) | |
| purpose | Yes | Purpose/reason for the decision | |
| approved | No | Whether the decision was approved | |
| reviewed_by | No | Human reviewer identifier | |
| final_action | Yes | The action that was taken (e.g. CREATE, UPDATE, APPROVE) | |
| reference_id | No | ID of referenced entity | |
| reviewer_role | No | Role of the reviewer (e.g. operator, admin) | |
| evidence_level | No | Evidence level. Default: AUDIT_READY | |
| reference_type | No | Type of referenced entity |
proof_reportInspect
Generates a structured decision report for a DPU. Returns a formatted document with decision details, hash chain verification, and download links (PDF, JSON-LD). Use this after proof_record to provide a downloadable evidence report.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The DPU ID to generate a report for |
proof_verifyInspect
Verifies a specific proof record's cryptographic integrity. Checks hash consistency and returns verification status.
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | Optional original data for re-verification of hash | |
| proofId | Yes | The proof ID to verify |
Verify Ownership
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [
{
"email": "your-email@example.com"
}
]
}The email address must match the email associated with your Glama account. Once verified, the connector will appear as claimed by you.
Sign in to verify ownershipControl your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!