MolTrust MCP Server

mt_endorse_agent

Idempotent

Issue a W3C SkillEndorsementCredential for another agent.

Requires a valid evidence_hash from mt_create_interaction_proof
(max 72h old). Self-endorsement is rejected.
Contributes to the endorsed agent's Trust Score.

Args:
    endorser_api_key: MolTrust API key of the endorsing agent
    endorsed_did: DID of the agent to endorse
    skill: Skill being endorsed (python, javascript, security, prediction, trading, data_analysis, api_integration, smart_contracts, nlp, computer_vision, general)
    evidence_hash: SHA-256 hash from mt_create_interaction_proof (sha256:...)
    evidence_timestamp: ISO 8601 timestamp from mt_create_interaction_proof
    vertical: MolTrust vertical (skill, shopping, travel, prediction, salesguard, sports, core)

Input Schema

Name	Required	Description
`skill`	Yes	Skill being endorsed (python, javascript, security, prediction, trading, data_analysis, api_integration, smart_contracts, nlp, computer_vision, general)
`vertical`	Yes	MolTrust vertical (skill, shopping, travel, prediction, salesguard, sports, core)
`endorsed_did`	Yes	DID of the agent to endorse, e.g. did:moltrust:a1b2c3d4e5f60718
`evidence_hash`	Yes	SHA-256 hash from mt_create_interaction_proof (sha256:...)
`endorser_api_key`	Yes	MolTrust API key of the endorsing agent
`evidence_timestamp`	Yes	ISO 8601 timestamp from mt_create_interaction_proof

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 28, 2026

addedInput schema / properties / endorsed_did / description

Added value: +"DID of the agent to endorse, e.g. did:moltrust:a1b2c3d4e5f60718"

addedInput schema / properties / endorser_api_key / description
```
Added value: +"MolTrust API key of the endorsing agent"
```

addedInput schema / properties / evidence_hash / description

Added value: +"SHA-256 hash from mt_create_interaction_proof (sha256:...)"

addedInput schema / properties / evidence_timestamp / description

Added value: +"ISO 8601 timestamp from mt_create_interaction_proof"

addedInput schema / properties / skill / description

Added value: +"Skill being endorsed (python, javascript, security, prediction, trading, data_analysis, api_integration, smart_contracts, nlp, computer_vision, general)"

addedInput schema / properties / vertical / description

Added value: +"MolTrust vertical (skill, shopping, travel, prediction, salesguard, sports, core)"

First observedSep 22, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover readOnly=false, idempotent=true, destructive=false, and the description adds valuable behavioral context: the evidence-hash freshness constraint, self-endorsement rejection, and the downstream effect on the endorsed agent's Trust Score. It doesn't explain idempotent behavior directly, so 4.

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?

The core purpose and prerequisites are front-loaded in three tight sentences. The Args block duplicates schema text and adds length without much new information, slightly diluting conciseness.

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

Completeness4/5

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

A mutation/issuance tool with an output schema present, so return values needn't be described. Prerequisites and consequences are covered; the main small gap is not distinguishing from sibling issuance tools, but the definition is complete enough to call correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description's Args section largely restates the schema field descriptions, adding only the renamed 'endorser_api_key' phrasing and cross-referencing mt_create_interaction_proof for two fields, but not meaningfully extending semantics.

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

Purpose4/5

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

States a specific verb ('Issue') and resource ('W3C SkillEndorsementCredential for another agent'), which clearly distinguishes it from verify/score siblings. It does not explicitly differentiate from other issuance tools like mt_skill_issue_vc, so a 4 rather than 5.

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?

Provides concrete prerequisites: a valid evidence_hash from mt_create_interaction_proof no older than 72h, and that self-endorsement is rejected. It lacks explicit guidance on when to choose this over sibling issuance tools, keeping it below 5.

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

All MolTrust MCP Server 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.