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.KNambiarDJsc/meridian-mcp

PYPI · MERIDIAN-MCP · SCANNED SEP 24

Local-first compliance scanner for DPDPA 2023/2025, RBI FREE-AI, SEBI AI/ML & EU AI Act.

Available components

0 this week 0 Trust /100

Recent critical change

CVE-2026-32871 affects this package (4 Aug 2026). See the changelog before you install this server.

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 Security25
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 32 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 522 tokens (~87/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
Install

How do I install the io.github.KNambiarDJsc/meridian-mcp server?

io.github.KNambiarDJsc/meridian-mcp runs locally as a PyPI package, launched with uvx meridian-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · meridian-mcp

# add to Claude Code
claude mcp add knambiardjsc-meridian-mcp -- uvx meridian-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "knambiardjsc-meridian-mcp": {
      "command": "uvx",
      "args": [
        "meridian-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "knambiardjsc-meridian-mcp": {
      "command": "uvx",
      "args": [
        "meridian-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add knambiardjsc-meridian-mcp -- uvx meridian-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "knambiardjsc-meridian-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "meridian-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add knambiardjsc-meridian-mcp --command uvx --arg meridian-mcp
# ~/.hermes/config.yaml
mcp_servers:
  knambiardjsc-meridian-mcp:
    command: "uvx"
    args: ["meridian-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "knambiardjsc-meridian-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "meridian-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add knambiardjsc-meridian-mcp -t stdio -c uvx -a meridian-mcp
// mcp.json
{
  "mcpServers": {
    "knambiardjsc-meridian-mcp": {
      "command": "uvx",
      "args": [
        "meridian-mcp"
      ]
    }
  }
}
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.

  • 18 Sept 26 0
    • Malware scan: pass → unverified ▼ security
    • Stability: pass → 0.77 functional
  • 17 Sept 26 0
    • Malware scan: unverified → pass ▲ security
    • Stability: 0.97 → pass security
  • 14 Sept 26 0
    • Malware scan: pass → unverified ▼ security
  • 13 Sept 26 0
    • Malware scan: unverified → pass ▲ security
  • 12 Sept 26 0
    • Malware scan: pass → unverified ▼ security
  • 11 Sept 26 0
    • Stability: pass → 0.80 functional
  • 10 Sept 26 0
    • Stability: 0.97 → pass security
  • 4 Sept 26 0
    • Stability: pass → 0.80 functional
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 24 Sept 2026 · Analysed pypi/meridian-mcp@0.3.3

Provenance No attestation

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

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Vulnerabilities 6 findings
ID CVE Severity Vector Fix available
GHSA-m8x7-r2rg-vh5g CVE-2025-64340 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H yes
GHSA-rww4-4w9c-7733 CVE-2026-27124 high yes
GHSA-vv7q-7jx5-f767 CVE-2026-32871 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H yes
PYSEC-2026-2475 CVE-2025-64340 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H yes
PYSEC-2026-2476 CVE-2026-27124 none yes
PYSEC-2026-338 CVE-2026-32871 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 111 packages
Packages resolved 111
Stale 8
No linked repository 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~458 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
cache_status ~46

Show or clear the Meridian local scan cache (~/.meridian/cache.db). Args: clear: If True, wipe all cached results. Default False.

NameTypeReqDescription
clearboolean––
NameTypeReqDescription
resultstringyes–

No examples provided.

check_health ~18

Verify Meridian MCP server is running and correctly configured.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

evaluate_policy ~103

Check a policy document, privacy policy, or model card for compliance gaps. Args: policy_text: Full text of the policy document. frameworks: Comma-separated. Free: dpdpa. Pro: rbi, eu, sebi, all. source_label: Label for the document (e.g. 'privacy_policy_v3').

NameTypeReqDescription
frameworksstring––
policy_textstringyes–
source_labelstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

explain_violation ~84

Get a plain-English explanation of any regulatory clause. Args: statutory_clause: e.g. "DPDPA §6(1)", "RBI FREE-AI Rec 23", "SEBI §5.1(h)" context: Optional description of your system for tailored advice.

NameTypeReqDescription
contextstring––
statutory_clausestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

scan_repository ~155

Scan a local repository for AI compliance violations. Args: path: Absolute or relative path to the repository root. frameworks: Comma-separated. Free: dpdpa. Pro: rbi, eu, sebi, all. max_files: Max files to scan (default 40, max 150). Returns: Markdown compliance report with violations, line numbers, regulatory citations, and remediation steps. LLM model used is configured via MERIDIAN_EVALUATOR_MODEL env var. API key is read from the provider's standard env var (e.g. ANTHROPIC_API_KEY).

NameTypeReqDescription
frameworksstring––
max_filesinteger––
pathstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

show_models ~52

Show all supported LLM providers and models, and how to configure them. Returns the full model catalogue with env var configuration instructions. API keys are always user-owned — Meridian reads them from your env, never stores them.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

Common questions

What is the io.github.KNambiarDJsc/meridian-mcp server?

io.github.KNambiarDJsc/meridian-mcp is listed in the public MCP registry as io.github.KNambiarDJsc/meridian-mcp. Local-first compliance scanner for DPDPA 2023/2025, RBI FREE-AI, SEBI AI/ML & EU AI Act. This page covers its PyPI package (meridian-mcp).

What tools does the io.github.KNambiarDJsc/meridian-mcp server expose?

io.github.KNambiarDJsc/meridian-mcp exposes 6 tools: scan_repository, evaluate_policy, explain_violation, show_models, check_health, cache_status. Their descriptions and schemas cost roughly 458 tokens of context every time the server is loaded.

Is the io.github.KNambiarDJsc/meridian-mcp server still maintained?

io.github.KNambiarDJsc/meridian-mcp is still listed as active in the MCP registry. We last reached this channel on 24 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.KNambiarDJsc/meridian-mcp server under?

io.github.KNambiarDJsc/meridian-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.