AP Control Labs Finance Controls

io.github.juodocPublished by GitHub account juodocv1.1.0Updated Oct 24, 2026

Read-only finance and operations controls for AI agents with evidence and safe next actions.

The publisher's own server: Finance Foundation

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

A remote, read-only MCP server giving AI assistants finance and operations controls with supporting evidence and suggested safe next actions.

What you can do
Provides read-only finance and operations controls for AI agents, as described in the registry entry. Returns supporting evidence alongside the controls it exposes. Suggests safe next actions rather than performing changes itself. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Consider it when an assistant needs to inspect finance and operations controls in an AP Control workspace without making changes, and when evidence-backed results and suggested next steps are useful.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. A bearer API key created in the AP Control workspace, sent in the Authorization header, is required.
Before you install
The server requires a bearer API key in the Authorization header; treat it as a secret and keep it out of logs and shared transcripts. The registry describes the controls as read-only, but the manifest lists no tools, so verify what each call actually does before relying on that.

Installation

In SourceWeft

  1. Open AP Control Labs Finance Controls in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/io.github.juodoc%2Fap-control/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": {
    "ap-control-labs-finance-controls": {
      "type": "http",
      "url": "https://api-production-9502.up.railway.app/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

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

Version history

1
  1. v1.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 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.

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

Other Finance integrations