MAVENS.mcp

io.github.franzfarianPublished by GitHub account franzfarianv0.2.4Updated Oct 24, 2026

Review connected software projects, submit local findings and read reports with explicit approval.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

A remote MCP server for reviewing connected software projects, submitting local findings and reading reports, with explicit approval required.

What you can do
Review connected software projects through the assistant, using the remote endpoint at mavens.it. Submit findings gathered locally back to the service. Read reports produced for the connected projects. Actions are described as requiring explicit approval before they proceed.
When to use it
Useful when you want an assistant to help audit or review software projects already connected to the MAVENS service and to pull their reports into the conversation.
Requirements
A remote streamable HTTP endpoint at mavens.it; no local package or runtime is needed. OAuth authentication is required, so an account with the provider is needed. Network access to the endpoint.
Before you install
Requires OAuth sign-in to a third-party service, and project data and submitted findings are sent to that service. Submitting findings writes data to the connected projects, so review what is sent before approving; the server states that actions need explicit approval.

Installation

In SourceWeft

  1. Open MAVENS.mcp 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/io.github.franzfarian%2Fmavens-mcp/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": {
    "mavens": {
      "type": "http",
      "url": "https://mavens.it/api/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.2.4LatestSep 29, 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.