Autonomy Foundry Governance

io.github.DiegomulPublished by GitHub account Diegomulv0.2.0Updated Oct 24, 2026

Governance and agentic-commerce policy tools for AI agents: spend, purchase and charter controls.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

A remote MCP endpoint offering governance and agentic-commerce policy tools for AI agents, covering spend, purchase and charter controls.

What you can do
The server exposes governance and agentic-commerce policy tools intended for AI agents, described as spend, purchase and charter controls. It is a remote streamable HTTP endpoint, so the assistant connects to it directly rather than running a local package. No individual tools are listed in the available material, so the exact operations are not documented here.
When to use it
Consider it when an assistant needs policy or governance checks around agent spending, purchasing, or charter rules. It may suit setups where agent commerce actions should be constrained by an external policy service.
Requirements
A remote streamable HTTP connection to the provider's endpoint. No authentication, environment variables, or headers are declared, and no local runtime or package is needed.
Before you install
The description mentions spend and purchase controls, so the server relates to money-related agent actions; confirm how spending limits are enforced before relying on it. No authentication is declared, so verify who can reach the endpoint and what data it receives. No tool list is published, so review the actual tools before granting access.

Installation

In SourceWeft

  1. Open Autonomy Foundry Governance 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/io.github.Diegomul%2Fautonomy-foundry-governance/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": {
    "autonomy-foundry-governance": {
      "type": "http",
      "url": "https://autonomy-foundry.autonomyfoundry.workers.dev/mcp"
    }
  }
}

README

This repository has no README.

Tools

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

Version history

1
  1. v0.2.0LatestSep 23, 2026

Score

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