meloqa-mcp (swl-informatica/meloQA-MCP) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 166 tools. No publisher has claimed this listing.

C
Caution
74/100

meloqa-mcp

Exposes every operation from the meloQA v1 API as MCP tools, enabling LLM clients to read and manage meloQA projects, test cases, cycles, executions, bugs, links, and reference data.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

swl-informatica

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 1 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
// tools this server exposes83 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

bug_environments_list

List environments for a project Tag: Bug Environments

bug_folders_create

Create bug folder Tag: Bug Folders

bug_folders_delete

Delete bug folder Tag: Bug Folders

bug_folders_get

Get bug folder by ID Tag: Bug Folders

bug_folders_list

List bug folders Tag: Bug Folders

bug_folders_update

Update bug folder Tag: Bug Folders

bug_priorities_list

List all bug priority levels Tag: Bug Priorities

bug_statuses_list

List all bug statuses Tag: Bug Statuses

bug_types_list

List bug types for a project Tag: Bug Types

bugs_attachments_create

Create bug attachment (returns presigned upload URL) Tag: Bug Attachments Cria o registro do anexo (uploaded=false) e retorna uma presigned URL S3 (PUT, 300s). Faça o PUT do arquivo na `uploadUrl` e depois confirme com PATCH /v1/bugs/:id/attachments/:attachmentId.

bugs_attachments_delete

Delete bug attachment Tag: Bug Attachments Remove o anexo (registro + arquivo no S3).

bugs_attachments_list

List bug attachments Tag: Bug Attachments Lista os anexos do bug. Itens com `uploaded=true` trazem `downloadUrl` (presigned, 300s).

bugs_attachments_update

Confirm bug attachment upload Tag: Bug Attachments Marca o anexo como enviado (`uploaded=true`) após o PUT no S3.

bugs_create

Create bug Tag: Bugs

bugs_delete

Delete bug Tag: Bugs

bugs_get

Get bug by ID Tag: Bugs

bugs_list

List bugs Tag: Bugs At least one query parameter is required: **projectId** or **folderId**.

bugs_update

Update bug Tag: Bugs

cycle_folders_create

Create cycle folder Tag: Cycle Folders

cycle_folders_delete

Delete cycle folder Tag: Cycle Folders

cycle_folders_get

Get cycle folder by ID Tag: Cycle Folders

cycle_folders_list

List cycle folders Tag: Cycle Folders

cycle_folders_update

Update cycle folder Tag: Cycle Folders

cycle_statuses_list

List all cycle statuses Tag: Cycle Statuses

cycles_create

Create cycle Tag: Cycles

cycles_delete

Delete cycle Tag: Cycles

cycles_get

Get cycle by ID Tag: Cycles

cycles_list

List cycles Tag: Cycles At least one query parameter is required: **projectId** or **folderId**.

cycles_update

Update cycle Tag: Cycles

executions_attachments_create

Create execution attachment (returns presigned upload URL) Tag: Execution Attachments Cria o registro do anexo (uploaded=false) e retorna uma presigned URL S3 (PUT, 300s). Faça o PUT do arquivo na `uploadUrl` e depois confirme com PATCH /v1/executions/:id/attachments/:attachmentId.

executions_attachments_delete

Delete execution attachment Tag: Execution Attachments Remove o anexo (registro + arquivo no S3).

executions_attachments_list

List execution attachments Tag: Execution Attachments Lista os anexos da execução. Itens com `uploaded=true` trazem `downloadUrl` (presigned, 300s).

executions_attachments_update

Confirm execution attachment upload Tag: Execution Attachments Marca o anexo como enviado (`uploaded=true`) após o PUT no S3.

executions_create

Create execution Tag: Executions The `state` field is system-managed and is silently ignored if sent in the body. Use `/v1/executions-run`, `/v1/executions-pause` and `/v1/executions-finish` to drive transitions.

executions_delete

Delete execution Tag: Executions

executions_finish

Finish an execution Tag: Executions Sets the execution state to `DONE` and records `executedAt` and `executedBy`. Allowed only when the current state is `IN_PROGRESS` — returns 400 for `WAITING`, `PAUSED` or `DONE`, when its parent tests cycle is `FINISHED`, or when the execution's `statusId` is s

executions_get

Get execution by ID Tag: Executions

executions_list

List executions Tag: Executions

executions_pause

Pause an execution Tag: Executions Sets the execution state to `PAUSED`. Allowed only when the current state is `IN_PROGRESS` — returns 400 for `WAITING`, `PAUSED` or `DONE`, or when its parent tests cycle is `FINISHED`.

executions_run

Start running an execution Tag: Executions Sets the execution state to `IN_PROGRESS`. Allowed only when the current state is `WAITING` or `PAUSED`. Returns 400 when the execution is already `IN_PROGRESS` or `DONE`, or when its parent tests cycle is `FINISHED`.

executions_update

Update execution Tag: Executions Executions in `state: DONE` are read-only and cannot be updated through this endpoint (public V1 only — the internal API does not enforce this guard). The `state` field itself is system-managed and is silently ignored if sent in the body — use `/v1/executions-run`,

links_batch_create

Link one entity to multiple entities at once Tag: Links Creates one record per target. Operation is atomic — if any record fails, none are created. **Paid-plan only:** free-plan organizations receive 403.

links_create

Create a link between two entities Tag: Links Creates a directional link between two entities. **entityA** is the entity currently open or being edited — its ID is stored in the corresponding foreign key field. **entityB** is the entity being linked to entityA — its type is stored in `type` and i

links_delete

Remove a link Tag: Links **Paid-plan only:** free-plan organizations receive 403.

links_list

List links for an entity Tag: Links Returns all entities linked to the given entity, regardless of which side of the link it was created from. **Example use case:** A user opens a bug and the UI needs to display its linked items panel. Pass `entityType=bug` and `entityId` as the ID of the open bu

location_countries_list

List all location countries Tag: Location Countries

organizations_get

Get organization by ID Tag: Organizations

organizations_list

List organizations Tag: Organizations

organizations_members_list

List members of an organization Tag: Organizations

organizations_update

Update organization Tag: Organizations The `employeeQuantity` field accepts one of the following values: `1 a 10`, `11 a 50`, `51 a 100`, `100+`. Send `null` to clear the value.

project_pictures_list

List available project pictures Tag: Projects

project_platforms_list

List platforms for a project Tag: Project Platforms

projects_create

Create project Tag: Projects Validation rules: - `name` must not exceed 20 characters. - `description` must not exceed 250 characters. - `projectPictureUrl` must reference a project picture predefined by the meloQA API — list the available IDs via `GET /v1/project-pictures`.

projects_delete

Delete project Tag: Projects

projects_execution_statuses_list

List execution statuses available in a project Tag: Projects Returns the execution statuses that can be assigned to executions in this project. Includes both the system-wide defaults (`projectId: null`, `isDefault: true`) and any project-specific statuses created for it. Use the `id` of an entry a

projects_get

Get project by ID Tag: Projects

projects_list

List projects Tag: Projects Returns only projects the authenticated user has effective access to (i.e. is a project member of).

projects_members_list

List members of a project Tag: Projects Returns the active (non-deleted) members of the project. The caller must be a member of the project.

projects_test_case_custom_fields_list

List custom field definitions for test cases of a project Tag: Projects Returns the custom field schema configured for test cases in the project. Use the `id` of each entry as `projectCustomFieldId` when reading or writing test case custom field values.

projects_update

Update project Tag: Projects Validation rules: - `name` must not exceed 20 characters. - `description` must not exceed 250 characters. - `projectPictureUrl` must reference a project picture predefined by the meloQA API — list the available IDs via `GET /v1/project-pictures`.

tags_create

Create tag Tag: Tags

tags_delete

Delete tag Tag: Tags

tags_get

Get tag by ID Tag: Tags

tags_list

List tags Tag: Tags

tags_update

Update tag Tag: Tags

test_case_folders_create

Create test case folder Tag: Test Case Folders Folder hierarchy is limited to **3 sub-levels** below the project root. Creating a folder under a parent that is already at the 3rd sub-level returns 400.

test_case_folders_delete

Delete test case folder Tag: Test Case Folders Removes the folder and hard-deletes every test case it contained, matching the meloQA front-end behavior. Child folders are removed in the same operation.

test_case_folders_get

Get test case folder by ID Tag: Test Case Folders

test_case_folders_list

List test case folders Tag: Test Case Folders

test_case_folders_update

Update test case folder Tag: Test Case Folders When `parentId` is changed, the folder is moved together with its whole subtree. The resulting hierarchy must not exceed **3 sub-levels** below the project root — otherwise the request is rejected with 400.

test_case_statuses_list

List all test case statuses Tag: Test Case Statuses

test_case_types_list

List all test case types Tag: Test Case Types

test_cases_archived_list

List archived test cases Tag: Test Cases Returns only archived test cases (`statusId === ARCHIVED`). At least one of **projectId** or **folderId** is required.

test_cases_attachments_create

Create test case attachment (returns presigned upload URL) Tag: Test Case Attachments Cria o registro do anexo (uploaded=false) e retorna uma presigned URL S3 (PUT, 300s). Faça o PUT do arquivo na `uploadUrl` e depois confirme com PATCH /v1/test-cases/:id/attachments/:attachmentId.

test_cases_attachments_delete

Delete test case attachment Tag: Test Case Attachments Remove o anexo (registro + arquivo no S3).

test_cases_attachments_list

List test case attachments Tag: Test Case Attachments Lista os anexos do test case. Itens com `uploaded=true` trazem `downloadUrl` (presigned, 300s).

test_cases_attachments_update

Confirm test case attachment upload Tag: Test Case Attachments Marca o anexo como enviado (`uploaded=true`) após o PUT no S3.

test_cases_create

Create test case Tag: Test Cases

test_cases_delete

Delete test case Tag: Test Cases

test_cases_get

Get test case by ID Tag: Test Cases

test_cases_list

List test cases Tag: Test Cases At least one query parameter is required: **projectId** or **folderId**. Archived test cases (`statusId === ARCHIVED`) are excluded — use `GET /v1/test-cases/archived` to list those.

test_cases_unarchive

Unarchive test case Tag: Test Cases Restores an archived test case (`statusId === ARCHIVED`) into the folder specified by `folderId`. The status returns to whatever it was before archiving (`statusBeforeId`); when no previous status is recorded the test case falls back to `FINISHED`.

test_cases_update

Update test case Tag: Test Cases Archived test cases (`statusId === ARCHIVED`) are read-only and cannot be updated through this endpoint.

// known CVEs in dependencies1 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.0.4GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configMELOQA_BASE_URLStatus: pre-release. Defaults to the public endpoint https://api.meloqa.com; override to point at another instance (e.g. a local http://localhost:3000).
configMELOQA_RATE_LIMITno 30 Client-side limit (requests/minute) used to throttle outgoing calls. Match the server's limit.
configMELOQA_SPEC_URLnpm run sync-spec # refresh spec/openapi.json from (default http://localhost:3000/v1/docs.json)
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

166/166 tools missing one or more hints — bug_environments_list (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); bug_folders_create (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); bug_folders_delete (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +163 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tests exist

No test files found

Add tests that exercise each declared tool.

Production dependencies are patched

0 critical, 1 high severity in production deps — @modelcontextprotocol/sdk@1.0.4 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Domain consistency

npm scope @meloqa doesn't match GitHub owner swl-informatica

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/swl-informatica/meloqa-mcp?variant=verified)](https://m8ven.ai/mcp/swl-informatica/meloqa-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 8f84e0cd287e85e84f16c0bba6d4833949d6706b
code hash: 83775bb4f9a9160995e9eb1224e3bf31baa8a34cbf508f4d155cd637cc54e7eb
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client