AgentAuth

io.github.raditotevPublished by GitHub account raditotevv0.1.1Updated Oct 24, 2026

Identity and auth for AI agents: credentials, tokens, delegations, and permission checks.

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

AgentAuth gives an AI assistant identity and authorization tools for agents: credentials, tokens, delegations and permission checks against an AgentAuth service

What you can do
Authenticate an agent against the AgentAuth service, using a default API key or a key passed per call, to obtain credentials or tokens. Manage agent credentials and tokens for identity and authorization. Create and handle delegations between agents. Run permission checks to see whether an action is allowed. All operations go to the AgentAuth service at the configured base URL.
When to use it
Use it when an assistant needs to act as an identified agent against an AgentAuth deployment, for example to obtain tokens, delegate access or verify permissions before performing a task. It is only useful if you already run or subscribe to an AgentAuth service.
Requirements
Runs as a local Python package (agentauth-mcp-server) over stdio on a desktop machine. Requires the AGENTAUTH_URL environment variable pointing at the AgentAuth service base URL, such as a hosted instance or a self-hosted localhost address. Optionally set AGENTAUTH_API_KEY as the default key for the authenticate tool; a key can also be supplied per call. Network access to that service is needed.
Before you install
The server handles identity and authorization material: the AGENTAUTH_API_KEY secret and the credentials, tokens and delegations it issues or manages. Treat the API key as sensitive and prefer per-call keys over a stored default where possible. Delegations and permission changes affect what agents are allowed to do, so review them before use. Point AGENTAUTH_URL only at a service you trust, since credentials are exchanged with it.

Installation

In SourceWeft

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

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

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

  • License10 pts

    Declare a license in the repository or the registry entry.