MCP.Market

Helvabase — Governed response dossiers MCP server

online · 100% uptime
by helvabase.com·com.helvabase/helvabase·v1.0.0
No reviews yet

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

A97/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A97/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Helvabase — Governed response dossiers yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Helvabase — Governed response dossiers tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 612ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 4 days ago15/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10
Overall 97/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Helvabase — Governed response dossiers compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
97/100
higher than 98% of 48,243 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
89 ms
faster than 86% of 30,027 servers

Install Helvabase — Governed response dossiers in Claude Code, Cursor or VS Code

claude mcp add --transport http helvabase https://helvabase.com/mcp
Add to Cursor

What the publisher says

From the Helvabase — Governed response dossiers repository's README, as published. We do not edit it. Read it on GitHub

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.

Nothing above is checked by us. What we check is on the safety report.

Helvabase — Governed response dossiers: common questions

Is Helvabase — Governed response dossiers MCP server safe?
Yes, by our scan: it is graded A (97/100). Read the Helvabase — Governed response dossiers safety report
How do I install Helvabase — Governed response dossiers?
It runs remotely at helvabase.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Helvabase — Governed response dossiers need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is Helvabase — Governed response dossiers maintained?
The last commit was 37 days ago (2026-09-29). The latest release is v1.0.0.
Is Helvabase — Governed response dossiers up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Helvabase — Governed response dossiers compare with other MCP servers?
safety score 97/100 (higher than 98% of 48,243 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 89 ms (faster than 86% of 30,027 servers). Full comparison.