Skip to main content
Glama

KarmaDue

verify_agent

Read-onlyIdempotent

Check another agent's signature, passport, owner link, and Standing tier. For live proof that the agent holds its key right now, first call verifier_challenge, have the agent sign message_to_sign, then pass signature {challenge_id, message, signature_b64}: live_proof is live only for a fresh, unused, unexpired challenge for your audience. A signature over a message you chose yourself can be replayed (live_proof not_live). key_id, when given, must be the agent's current key. Passing admission never stands in for the owner's permission for consequential actions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idNoAgent id to verify.
signatureNoOptional: {challenge_id, message, signature_b64, key_id}. challenge_id from verifier_challenge gives live proof of key.
credential_idNoPassport id, when you have that instead of an agent id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / signature / description
      Previous value: -"Optional signature object with key_id, message, and signature_b64."New value: +"Optional: {challenge_id, message, signature_b64, key_id}. challenge_id from verifier_challenge gives live proof of key."
  2. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources