io.github.acabala/apidog-tests-mcp

MCPcommunity
v0.0.5io.github.acabalaUnknownUpdated 7mo agonpmGitHub

MCP server for managing Apidog test cases, scenarios, suites, and test data

MCP (Model Context Protocol) server for managing Apidog test cases, scenarios, suites, and test data. Gives AI assistants full read/write access to Apidog's test management features. This project is not an official Apidog integration. Test Cases -- Create, read, update, delete, and bulk-create test cases for API endpoints Test Scenarios -- Build multi-step test flows chaining multiple API calls…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1GitHub stars
1Forks
7mo agoLast update
Package
Authorio.github.acabala
LicenseUnknown
Version0.0.5
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface30 tools · 5 privileged
Security scan✓ Cleanv0.0.5 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

30 tools · 5 privileged
Statically extracted from the published packagev0.0.5 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

create_scenario_folderNo description published

This tool published no description. Forge does not invent one.

delete_scenario_folderprivilegedNo description published

This tool published no description. Forge does not invent one.

create_suite_folderNo description published

This tool published no description. Forge does not invent one.

list_environmentsNo description published

This tool published no description. Forge does not invent one.

list_api_endpointsNo description published

This tool published no description. Forge does not invent one.

list_test_case_categoriesNo description published

This tool published no description. Forge does not invent one.

list_test_case_tagsNo description published

This tool published no description. Forge does not invent one.

list_runnersNo description published

This tool published no description. Forge does not invent one.

get_endpoint_statisticsNo description published

This tool published no description. Forge does not invent one.

list_test_casesNo description published

This tool published no description. Forge does not invent one.

get_test_caseNo description published

This tool published no description. Forge does not invent one.

create_test_caseNo description published

This tool published no description. Forge does not invent one.

create_test_cases_bulkNo description published

This tool published no description. Forge does not invent one.

update_test_caseNo description published

This tool published no description. Forge does not invent one.

delete_test_caseprivilegedNo description published

This tool published no description. Forge does not invent one.

list_test_dataNo description published

This tool published no description. Forge does not invent one.

get_test_dataNo description published

This tool published no description. Forge does not invent one.

create_test_dataNo description published

This tool published no description. Forge does not invent one.

update_test_dataNo description published

This tool published no description. Forge does not invent one.

delete_test_dataprivilegedNo description published

This tool published no description. Forge does not invent one.

list_test_scenariosNo description published

This tool published no description. Forge does not invent one.

get_test_scenario_stepsNo description published

This tool published no description. Forge does not invent one.

create_test_scenarioNo description published

This tool published no description. Forge does not invent one.

update_test_scenario_stepsNo description published

This tool published no description. Forge does not invent one.

delete_test_scenarioprivilegedNo description published

This tool published no description. Forge does not invent one.

list_test_suitesNo description published

This tool published no description. Forge does not invent one.

get_test_suiteNo description published

This tool published no description. Forge does not invent one.

create_test_suiteNo description published

This tool published no description. Forge does not invent one.

update_test_suite_itemsNo description published

This tool published no description. Forge does not invent one.

delete_test_suiteprivilegedNo description published

This tool published no description. Forge does not invent one.

0 of 30 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP (Model Context Protocol) server for managing Apidog test cases, scenarios, suites, and test data. Gives AI assistants full read/write access to Apidog's test management features. This project is not an official Apidog integration. Test Cases -- Create, read, update, delete, and bulk-create test cases for API endpoints Test Scenarios -- Build multi-step test flows chaining multiple API calls Test Suites -- Organize tests into runnable suites for CI/CD Test Data -- Manage data-driven test…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.

Topics

Related in testing & ci