AuditFellow

app.auditfellowPublished by auditfellow.appOfficial publisherv0.3.0Updated Oct 26, 2026

Your audit methodology inside Claude: findings, risks, controls and workpapers in your team format.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

AuditFellow is a remote MCP server that brings your audit methodology into Claude, covering findings, risks, controls and workpapers in your team's format.

What you can do
  • Work with audit findings, risks and controls inside the assistant.
  • Produce and manage workpapers in the team's own format.
  • Apply the organization's audit methodology to the work being drafted.
  • No individual tools are documented, so exact operations are not described in the available material.
When to use it
Useful for audit teams that already follow a defined methodology and want an assistant to draft or organize findings, risks, controls and workpapers in their standard format instead of generic output.
Requirements
A remote MCP endpoint at auditfellow.app using streamable HTTP. OAuth authentication is required, so a user account with the provider is needed. No environment variables or headers are declared.
Before you install
The server is hosted by a third party and requires OAuth sign-in, so audit content you send is handled outside your machine. Audit findings and workpapers are often confidential; confirm the provider's data handling before use. No tool list is published, so what it can read or change cannot be verified in advance.

Installation

In SourceWeft

  1. Open AuditFellow 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/app.auditfellow%2Fauditfellow/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": {
    "auditfellow": {
      "type": "http",
      "url": "https://auditfellow.app/mcp/oauth"
    }
  }
}

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.3.0LatestSep 16, 2026

Score

56% 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

    Publish an icon in the registry entry.

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