Mifori CertAgent

Get Agent Audit Certificate & History

get_agent_certificate

Read-onlyIdempotent

Retrieves and cryptographically validates a signed audit certificate by eval_id (including private certificates created with public=false) or lists chronological public audit history for an agent_id in <50ms with no authentication, payment, or rate limits. Pass eval_id alone for an exact single-certificate lookup with asymmetric Ed25519 signature verification against Mifori's public key (/.well-known/jwks.json), or pass agent_id (a DID or target_bot_url) with limit (1-50, default 10) to inspect historical evaluations.

Input Schema

Name	Required	Description
`limit`	No	Maximum number of historical certificates to return when querying by agent_id (integer 1-50, default 10).
`eval_id`	No	UUID of a specific audit certificate to fetch and verify (e.g. 'cab449d2-9072-415d-a8fd-d3a51bd3d87d').
`agent_id`	No	Semantic agent DID (e.g. 'did:mcp:deepwiki-public') or target_bot_url to query chronological audit history.

Output Schema

Name	Required	Description
`count`	Yes	Number of certificate records returned.
`error`	No	Diagnostic message when status is NOT_FOUND or INVALID_ARGUMENTS.
`status`	Yes	Lookup status ('VALIDATED', 'HISTORY_OK', 'NOT_FOUND', 'INVALID_SIGNATURE', or 'INVALID_ARGUMENTS').
`eval_id`	No	Evaluation UUID of the primary or requested certificate.
`agent_id`	No	Semantic agent DID associated with the certificate.
`verified`	Yes	True if the certificate or latest audit has an intact Ed25519 signature and AAA/AA tier.
`issued_at`	No	ISO-8601 UTC timestamp of certificate issuance.
`latency_ms`	No	Measured round-trip latency in milliseconds.
`certificates`	Yes	Chronological list of audit certificates (newest first).
`synthetic_iq`	No	Measured Synthetic IQ score (0-100).
`target_bot_url`	No	Audited target agent endpoint URL.
`reliability_tier`	No	Assigned trust tier ('AAA', 'AA', 'B', or 'REJECTED').
`protocol_detected`	No	Detected protocol ('MCP 2.0', 'Mifori Cognitive v1', etc.).
`certagent_signature`	No	Asymmetric Ed25519 cryptographic signature ('0x...').
`verified_capabilities`	No	Verified MCP tools or agent skills.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 18, 2026

changedInput schema / properties / agent_id / description

Previous value: -"Semantic agent DID (e.g. 'did:mifori:reference-agent') or target_bot_url to query chronological audit history."New value: +"Semantic agent DID (e.g. 'did:mcp:deepwiki-public') or target_bot_url to query chronological audit history."

changedOutput schema / properties / certagent_signature / description

Previous value: -"HMAC-SHA256 cryptographic signature ('0x...')."New value: +"Asymmetric Ed25519 cryptographic signature ('0x...')."

changedOutput schema / properties / certificates / items / properties / certagent_signature / description
```
Previous value: -"HMAC-SHA256 signature."New value: +"Asymmetric Ed25519 signature."
```
addedOutput schema / properties / certificates / items / properties / protocol_detected
```
Added value: +{
+  "description": "Detected protocol.",
+  "type": "string"
+}
```

changedOutput schema / properties / certificates / items / properties / verified / description

Previous value: -"Whether HMAC signature and tier are valid."New value: +"Whether Ed25519 signature and tier are valid."

addedOutput schema / properties / certificates / items / properties / verified_capabilities
```
Added value: +{
+  "description": "Verified capabilities.",
+  "type": "string"
+}
```

addedOutput schema / properties / protocol_detected

Added value: +{
+  "description": "Detected protocol ('MCP 2.0', 'Mifori Cognitive v1', etc.).",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / properties / verified / description

Previous value: -"True if the certificate or latest audit has an intact HMAC-SHA256 signature and AAA/AA tier."New value: +"True if the certificate or latest audit has an intact Ed25519 signature and AAA/AA tier."

addedOutput schema / properties / verified_capabilities

Added value: +{
+  "description": "Verified MCP tools or agent skills.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

AddedOct 16, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover readOnly, idempotent, non-destructive and closed-world, and the description adds substantial context beyond them: <50ms latency, no authentication/payment/rate limits, inclusion of private certificates (public=false), and Ed25519 asymmetric verification against a named JWKS endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences that front-load the core lookup behavior and then the mode-selection rule. Every clause carries information, though the first sentence packs several independent facts (latency, cost, private certs) into one run-on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and annotations covering the safety profile, the description need not explain return shapes. It fully covers both invocation paths, verification mechanism, and access conditions, leaving nothing an agent needs in order to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds interaction semantics the schema lacks: eval_id used alone is mutually exclusive with agent_id+limit, and it clarifies agent_id accepts a DID or target_bot_url. It adds mode-selection meaning beyond the per-parameter schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb (retrieves/validates/lists) and resource (signed audit certificate, public audit history), and clearly delineates the two operations. It is easily distinguished from siblings like get_agent_leaderboard or verify_agent_reputation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the two invocation modes: pass eval_id alone for a single-certificate lookup, or pass agent_id with limit for history. This gives clear context for selection, though it does not name or exclude the sibling tools by comparison.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Mifori CertAgent tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?