Fullmakt

ai.fullmaktPublished by fullmakt.aiOfficial publisherv0.1.0Updated Oct 30, 2026

Credential broker for AI agents: scoped, revocable API access with policy enforcement and audit.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Remote credential broker that gives AI agents scoped, revocable API access with policy enforcement and audit logging.

What you can do
  • Acts as a credential broker for AI agents, mediating access to APIs on the agent's behalf.
  • Grants scoped, revocable API access rather than handing over long-lived secrets.
  • Enforces access policies on the requests an agent makes.
  • Records audit information about that access.
  • No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Worth considering when an assistant needs to call third-party APIs but you want access limited in scope, revocable, policy-controlled and auditable instead of sharing raw credentials.
Requirements
A remote MCP endpoint at fullmakt.ai over streamable HTTP. OAuth authentication is required. No environment variables or headers are declared.
Before you install
The server sits between your agents and your API credentials, so it becomes a trusted party holding access to those APIs; review its scoping, revocation and audit behavior before use. OAuth authorization is required, and the manifest does not document which tools or actions it exposes.

Installation

In SourceWeft

  1. Open Fullmakt in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/ai.fullmakt%2Ffullmakt/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "fullmakt": {
      "type": "http",
      "url": "https://fullmakt.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

67% 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 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.

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