io.github.meridian-silkdev/meridian-mcp
NPM · @MERIDIANTOOLKIT/MCP
MCP server for Meridian: services, requests, workflow, payments, meetings for founders.
Available components
Last scanned (3 hours ago)
Scores higher than 93% of npm servers
Category Workflow Automation
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to meridian-silkdev/meridian-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 61 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1010 tokens (~56/item across 18 items; 16 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 61% 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 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 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
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.
- 5 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 1 Nov 26 0
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 31 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.97 functional
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Stability: pass → 0.97 functional
- 18 Oct 26 0
- Stability: 0.97 → pass security
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Analysed npm/@meridiantoolkit/mcp@0.1.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | meridian-silkdev/meridian-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/meridian-silkdev/meridian-mcp/.github/workflows/publish.yml@refs/tags/v0.1.2 |
| Rekor log index | 2712365509 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:dec69b3ab800467f6bb7cd106d03cd48d9277f7254b894ba0be0c2f49c4766ad6f78acfad1d74e37ae0864c28b6b98a054ea98cf45b1755ec03e69f83 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
advance_step ~64
Advance the current step for a request to the next step (completes current step and moves currentStepId). Validates phase transitions.
| Name | Type | Req | Description |
|---|---|---|---|
| requestId | string | yes | – |
| stepId | string | – | Optional: specific step id to complete (defaults to current step) |
No output schema declared.
No examples provided.
create_meeting ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| duration | number | yes | Minutes |
| inviteCustomer | boolean | – | – |
| inviteProvider | boolean | – | – |
| scheduledAt | string | yes | ISO 8601 datetime |
| serviceRequestId | string | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
create_service_request ~71
Create a new service request. Needs serviceId (or slug) and answers matching the service formConfig.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | – | Form answers keyed by field name |
| customTitle | string | – | Optional custom title for ad-hoc requests |
| serviceId | string | yes | Service id or slug |
No output schema declared.
No examples provided.
get_payment_status ~51
Get payment state for a service request (Payment row: amount, status, provider, serviceRequestId unique). Returns verification status — never trust redirect alone.
| Name | Type | Req | Description |
|---|---|---|---|
| requestId | string | yes | ServiceRequest id |
No output schema declared.
No examples provided.
get_service ~38
Get a single Meridian service by id or slug, including formConfig and delivery steps.
| Name | Type | Req | Description |
|---|---|---|---|
| idOrSlug | string | yes | Service id or slug |
No output schema declared.
No examples provided.
get_service_request ~37
Get a single service request by id, including current step, phase, and requestSteps.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | ServiceRequest id |
No output schema declared.
No examples provided.
get_workflow_status ~62
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.
| Name | Type | Req | Description |
|---|---|---|---|
| requestId | string | yes | ServiceRequest id |
No output schema declared.
No examples provided.
list_categories ~28
List Meridian service categories (name, slug, icon, isActive, sortOrder, countryCode).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_meetings ~73
List meetings. Filter by serviceRequestId, status, or participant userId. Meetings are created with a fixed title/time/duration and explicit invites (customer/provider/both).
| Name | Type | Req | Description |
|---|---|---|---|
| serviceRequestId | string | – | – |
| status | string | – | SCHEDULED | IN_PROGRESS | COMPLETED | CANCELLED |
No output schema declared.
No examples provided.
list_request_steps ~46
List all RequestSteps for a request in order, including key, phase, assignedTo, stepType, status, startedAt, completedAt.
| Name | Type | Req | Description |
|---|---|---|---|
| requestId | string | yes | – |
No output schema declared.
No examples provided.
list_service_requests ~101
List service requests. Filter by status (DRAFT, REQUIREMENTS, ADMIN_VALIDATION, PROVIDER_ACCEPTANCE, QUOTE, PAYMENT, DELIVERY, FULFILLMENT, COMPLETED, DISPUTED, CANCELLED), customerId, providerId.
| Name | Type | Req | Description |
|---|---|---|---|
| customerId | string | – | – |
| limit | number | – | Max results (default 20) |
| providerId | string | – | – |
| status | string | – | ServiceRequestStatus filter |
No output schema declared.
No examples provided.
list_services ~78
List Meridian services. Filter by category slug, active flag, or country code (e.g. TN, FR, PT).
| Name | Type | Req | Description |
|---|---|---|---|
| categorySlug | string | – | Filter by category slug |
| countryCode | string | – | ISO 3166-1 alpha-2, e.g. TN |
| isActive | boolean | – | Only active services |
No output schema declared.
No examples provided.
meridian_status ~35
Check Meridian API connectivity (MERIDIAN_API_URL + MERIDIAN_API_KEY) and list available tools/resources. No params.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
respond_to_meeting ~53
Record RSVP for a meeting (ACCEPTED/DECLINED/PENDING). Declining records your answer but does NOT cancel the meeting.
| Name | Type | Req | Description |
|---|---|---|---|
| meetingId | string | yes | – |
| response | string | yes | – |
No output schema declared.
No examples provided.
update_request_status ~67
Advance or set a request's status. Prefer advance_step for workflow transitions. Use only when you know the target phase is valid.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | ServiceRequest id |
| reason | string | – | Optional reason/note |
| status | string | yes | Target ServiceRequestStatus |
No output schema declared.
No examples provided.
verify_payment ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| paymentId | string | – | Payment id or provider transaction id |
| requestId | string | yes | – |
No output schema declared.
No examples provided.
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.
npm · @meridiantoolkit/mcp
claude mcp add meridian-silkdev-meridian-mcp -- npx -y @meridiantoolkit/mcp
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 90 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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 5 November 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.