# mcpflux check skill

Use this pack to probe an MCP endpoint from **Cursor or Claude Code**, without a hosted mcpflux scan or account. The agent needs network access and MCP/HTTP tools. The checklist is an installed snapshot, not an automatically refreshed ruleset.

For hosted scans and their versioned scores, use [the API prompt](/prompt.md) on the mcpflux check site instead.

## Try it once

The site's **Copy skill + checklist** button copies both instructions and checklist into one self-contained prompt. Paste it into your agent, then include the MCP URL. This runs a one-off check; it does not install a reusable skill.

## Install both files

Keep these files together in a folder named `mcp-connector-check`:

- [SKILL.md](mcp-connector-check/SKILL.md)
- [checklist.md](mcp-connector-check/checklist.md)

Choose a location:

| Agent | This project only | All your projects |
| --- | --- | --- |
| Claude Code | `.claude/skills/mcp-connector-check/` | `~/.claude/skills/mcp-connector-check/` |
| Cursor | `.cursor/skills/mcp-connector-check/` | `~/.cursor/skills/mcp-connector-check/` |

### From a repository checkout

Run from the repository root. For Claude Code in this project:

```sh
mkdir -p .claude/skills
cp -R skills/mcp-connector-check .claude/skills/
```

For Cursor across projects:

```sh
mkdir -p ~/.cursor/skills
cp -R skills/mcp-connector-check ~/.cursor/skills/
```

Use the table above to choose another destination. If updating an existing installation, replace both files together.

Locations follow the [Claude Code skill docs](https://code.claude.com/docs/en/skills) and [Cursor skill docs](https://cursor.com/docs/skills).

### From the website (no clone)

Save both linked files above into the chosen folder, or run the following after replacing the example origin with the site you opened:

```sh
MCP_CHECK_SITE='https://YOUR-MCPFLUX-CHECK-SITE'
MCP_SKILL_DIR='.claude/skills/mcp-connector-check'
mkdir -p "$MCP_SKILL_DIR"
curl --fail --show-error --silent --max-time 30 \
  "$MCP_CHECK_SITE/skills/mcp-connector-check/SKILL.md" \
  -o "$MCP_SKILL_DIR/SKILL.md"
curl --fail --show-error --silent --max-time 30 \
  "$MCP_CHECK_SITE/skills/mcp-connector-check/checklist.md" \
  -o "$MCP_SKILL_DIR/checklist.md"
```

Check that both downloads succeeded before using the skill. Reopen the project or start a new agent session if the installed skill is not discovered.

## Use it

> Use mcp-connector-check to assess https://example.com/mcp for publication in Claude and ChatGPT. Save a Markdown report.

For a custom connection, say **connection readiness** instead of publication. The report includes per-client verdicts, evidence, fixes, tools, and untested/manual items. Auth requirements or probe limits produce an incomplete report; the skill does not execute tools to prove behavior or produce hosted numerical scores.

## Maintaining this pack

`skills/` in the repository is the source of truth. From `frontend/`, run `npm run sync:skills` after editing it. This updates the public copies served at `/skills/`; development/build scripts do this automatically when the repository source is available. `npm run check:skills` verifies the copies match. Frontend-only Docker builds use the already synchronized public files.