AgentVerify

za.co.t-horizon.agentverifyPublished by agentverify.t-horizon.co.zaOfficial publisherv1.0.0Updated Oct 30, 2026

Trust checks for agent-to-agent deals. Identity, co-signed receipts, paid trust scores, and badges.

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

AgentVerify is a remote MCP server that lets an assistant look up agent identities, verify trust badges, and buy paid trust scores for agent-to-agent deals.

What you can do
  • Look up pricing, network and payments mode for the service
  • Read an agent's public profile, without its trust score
  • Verify a trust badge against the server's Ed25519 key
  • Request a trust score for a single agent, paid per call via x402
When to use it
Useful when an assistant needs to assess another agent's identity or trustworthiness before an agent-to-agent transaction, or to confirm that a displayed trust badge is genuine.
Requirements
A remote streamable HTTP endpoint; no local package, account, API key or header is declared. The paid trust check requires an x402 payment payload supplied in the request metadata, so a wallet or x402-capable client is needed.
Before you install
trust_check costs money: the first call returns a PaymentRequired error and must be retried with an x402 payment payload, so spending can occur. Badge verification relies on the server's own Ed25519 key. Public profiles exclude the trust score.

Installation

In SourceWeft

  1. Open AgentVerify in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/za.co.t-horizon.agentverify%2Fagentverify/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "agentverify": {
      "type": "http",
      "url": "https://agentverify.t-horizon.co.za/mcp"
    }
  }
}

Tools

4

get_pricing

Current AgentVerify prices, network, and payments mode. Free.

Takes no parameters.

get_agent_profile

Public agent profile. Does not include the trust score. Free.

Parametersagent_idrequired

verify_badge

Check an AgentVerify trust badge against this server's Ed25519 key. Free.

Parametersbadgerequired

trust_check

Trust score for one agent. Without payment this returns an x402 PaymentRequired tool error. Retry with params._meta['x402/payment'].

Parametersagent_idrequired

Version history

1
  1. v1.0.0LatestOct 30, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.