Back to Browse

Helvabase MCP Server

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 Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

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 MCP installer

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.

Install

Use Node.js 20 or newer:

npx --yes github:alopez3006/helvabase-mcp \
  --url https://YOUR-DEPLOYED-HOST/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 this installation surface is public. The private Helvabase source repository syncs it after the corresponding changes land on main.

Reviews

No reviews yet

Be the first to review this server!