Akeyless Agentic Runtime Authority

io.github.akeyless-communityPublished by GitHub account akeyless-communityv0.1.0Updated Oct 30, 2026

Secretless database and cloud access via Akeyless RTA. Credentials never enter the model.

The publisher's own server: authority.md

Overview

AI-generated overview

Akeyless Agentic Runtime Authority gives an assistant secretless access to databases and cloud resources, keeping credentials out of the model.

What you can do
  • Provides secretless access to databases and cloud resources through Akeyless RTA, so the assistant works with resources without handling raw credentials.
  • Keeps credentials out of the model context, per the provider's description.
  • Authenticates to Akeyless using a configurable method (access key, SAML, OIDC, universal identity, JWT, AWS IAM, Azure AD or GCP).
  • Supports ARA audit sessions tied to an agent ID.
  • No tool list is published, so the exact operations available are not documented here.
When to use it
Worth considering when an assistant needs to reach databases or cloud resources and you want access brokered by Akeyless rather than passing secrets into the model. Best suited to teams already running an Akeyless Gateway and identity setup.
Requirements
Runs as a local stdio process (npm package) on a desktop machine. Needs an Akeyless Gateway URL, an Akeyless Access ID, and an authentication type; access-key auth also needs the access key secret, and audit sessions need an agent ID.
Before you install
Requires the AKEYLESS_ACCESS_KEY secret and an Access ID, which grant access to protected resources; store them in the local environment rather than in prompts. Access is brokered through your Akeyless Gateway, so requests and audit data flow to that service. The published tool list is empty, so review what the connector can actually do before granting it access.

Installation

In SourceWeft

  1. Open Akeyless Agentic Runtime Authority 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.0LatestSep 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.

Other Authority integrations