Helvabase — Governed response dossiers

com.helvabasePublished by helvabase.comOfficial publisherv1.0.0Updated Oct 27, 2026

Connect your AI assistant to governed tender and RFP dossiers: sources, versions, decisions.

VerifiedStreamable HTTPWeb executableKnowledge & Memory Business & Commerce

Server details

Identifier: com.helvabase/helvabase
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to helvabase.com, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.helvabase%2Fhelvabase.svg)](https://sourceweft.com/mcp/com.helvabase%2Fhelvabase?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Remote Helvabase connector that gives an AI assistant access to governed tender and RFP dossiers, including sources, versions and decisions.

What you can do: Browse and query governed tender and RFP dossiers, including their sources, versions and decisions.
Run a small core catalogue of eight essential operations plus metadata help.
Invoke scoped read and write specialist operations through packaged skills that describe discovery and exact-contract invocation.
Work in French, English and German, with workflows for sourced dossiers and human review.
When to use it: Useful when you work with public-procurement or RFP material and want an assistant to look up dossiers, trace their sources and versions, and follow decisions inside a governed workspace rather than ad-hoc documents.
Requirements: A remote HTTPS endpoint ending in /mcp on the hosted Helvabase service; no local server is provided. A Helvabase account authorized through the client's OAuth flow (Authorization header). The optional config generator needs Node.js 20 or newer.

Before you install

Requires authorizing your Helvabase account; no API key or bearer token is written into client config files. The server exposes scoped write operations, so changes may affect your workspace. Changing the endpoint URL can require re-authorizing OAuth. The README states the repository is not an official directory approval and that native client acceptance, file transfer, refresh/revocation and human-review workflows still need verification against the deployed service.

Installation

In SourceWeft

Open Helvabase — Governed response dossiers in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
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/com.helvabase%2Fhelvabase/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": {
    "helvabase-governed-response-dossiers": {
      "type": "http",
      "url": "https://helvabase.com/mcp"
    }
  }
}

README

Helvabase plugins and connector

Published by Starbox Group Gmbh. The plugins provide workflows for sourced dossiers and human review, in French, English and German.

Install the plugin from this repository

Add https://github.com/alopez3006/helvabase-mcp as a plugin marketplace in your client, then install Helvabase and authorize your Helvabase account. Repository catalogues are available for Claude and Codex. This repository is not an official directory approval; native end-to-end acceptance remains in progress.

Français
English
Deutsch
Claude complete plugin: plugins/claude/helvabase
Codex complete plugin: plugins/helvabase

Plugin files are MIT licensed. Brand assets and the hosted service are excluded; see LICENSE and NOTICE.

Agent catalogue

Plugin version 1.4.8 uses https://helvabase.com/mcp?catalog=core: eight essential operations, metadata help and scoped read/write specialist execution. The packaged skills describe discovery and exact-contract invocation. Update your existing plugin and refresh its tools; changing from the previous URL can require OAuth again. Keep the same authorized account and workspace.

The complete individual catalogue remains at https://helvabase.com/mcp, including for review. No official directory acceptance is implied. Native Codex specialist reads have been verified; native Claude acceptance and full file workflows remain separate checks.

Connector configuration fallback

This repository is the public installation surface for the hosted Helvabase MCP connector. It does not contain the Helvabase application, customer data, backend credentials or a standalone replacement server.

Generate configuration

Use Node.js 20 or newer:

The command writes codex.toml, claude.json, mistral.json and README.txt to ./helvabase-mcp-config (or the directory supplied with --out).

Authentication is completed through each client’s OAuth flow. No API key or bearer token is placed in a client configuration file.

The URL must be a deployed Helvabase HTTPS endpoint ending in /mcp. This kit does not deploy Helvabase or provide a local server. Native-client compatibility, file transfer, refresh/revocation and human-review workflows must be verified against the deployed service.

Only files under public/mcp are published from the private Helvabase repository. The source workflow syncs this directory after changes land on main. It uses a dedicated SSH deploy key with write access only to alopez3006/helvabase-mcp, stored as the source repository's MCP_PUBLICATION_SSH_KEY Actions secret. No personal GitHub token is required.

Source: README.md at commit c192ba4

Tools

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

v1.0.0LatestSep 16, 2026

Score

85% 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
License10 pts