Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Kevros — Agentic Identity Trust

REMOTE · GOVERNANCE.TASKHAWKTECH.COM · SCANNED SEP 20

Agentic identity trust: precision decisioning, cryptographic release tokens, hash-chained proof

0 this week 85 Trust /100
Trust breakdown (7 categories)

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 Security69
Transport & Reachability100
Schema Quality & AI Usability85
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1094 tokens (~99/item across 11 items; 9 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

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

# add to Claude Code
claude mcp add --transport http ndl-systems-kevros 'https://governance.taskhawktech.com/mcp/'
// .cursor/mcp.json
{
  "mcpServers": {
    "ndl-systems-kevros": {
      "url": "https://governance.taskhawktech.com/mcp/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ndl-systems-kevros": {
      "type": "http",
      "url": "https://governance.taskhawktech.com/mcp/"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.ndl-systems-kevros]
url = "https://governance.taskhawktech.com/mcp/"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ndl-systems-kevros": {
      "type": "remote",
      "url": "https://governance.taskhawktech.com/mcp/",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ndl-systems-kevros --url 'https://governance.taskhawktech.com/mcp/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ndl-systems-kevros:
    url: "https://governance.taskhawktech.com/mcp/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ndl-systems-kevros": {
      "Transport": "http",
      "Url": "https://governance.taskhawktech.com/mcp/"
    }
  }
}
# add to Vellum
assistant mcp add ndl-systems-kevros -t streamable-http -u 'https://governance.taskhawktech.com/mcp/'
// mcp.json
{
  "mcpServers": {
    "ndl-systems-kevros": {
      "type": "http",
      "url": "https://governance.taskhawktech.com/mcp/"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 4 Sept 26 +1
    • Stability: 0.97 → pass security
  • 1 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Aug 26 −3
    • Stability: pass → 0.77 functional
  • 26 Aug 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
  • 25 Aug 26 +1
    • Stability: 0.97 → pass security
  • 23 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Aug 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
Diagnostics

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 20 Sept 2026 · Probed https://governance.taskhawktech.com/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=governance.taskhawktech.com CN=Amazon RSA 2048 M04,O=Amazon,C=US 26 May 2026 9 Dec 2026 RSA 2048 SHA256-RSA 432aac6e8325237e0a0f80046465a1d
SANs: governance.taskhawktech.com
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of governance.taskhawktech.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
taskhawktech.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'none'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy camera=(), microphone=(), geolocation=()

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/ Verified 200
http (plaintext) http://governance.taskhawktech.com/mcp/ Inconclusive 403
MCP tools · 9 exposed · ~1,065 tokens

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 →

Tool Tokens
attest ~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.

NameTypeReqDescription
action_descriptionstringyesHuman-readable description of the action taken
action_payloadobjectyesStructured data describing the action (hashed into provenance)
agent_idstringyesUnique identifier of the attesting agent
contextOptional metadata such as environment, trigger, or session info
NameTypeReqDescription
resultstringyes

No examples provided.

bind ~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.

NameTypeReqDescription
agent_idstringyesUnique identifier of the agent declaring intent
command_payloadobjectyesThe command that will be executed to fulfill this intent
goal_stateExpected end state for outcome verification
intent_descriptionstringyesHuman-readable description of what the agent intends to do
intent_sourcestringOrigin of intent: AI_PLANNER, HUMAN_OPERATOR, or SYSTEM
intent_typestringyesCategory of intent (e.g. 'navigation', 'transaction', 'deployment')
parent_intent_idID of parent intent for hierarchical intent chains
NameTypeReqDescription
resultstringyes

No examples provided.

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.

NameTypeReqDescription
agent_idstringyesAgent whose provenance records to include in the bundle
include_intent_chainsbooleanInclude intent-command binding chains in the bundle
include_pqc_signaturesbooleanInclude post-quantum ML-DSA-87 block signatures
include_verification_instructionsbooleanInclude step-by-step verification procedure for auditors
max_recordsintegerMaximum number of provenance records to include
time_range_endISO 8601 end time filter (inclusive)
time_range_startISO 8601 start time filter (inclusive)
NameTypeReqDescription
resultstringyes

No examples provided.

check-peer ~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.

NameTypeReqDescription
agent_idstringyesID of the peer agent to look up
NameTypeReqDescription
resultstringyes

No examples provided.

health ~35

Check the governance gateway health status. Free.

NameTypeReqDescription
verbosebooleanReturn additional details such as chain length and PQC signing status
NameTypeReqDescription
resultstringyes

No examples provided.

status ~49

Check your current usage and quota: calls used, calls remaining, tier, rate limits, and billing status. Free.

NameTypeReqDescription
include_chain_detailsbooleanInclude hash-chain integrity check and latest provenance epoch
NameTypeReqDescription
resultstringyes

No examples provided.

verify ~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.

NameTypeReqDescription
action_payloadobjectyesAction parameters to verify against policy bounds
action_typestringyesCategory of action to verify (e.g. 'deploy', 'trade', 'send_email')
agent_idstringyesUnique identifier of the agent requesting verification
idempotency_keyOptional key for idempotent retries - same key returns cached result
policy_contextOptional policy overrides such as max_values or forbidden_keys
template_idNamed policy template (e.g. 'robotics-arm', 'financial-transaction'). Merged with policy_context.
NameTypeReqDescription
resultstringyes

No examples provided.

verify-outcome ~133

Verify that an executed action achieved its declared intent. Closes the loop: intent -> command -> action -> outcome -> verification. Free (included with bind).

NameTypeReqDescription
actual_stateobjectyesObserved end state after action execution, compared against goal_state
agent_idstringyesUnique identifier of the agent whose outcome is being verified
binding_idstringyesID of the intent-command binding from governance_bind
intent_idstringyesID of the original intent from governance_bind
tolerancenumberNumeric tolerance for goal matching (0.1 = 10% deviation allowed)
NameTypeReqDescription
resultstringyes

No examples provided.

verify-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.

NameTypeReqDescription
release_tokenstringyesRelease token string received from governance_verify
token_preimageDeprecated. 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…
NameTypeReqDescription
resultstringyes

No examples provided.

Common questions

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 85 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?

No. We connected to Kevros — Agentic Identity Trust without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Kevros — Agentic Identity Trust MCP server still maintained?

Kevros — Agentic Identity Trust is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.