Skip to main content
Glama

agentfolio_verify_operator

Verify an AI agent's operator identity using OATR attestation, returning off-chain operator status and on-chain SATP reputation to assess trustworthiness.

Instructions

Verify an agent's operator identity via OATR (Open Agent Trust Registry). Returns off-chain operator verification status alongside on-chain SATP reputation. Two-layer identity: who RUNS the agent (OATR) + how TRUSTED the agent is (SATP).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYesAgent ID to check operator identity for
tokenNoOATR attestation token to verify (optional — if not provided, checks AgentFolio profile for linked OATR identity)

Implementation Reference

  • Input schema for agentfolio_verify_operator: requires agent_id (string), optional token (string) for OATR attestation verification.
    {
      name: "agentfolio_verify_operator",
      description:
        "Verify an agent's operator identity via OATR (Open Agent Trust Registry). Returns off-chain operator verification status alongside on-chain SATP reputation. Two-layer identity: who RUNS the agent (OATR) + how TRUSTED the agent is (SATP).",
      inputSchema: {
        type: "object",
        properties: {
          agent_id: {
            type: "string",
            description: "Agent ID to check operator identity for",
          },
          token: {
            type: "string",
            description: "OATR attestation token to verify (optional — if not provided, checks AgentFolio profile for linked OATR identity)",
          },
        },
        required: ["agent_id"],
      },
    },
  • Handler for agentfolio_verify_operator: fetches profile from AgentFolio API, extracts SATP on-chain reputation (trust score, verifications), and performs OATR operator identity verification via optional attestation token or wallet cross-reference.
    case "agentfolio_verify_operator": {
      const profile = await api(`/profile/${args.agent_id}`);
      const satpTrust = profile.trustScore ?? 0;
      const verifs = profile.verifications || {};
      const verifsArr = Array.isArray(verifs) ? verifs : Object.keys(verifs).filter(k => verifs[k]);
      const satpOnChain = verifsArr.includes("solana") || !!verifs.solana;
      
      let oatrResult = null;
      if (oatrAvailable) {
        try {
          if (args.token && verifyAttestation) {
            // Verify a specific OATR attestation token
            oatrResult = await verifyAttestation(args.token);
          } else {
            // Check if agent has OATR-linked identity via wallet key
            const wallets = profile.wallets || {};
            const solanaAddr = wallets.solana || wallets.sol;
            oatrResult = {
              checked: true,
              linked: false,
              note: solanaAddr 
                ? `Agent has Solana wallet ${solanaAddr}. OATR operator lookup requires attestation token or DID.`
                : "No Solana wallet linked. Cannot cross-reference with OATR operator registry.",
            };
          }
        } catch (err) {
          oatrResult = { checked: true, error: err.message };
        }
      } else {
        oatrResult = {
          checked: false,
          note: "OATR integration not available. Install @open-agent-trust/registry for two-layer identity verification.",
        };
      }
      
      return JSON.stringify({
        agent_id: args.agent_id,
        name: profile.name,
        two_layer_identity: {
          layer1_oatr: {
            description: "Off-chain operator identity (who runs this agent)",
            ...oatrResult,
          },
          layer2_satp: {
            description: "On-chain agent reputation (how trusted is this agent)",
            trust_score: satpTrust,
            on_chain: satpOnChain,
            verifications: verifsArr,
          },
        },
        combined_assessment: satpOnChain 
          ? `Agent has on-chain SATP identity (trust: ${satpTrust}). ${oatrResult?.linked ? "OATR operator verified." : "OATR operator not yet linked."}`
          : `Agent registered but no on-chain identity yet. Trust score: ${satpTrust}.`,
      }, null, 2);
    }
  • OATR integration setup: dynamically imports @open-agent-trust/registry to provide verifyAttestation function. Sets oatrAvailable flag used by the verify_operator handler.
    // ── OATR Integration (Open Agent Trust Registry) ─────────────────────────────
    // Two-layer identity: OATR (off-chain operator) + SATP (on-chain reputation)
    let oatrAvailable = false;
    let verifyAttestation, OpenAgentTrustRegistry;
    try {
      const oatr = await import("@open-agent-trust/registry");
      verifyAttestation = oatr.verifyAttestation;
      OpenAgentTrustRegistry = oatr.OpenAgentTrustRegistry || oatr.default;
      if (verifyAttestation || OpenAgentTrustRegistry) {
        oatrAvailable = true;
        console.error("[agentfolio-mcp] OATR integration enabled");
      }
    } catch {
      console.error("[agentfolio-mcp] OATR not available (optional dependency)");
    }
  • HTTP helper used by the handler to fetch profile data from the AgentFolio API (https://agentfolio.bot/api).
    async function api(path, opts = {}) {
      const url = `${API_BASE}${path}`;
      const res = await fetch(url, {
        headers: { "Content-Type": "application/json", ...opts.headers },
        ...opts,
      });
      if (!res.ok) {
        const body = await res.text().catch(() => "");
        throw new Error(`AgentFolio API ${res.status}: ${body}`);
      }
      // Guard against HTML error pages returned with 200
      const ct = res.headers.get("content-type") || "";
      if (!ct.includes("application/json")) {
        const body = await res.text().catch(() => "");
        if (body.includes("<!DOCTYPE") || body.includes("<html")) {
          throw new Error(`AgentFolio API returned HTML instead of JSON for ${path}`);
        }
      }
      return res.json();
    }
  • src/index.js:437-440 (registration)
    Registration: tools are exposed via the MCP ListToolsRequestSchema handler, returning the TOOLS array which includes agentfolio_verify_operator at index [9].
    // List tools
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: TOOLS,
    }));
Behavior2/5

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

No annotations provided, so description carries full burden. It lacks disclosure on read-only nature, required permissions, rate limits, or cost. The fallback behavior when token is omitted is mentioned, but no details on error handling or side effects.

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

Conciseness5/5

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

Two sentences with no redundancy. First sentence clearly states action and protocol; second sentence adds complementary context. Efficient and scannable.

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

Completeness2/5

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

Without output schema, description should describe return structure (e.g., fields, data types). Only vague references to 'status' and 'reputation' are given. Missing error scenarios, edge cases, and data format details necessary for reliable invocation.

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%, and description adds meaning by explaining the optional token parameter's fallback behavior and the two-layer identity concept. However, it does not detail expected values or return format beyond high-level status.

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?

Description states specific action (verify operator identity via OATR), identifies two distinct outputs (off-chain status and on-chain SATP reputation), and distinguishes from sibling tools by focusing on the operator layer.

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

Usage Guidelines3/5

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

Description explains what the tool does but provides no guidance on when to use it versus alternatives like agentfolio_verify or agentfolio_trust_gate. Usage context is implied but not explicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/0xbrainkid/agentfolio-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server