Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.felixbaumannkontakt-tech/nexora

NPM · @LIVERELAYGROUP/NEXORA-MCP-SERVER · SCANNED SEP 20

NEXORA: Tools fuer Vertrieb, Website-Verwaltung und Holding-Verwaltung (LiveRelay Group).

69 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (ISC).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 397 tokens (~44/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 71% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the io.github.felixbaumannkontakt-tech/nexora MCP server?

io.github.felixbaumannkontakt-tech/nexora runs locally as an npm package, launched with npx -y @liverelaygroup/nexora-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @liverelaygroup/nexora-mcp-server

# add to Claude Code
claude mcp add felixbaumannkontakt-tech-nexora -- npx -y @liverelaygroup/nexora-mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "felixbaumannkontakt-tech-nexora": {
      "command": "npx",
      "args": [
        "-y",
        "@liverelaygroup/nexora-mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "felixbaumannkontakt-tech-nexora": {
      "command": "npx",
      "args": [
        "-y",
        "@liverelaygroup/nexora-mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add felixbaumannkontakt-tech-nexora -- npx -y @liverelaygroup/nexora-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "felixbaumannkontakt-tech-nexora": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@liverelaygroup/nexora-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add felixbaumannkontakt-tech-nexora --command npx --arg -y --arg @liverelaygroup/nexora-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  felixbaumannkontakt-tech-nexora:
    command: "npx"
    args: ["-y", "@liverelaygroup/nexora-mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "felixbaumannkontakt-tech-nexora": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@liverelaygroup/nexora-mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add felixbaumannkontakt-tech-nexora -t stdio -c npx -a -y @liverelaygroup/nexora-mcp-server
// mcp.json
{
  "mcpServers": {
    "felixbaumannkontakt-tech-nexora": {
      "command": "npx",
      "args": [
        "-y",
        "@liverelaygroup/nexora-mcp-server"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 69

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/@liverelaygroup/nexora-mcp-server@1.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~397 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
add_company ~28

Legt eine Firma der Holding im Register an.

NameTypeReqDescription
namestringyesName der Firma

No output schema declared.

No examples provided.

add_company_note ~53

Fuegt einer Firma eine Notiz hinzu (z. B. Status-Update, Aufgabe, Ereignis).

NameTypeReqDescription
idstringyesDie ID der Firma
notestringyesDer Notiztext

No output schema declared.

No examples provided.

add_lead ~77

Fuegt einen neuen Lead hinzu (z. B. ein Unternehmen ohne/mit schlechter Website, gefunden ueber Google Maps).

NameTypeReqDescription
companystringyesName des Unternehmens
notesstringOptionale Notiz zum Lead
sourcestringyesWoher der Lead kommt, z. B. 'Google Maps'

No output schema declared.

No examples provided.

add_project ~71

Legt ein neues Website-/Webapp-Projekt fuer einen Kunden an (Start: Status 'mockup').

NameTypeReqDescription
clientstringyesName des Kunden/Unternehmens
notesstring
pricenumberVereinbarter Preis in Euro
typestringyes

No output schema declared.

No examples provided.

list_companies ~19

Listet alle registrierten Firmen der Holding auf.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_leads ~21

Listet alle bisher erfassten Leads mit Status auf.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_projects ~21

Listet alle Website-/Webapp-Projekte mit Status auf.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

update_lead_status ~51

Aktualisiert den Status eines Leads (neu, email_gesendet, angerufen, termin, gewonnen, verloren).

NameTypeReqDescription
idstringyesDie ID des Leads
statusstringyes

No output schema declared.

No examples provided.

update_project_status ~56

Aktualisiert den Status eines Projekts (mockup, warten_auf_freigabe, rechnung_gestellt, bezahlt, abgeschlossen).

NameTypeReqDescription
idstringyesDie ID des Projekts
statusstringyes

No output schema declared.

No examples provided.

Common questions

What is the io.github.felixbaumannkontakt-tech/nexora MCP server?

io.github.felixbaumannkontakt-tech/nexora is an MCP server listed in the public MCP registry as io.github.felixbaumannkontakt-tech/nexora. NEXORA: Tools fuer Vertrieb, Website-Verwaltung und Holding-Verwaltung (LiveRelay Group). This page covers its npm package (@liverelaygroup/nexora-mcp-server).

Is the io.github.felixbaumannkontakt-tech/nexora MCP server safe to use?

io.github.felixbaumannkontakt-tech/nexora scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.felixbaumannkontakt-tech/nexora MCP server expose?

io.github.felixbaumannkontakt-tech/nexora exposes 9 tools: add_lead, list_leads, update_lead_status, add_project, list_projects, and 4 more. Their descriptions and schemas cost roughly 397 tokens of context every time the server is loaded.

Is the io.github.felixbaumannkontakt-tech/nexora MCP server still maintained?

io.github.felixbaumannkontakt-tech/nexora is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.felixbaumannkontakt-tech/nexora MCP server under?

io.github.felixbaumannkontakt-tech/nexora declares the ISC licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.