MCP Tool Integration · Public

decoy-scan

MCP tool integration project for safely connecting external tools, services, or data sources to an AI host.

MCPTool callingHost configurationPermission boundariesAcceptance checks

Best fitDevelopers who need Claude, Cursor, Codex, or another MCP-capable AI host to call external tools safely.

Check whether this project matches your task before installing it.

What it can doMCP setup guidance, host configuration checks, tool permission boundaries, recovery steps, and acceptance checks

Review the portable capability path.

Before continuingVerify in a sandbox

Do not treat a preview pack as a proven local install.

GitHub snapshot1 stars

0 forks · 1 contributors

Doramagic.ai Last verification date: 2026-07-09 Verification method: source evidence, semantic profile, public page gate, and static build acceptance.

Official first step Read manual preview Source repository

Publication status · 2026-07-09

What is decoy-scan?

decoy-scan helps connect external tools, services, or data sources to AI hosts that support MCP.
Best fit: Developers who need Claude, Cursor, Codex, or another MCP-capable AI host to call external tools safely.
Not for: Not for users who cannot change host configuration, grant tool permissions, or isolate network, file, and credential access.
Capability added to an AI workflow: MCP setup guidance, host configuration checks, tool permission boundaries, recovery steps, and acceptance checks
First safe verification step: Verify the MCP server command, permission scope, and rollback path in a non-primary host configuration first.
Verification state: source, Quick Start, and sandbox install checks are recorded as passed.
Top risk: May increase setup, validation, or first-run risk for the user.
Evidence base: https://github.com/decoy-run/decoy-scan, https://github.com/decoy-run/decoy-scan#readme, Human Manual, Pitfall Log

Quick decision

Use this section to decide whether the project is worth a deeper read.

Best forDevelopers who need Claude, Cursor, Codex, or another MCP-capable AI host to call external tools safely.

Match the project to your task before installing it.

CapabilityMCP setup guidance, host configuration checks, tool permission boundaries, recovery steps, and acceptance checks

MCP tool integration project for safely connecting external tools, services, or data sources to an AI host.

Repositorydecoy-run/decoy-scan

1 stars · 0 forks

What it can do

Translate the upstream project into concrete capabilities the user can judge before installing.

Introduction and Getting Started

Related topics: System Architecture and Source Modules, CLI, GitHub Action, and Library API

Source: https://github.com/decoy-run/decoy-scan / Human Manual

System Architecture and Source Modules

Related topics: Introduction and Getting Started, Security Checks, Patterns, and Detection Rules

Source: https://github.com/decoy-run/decoy-scan / Human Manual

Security Checks, Patterns, and Detection Rules

Related topics: System Architecture and Source Modules, CLI, GitHub Action, and Library API

Source: https://github.com/decoy-run/decoy-scan / Human Manual

CLI, GitHub Action, and Library API

Related topics: Introduction and Getting Started, Security Checks, Patterns, and Detection Rules

Source: https://github.com/decoy-run/decoy-scan / Human Manual

Doramagic Pitfall Log

Source-linked risks stay visible on the manual page so the preview does not read like a recommendation.

Source: Doramagic discovery, validation, and Project Pack records

Sources: https://github.com/decoy-run/decoy-scan, Human Manual, Project Pack evidence, and downstream validation signals.

Community Discussion Evidence

Project-level external discussion stays visible on the detail page, not only inside the manual.

Stars1 stars

Forks0 forks

Contributors1 contributors

Licenseunknown

Community Discussion Evidence

3 source-linked items

Review these external discussions before using decoy-scan with real data or production workflows. They are review inputs, not standalone proof that the project is production-ready.

01
v0.5.8
github / github_release
02
Decoy Scan - MCP Security for CI/CD
github / github_release
03
Configuration risk requires verification
GitHub / issue

How to start

Only source-backed commands are shown here. Verify them in an isolated environment first.

Try the prompt first

Test the workflow without installing the upstream project.

preview

Read the Human Manual

Understand inputs, outputs, limits, and failure modes.

manual

Take context to your AI host

Use the compiled assets in your preferred AI environment.

context

Run sandbox verification

Confirm install commands and rollback before using a primary environment.

verify

npx decoy-scan

Official start command · https://github.com/decoy-run/decoy-scan#readme · verified: yes

Human Manual

The English page must expose the real manual, not a short placeholder.

8+ sections · Human Manual

decoy-scan Manual

Security scanner for MCP server configurations. Like npm audit, but for your AI agent tool servers. Finds risky tools, input validation gaps, transport vulnerabilities, and over-permissioned capability chains. Open source, zero dependencies.

Open the full manual

https://github.com/decoy-run/decoy-scan Project Manual
Table of Contents
Introduction and Getting Started
Related Pages
Purpose and Scope
Prerequisites and Installation
Scan Workflow
Interpreting Output and Exit Codes

Introduction and Getting Started

Related topics: System Architecture and Source Modules, CLI, GitHub Action, and Library API

Source: https://github.com/decoy-run/decoy-scan / Human Manual

System Architecture and Source Modules

Related topics: Introduction and Getting Started, Security Checks, Patterns, and Detection Rules

Source: https://github.com/decoy-run/decoy-scan / Human Manual

Security Checks, Patterns, and Detection Rules

Related topics: System Architecture and Source Modules, CLI, GitHub Action, and Library API

Source: https://github.com/decoy-run/decoy-scan / Human Manual

CLI, GitHub Action, and Library API

Related topics: Introduction and Getting Started, Security Checks, Patterns, and Detection Rules

Source: https://github.com/decoy-run/decoy-scan / Human Manual

Doramagic Pitfall Log

Source-linked risks stay visible on the manual page so the preview does not read like a recommendation.

Source: Doramagic discovery, validation, and Project Pack records

AI Context Pack and portable assets

After deciding to continue, take the project context into your own AI host.

Complete pack plus user-owned assets

These files are planning and verification assets for Claude Code, Codex, Gemini, Cursor, ChatGPT, and other AI hosts.

Download complete pack Read Human Manual

BundleComplete Project Pack AssetAI Context Pack AssetBoundary & Risk Card AssetHuman Manual AssetPitfall Log AssetPrompt Preview AssetQuick Start EvidenceREPO_INSPECTION.json

Preflight checks

Treat this page as a planning asset, not proof that your local environment is ready.

The manual is generated from source-linked project files and Doramagic validation signals.
Community evidence warnings stay visible instead of being converted into marketing claims.
This English page is indexable because the locale quality gate passed and explicit English index approval is enabled.
Use the upstream repository as the final authority for installation commands, license, and version-specific behavior.

Pitfall Log and verification risks

Doramagic surfaces high-risk items before users treat a candidate capability as verified.

medium

Configuration risk requires verification

May increase setup, validation, or first-run risk for the user.

medium

Capability evidence risk requires verification

May increase setup, validation, or first-run risk for the user.

medium

Maintenance risk requires verification

May increase setup, validation, or first-run risk for the user.

medium

Security or permission risk requires verification

May increase setup, validation, or first-run risk for the user.

medium

Security or permission risk requires verification

May increase setup, validation, or first-run risk for the user.

low

Maintenance risk requires verification

May increase setup, validation, or first-run risk for the user.

low

Maintenance risk requires verification

May increase setup, validation, or first-run risk for the user.