Agentra

ai.agentrapayPublished by agentrapay.aiOfficial publisherv1.0.0Updated Oct 24, 2026

Identity oracle and trust layer for autonomous AI agents. Bidirectional KYA and trust scoring.

VerifiedSSEWeb executableSecurity & MonitoringAI & ML

Overview

AI-generated overview

Agentra is a remote MCP endpoint described as an identity oracle and trust layer that gives autonomous AI agents bidirectional KYA and trust scoring.

What you can do
Provides an identity oracle for autonomous AI agents, per the registry description. Offers bidirectional KYA (know-your-agent) checks. Returns trust scores for agents. No tool list, instructions or README were supplied, so the exact operations and their inputs and outputs cannot be confirmed from this listing.
When to use it
Consider it when an assistant or agent workflow needs to check or assert agent identity and trust scores, for example before letting one agent act on behalf of another. Because no tools are documented, verify the actual capabilities before relying on it.
Requirements
A remote MCP connection over SSE to the provider's endpoint. The manifest declares no authentication, environment variables or headers, and no packages; confirm with the provider whether any credentials are actually needed.
Before you install
The service handles agent identity and trust data, which may be sensitive; consider what identity details are sent to this third party. No authentication is declared, so verify how access is controlled. No tools are documented, so write or other actions cannot be ruled out.

Installation

In SourceWeft

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

Web executable via SSE. 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/ai.agentrapay%2Fagentra/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": {
    "agentra": {
      "type": "sse",
      "url": "https://api.agentrapay.ai/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

56% 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

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

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