Kevros — Agentic Identity Trust
REMOTE · GOVERNANCE.TASKHAWKTECH.COM
Agentic identity trust: precision decisioning, cryptographic release tokens, hash-chained proof
Available components
Last scanned (8 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 20 Oct 2026.
Category Security
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security14
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 27 Oct 26 −18
The score moved with no change recorded against any check. We would rather say so than guess.
- 26 Oct 26 −18
The score moved with no change recorded against any check. We would rather say so than guess.
- 25 Oct 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 24 Oct 26 −18
The score moved with no change recorded against any check. We would rather say so than guess.
- 23 Oct 26 −18
The score moved with no change recorded against any check. We would rather say so than guess.
- 21 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 16 Oct 26 +4
- Authorization: partial → fail ▼ security
- DNSSEC: fail → pass ▲ security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Oct 2026 · Probed https://governance.taskhawktech.com/mcp/
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of governance.taskhawktech.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| taskhawktech.com. | present | 2371 | 13 | Verified |
| governance.taskhawktech.com. | Verified address RRset verified with the apex keys |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://governance.taskhawktech.com/mcp/ | Unreachable | ||
| http (plaintext) | http://governance.taskhawktech.com/mcp/ | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
attest Attest Action ~113
Create a hash-chained provenance record for an action you've taken. Each attestation extends the append-only evidence chain. The hash can be independently verified by any third party. Cost: $0.02 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| action_description | string | yes | Human-readable description of the action taken |
| action_payload | object | yes | Structured data describing the action (hashed into provenance) |
| agent_id | string | yes | Unique identifier of the attesting agent |
| context | – | – | Optional metadata such as environment, trigger, or session info |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
bind Bind Intent to Command ~176
Declare an intent and cryptographically bind it to a command. Proves that the command was issued in service of the declared intent. Use verify-outcome after execution to close the loop. Cost: $0.02 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Unique identifier of the agent declaring intent |
| command_payload | object | yes | The command that will be executed to fulfill this intent |
| goal_state | – | – | Expected end state for outcome verification |
| intent_description | string | yes | Human-readable description of what the agent intends to do |
| intent_source | string | – | Origin of intent: AI_PLANNER, HUMAN_OPERATOR, or SYSTEM |
| intent_type | string | yes | Category of intent (e.g. 'navigation', 'transaction', 'deployment') |
| parent_intent_id | – | – | ID of parent intent for hierarchical intent chains |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
bundle Generate Compliance Bundle ~178
Generate a certifier-grade compliance evidence bundle. Contains hash-chained provenance, intent bindings, PQC attestations, and verification instructions. Independently verifiable without Kevros access. Cost: $0.05 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Agent whose provenance records to include in the bundle |
| include_intent_chains | boolean | – | Include intent-command binding chains in the bundle |
| include_pqc_signatures | boolean | – | Include post-quantum ML-DSA-87 block signatures |
| include_verification_instructions | boolean | – | Include step-by-step verification procedure for auditors |
| max_records | integer | – | Maximum number of provenance records to include |
| time_range_end | – | – | ISO 8601 end time filter (inclusive) |
| time_range_start | – | – | ISO 8601 start time filter (inclusive) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
check-peer Check Peer Trust ~59
Check another agent's trust score and governance history. Returns trust score (0-100), chain length, attestation count, and tier. Free, no API key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | ID of the peer agent to look up |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
health Health Check ~35
Check the governance gateway health status. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| verbose | boolean | – | Return additional details such as chain length and PQC signing status |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
status Trust Status ~49
Check your current usage and quota: calls used, calls remaining, tier, rate limits, and billing status. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| include_chain_details | boolean | – | Include hash-chain integrity check and latest provenance epoch |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify Verify Action ~210
Verify an action against policy bounds before executing it. Returns ALLOW (proceed), CONSTRAIN (proceed with modified values; emitted on the wire as the legacy value CLAMP - both refer to the same verdict, CONSTRAIN is the public name), or DENY (stop). Every verification is recorded in a hash-chained provenance ledger. Cost: $0.01 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| action_payload | object | yes | Action parameters to verify against policy bounds |
| action_type | string | yes | Category of action to verify (e.g. 'deploy', 'trade', 'send_email') |
| agent_id | string | yes | Unique identifier of the agent requesting verification |
| idempotency_key | – | – | Optional key for idempotent retries - same key returns cached result |
| policy_context | – | – | Optional policy overrides such as max_values or forbidden_keys |
| template_id | – | – | Named policy template (e.g. 'robotics-arm', 'financial-transaction'). Merged with policy_context. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify-outcome Verify Outcome ~133
Verify that an executed action achieved its declared intent. Closes the loop: intent -> command -> action -> outcome -> verification. Free (included with bind).
| Name | Type | Req | Description |
|---|---|---|---|
| actual_state | object | yes | Observed end state after action execution, compared against goal_state |
| agent_id | string | yes | Unique identifier of the agent whose outcome is being verified |
| binding_id | string | yes | ID of the intent-command binding from governance_bind |
| intent_id | string | yes | ID of the original intent from governance_bind |
| tolerance | number | – | Numeric tolerance for goal matching (0.1 = 10% deviation allowed) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify-token Verify Release Token ~112
Verify a release token from another agent. Confirms the token is authentic, was issued by the Kevros gateway, and remains currently authorized after any halt or mode transition. Free, no API key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| release_token | string | yes | Release token string received from governance_verify |
| token_preimage | – | – | Deprecated. The gateway now performs verification entirely server-side using the release_token alone; any value supplied here is ignored. Field retained for backward compatibility with v1 SDK callers… |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the Kevros — Agentic Identity Trust MCP server?
Kevros — Agentic Identity Trust is a hosted endpoint at https://governance.taskhawktech.com/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · governance.taskhawktech.com
claude mcp add --transport http ndl-systems-kevros 'https://governance.taskhawktech.com/mcp/'
What is the Kevros — Agentic Identity Trust MCP server?
Kevros — Agentic Identity Trust is an MCP server listed in the public MCP registry as io.github.ndl-systems/kevros. Agentic identity trust: precision decisioning, cryptographic release tokens, hash-chained proof. This page covers its hosted endpoint (https://governance.taskhawktech.com/mcp/).
Is the Kevros — Agentic Identity Trust MCP server safe to use?
Kevros — Agentic Identity Trust scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Kevros — Agentic Identity Trust MCP server expose?
Kevros — Agentic Identity Trust exposes 9 tools: verify, attest, bind, verify-outcome, bundle, and 4 more. Their descriptions and schemas cost roughly 1,065 tokens of context every time the server is loaded.
Does the Kevros — Agentic Identity Trust MCP server require authentication?
Its publisher declares no required credentials for Kevros — Agentic Identity Trust. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Kevros — Agentic Identity Trust MCP server still maintained?
Kevros — Agentic Identity Trust has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 20 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.