How do I install Helvabase?

Helvabase is a remote plugin. You do not need to install anything locally. Add the server URL to your AI app's MCP configuration and you are ready to go.

Is Helvabase safe to use?

Yes. Helvabase passed MCP Marketplace's automated security scan with a score of 10/10 (low risk). Every server on MCP Marketplace is security-scanned before it's listed; see the full security report on this page for the findings and permissions.

What AI apps work with Helvabase?

Helvabase uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Helvabase MCP Server

by Alopez3006

Developer ToolsLow Risk10.0MCP RegistryRemote

Free

Server data from the Official MCP Registry

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

About

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

Remote endpoints: streamable-http: https://helvabase.com/mcp

Security Report

10.0

Low Risk10.0Low Risk

Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

Endpoint verified · Requires authentication · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

file_system

Applies to the server that hosts this plugin, not to your machine.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "com-helvabase-helvabase": {
      "url": "https://helvabase.com/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub 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:

npx --yes github:alopez3006/helvabase-mcp \
  --url https://helvabase.com/mcp

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.

Reviews

No reviews yet

Be the first to review this server!

4.7

Local

MCP Marketplace

Free

by mcp-marketplace · Developer Tools

Search and install MCP servers from inside your AI client.