# io.github.meridian-silkdev/meridian-mcp (npm · @meridiantoolkit/mcp)

MCP server for Meridian: services, requests, workflow, payments, meetings for founders.

- Trust score: 89/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `@meridiantoolkit/mcp`: 89/100 (this document), [markdown](https://verifymcp.io/servers/meridian-silkdev-meridian-mcp/meridiantoolkit-mcp.md), [page](https://verifymcp.io/servers/meridian-silkdev-meridian-mcp/meridiantoolkit-mcp)

## Channel facts

- Registry: `npm`
- Package: `@meridiantoolkit/mcp`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 97 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to meridian-silkdev/meridian-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 15 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1010 tokens (~56/item across 18 items; 16 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 61% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

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

### Claude

```bash
claude mcp add meridian-silkdev-meridian-mcp -- npx -y @meridiantoolkit/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "meridian-silkdev-meridian-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@meridiantoolkit/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "meridian-silkdev-meridian-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@meridiantoolkit/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add meridian-silkdev-meridian-mcp -- npx -y @meridiantoolkit/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "meridian-silkdev-meridian-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@meridiantoolkit/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add meridian-silkdev-meridian-mcp --command npx --arg -y --arg @meridiantoolkit/mcp
```

### Hermes

```yaml
mcp_servers:
  meridian-silkdev-meridian-mcp:
    command: "npx"
    args: ["-y", "@meridiantoolkit/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "meridian-silkdev-meridian-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@meridiantoolkit/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add meridian-silkdev-meridian-mcp -t stdio -c npx -a -y @meridiantoolkit/mcp
```

### Other

```json
{
  "mcpServers": {
    "meridian-silkdev-meridian-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@meridiantoolkit/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 89, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 85, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-04 (score 81)

First indexed and scored.

## MCP tools (16)

### `meridian_status` (~35 tokens)

Check Meridian API connectivity (MERIDIAN_API_URL + MERIDIAN_API_KEY) and list available tools/resources. No params.

### `list_services` (~78 tokens)

List Meridian services. Filter by category slug, active flag, or country code (e.g. TN, FR, PT).

Input parameters:

- `categorySlug` (string): Filter by category slug
- `countryCode` (string): ISO 3166-1 alpha-2, e.g. TN
- `isActive` (boolean): Only active services

### `get_service` (~38 tokens)

Get a single Meridian service by id or slug, including formConfig and delivery steps.

Input parameters:

- `idOrSlug` (string, required): Service id or slug

### `list_categories` (~28 tokens)

List Meridian service categories (name, slug, icon, isActive, sortOrder, countryCode).

### `list_service_requests` (~101 tokens)

List service requests. Filter by status (DRAFT, REQUIREMENTS, ADMIN_VALIDATION, PROVIDER_ACCEPTANCE, QUOTE, PAYMENT, DELIVERY, FULFILLMENT, COMPLETED, DISPUTED, CANCELLED), customerId, providerId.

Input parameters:

- `customerId` (string)
- `limit` (number): Max results (default 20)
- `providerId` (string)
- `status` (string): ServiceRequestStatus filter

### `get_service_request` (~37 tokens)

Get a single service request by id, including current step, phase, and requestSteps.

Input parameters:

- `id` (string, required): ServiceRequest id

### `create_service_request` (~71 tokens)

Create a new service request. Needs serviceId (or slug) and answers matching the service formConfig.

Input parameters:

- `answers` (object): Form answers keyed by field name
- `customTitle` (string): Optional custom title for ad-hoc requests
- `serviceId` (string, required): Service id or slug

### `update_request_status` (~67 tokens)

Advance or set a request's status. Prefer advance_step for workflow transitions. Use only when you know the target phase is valid.

Input parameters:

- `id` (string, required): ServiceRequest id
- `reason` (string): Optional reason/note
- `status` (string, required): Target ServiceRequestStatus

### `get_workflow_status` (~62 tokens)

Get the workflow state for a request: current phase, current step, and all requestSteps with status (PENDING/IN_PROGRESS/COMPLETED). Status is derived from currentStepId → phase.

Input parameters:

- `requestId` (string, required): ServiceRequest id

### `advance_step` (~64 tokens)

Advance the current step for a request to the next step (completes current step and moves currentStepId). Validates phase transitions.

Input parameters:

- `requestId` (string, required)
- `stepId` (string): Optional: specific step id to complete (defaults to current step)

### `list_request_steps` (~46 tokens)

List all RequestSteps for a request in order, including key, phase, assignedTo, stepType, status, startedAt, completedAt.

Input parameters:

- `requestId` (string, required)

### `get_payment_status` (~51 tokens)

Get payment state for a service request (Payment row: amount, status, provider, serviceRequestId unique). Returns verification status — never trust redirect alone.

Input parameters:

- `requestId` (string, required): ServiceRequest id

### `verify_payment` (~71 tokens)

Verify a payment with the provider (Flouci for Tunisia — local wallet/card — or Stripe for international cards). Triggers server-side verification — redirect back to the portal alone is never proof of payment.

Input parameters:

- `paymentId` (string): Payment id or provider transaction id
- `requestId` (string, required)

### `list_meetings` (~73 tokens)

List meetings. Filter by serviceRequestId, status, or participant userId. Meetings are created with a fixed title/time/duration and explicit invites (customer/provider/both).

Input parameters:

- `serviceRequestId` (string)
- `status` (string): SCHEDULED | IN_PROGRESS | COMPLETED | CANCELLED

### `create_meeting` (~105 tokens)

Create a meeting with title, scheduledAt (ISO), duration minutes, optional serviceRequestId, and invite selection (customer/provider). Creates Teams meeting via Graph and sends invites immediately.

Input parameters:

- `description` (string)
- `duration` (number, required): Minutes
- `inviteCustomer` (boolean)
- `inviteProvider` (boolean)
- `scheduledAt` (string, required): ISO 8601 datetime
- `serviceRequestId` (string)
- `title` (string, required)

### `respond_to_meeting` (~53 tokens)

Record RSVP for a meeting (ACCEPTED/DECLINED/PENDING). Declining records your answer but does NOT cancel the meeting.

Input parameters:

- `meetingId` (string, required)
- `response` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/meridian-silkdev-meridian-mcp/meridiantoolkit-mcp#diagnostics

## Score history

- 2026-09-20: 89
- 2026-09-19: 88
- 2026-09-18: 88
- 2026-09-17: 87
- 2026-09-16: 87
- 2026-09-15: 86
- 2026-09-14: 86
- 2026-09-13: 85
- 2026-09-12: 85
- 2026-09-11: 81
- 2026-09-10: 81
- 2026-09-09: 81
- 2026-09-08: 81
- 2026-09-07: 81
- 2026-09-06: 81
- 2026-09-05: 81
- 2026-09-04: 81

## Common questions

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

io.github.meridian-silkdev/meridian-mcp is listed in the public MCP registry as io.github.meridian-silkdev/meridian-mcp. MCP server for Meridian: services, requests, workflow, payments, meetings for founders. This page covers its npm package (@meridiantoolkit/mcp).

### Is the io.github.meridian-silkdev/meridian-mcp server safe to use?

io.github.meridian-silkdev/meridian-mcp scores 89 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. Its build provenance is signed and verified. 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.meridian-silkdev/meridian-mcp server expose?

io.github.meridian-silkdev/meridian-mcp exposes 16 tools: meridian_status, list_services, get_service, list_categories, list_service_requests, and 11 more. Their descriptions and schemas cost roughly 980 tokens of context every time the server is loaded.

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

io.github.meridian-silkdev/meridian-mcp 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.meridian-silkdev/meridian-mcp server under?

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

## Links

- npm package: https://www.npmjs.com/package/@meridiantoolkit/mcp
- Socket report: https://socket.dev/npm/package/@meridiantoolkit/mcp
- Repository: https://github.com/meridian-silkdev/meridian-mcp
- Changelog RSS feed: https://verifymcp.io/servers/meridian-silkdev-meridian-mcp/meridiantoolkit-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/meridian-silkdev-meridian-mcp/meridiantoolkit-mcp.json
- HTML version of this page: https://verifymcp.io/servers/meridian-silkdev-meridian-mcp/meridiantoolkit-mcp