agentleFS
Sign inStart free
mcpcheckupmcpcheckup/preflight/.cursor/rules/mcp-preflight.mdc

preflight / rules

Cursor rule1 starsChanged 52 days agoApache-2.0View on GitHub

Look up an MCP server on MCP Checkup before adding, recommending, or debugging it.

  • Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.

    Of the Cursor rule files we read, the 4,187 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repositoryOne other file it gives its agents.

The file

We split this mcp-preflight.mdc into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before adding, recommending, or debugging an MCP server, look it up on MCP Checkup (MCP endpoint https://mcpcheckup.com/mcp, no …

    line 8
  2. Very specific:

    Not tracked yet? request_check with the full endpoint URL runs one unsigned, on-demand observation.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
mcp-preflight.mdc
---
description: Look up an MCP server on MCP Checkup before adding, recommending, or debugging it.
alwaysApply: false
---

## MCP servers: look before you connect

Before adding, recommending, or debugging an MCP server, look it up on MCP Checkup (MCP endpoint `https://mcpcheckup.com/mcp`, no authentication; listed in the official MCP Registry as `com.mcpcheckup/mcp`).

- `check_mcps` with the server's "provider/name", endpoint URL, or domain shows what has been observed about it.
- `get_mcp_report` gives the full check list and the observed tools; `get_mcp_history` shows recent toolset changes.
- Not tracked yet? `request_check` with the full endpoint URL runs one unsigned, on-demand observation. It contacts exactly the host you name, so ask the user first.

Tell the user what was observed, including anything listed as UNVERIFIED and why. MCP Checkup reports facts, not verdicts: do not turn these results into a judgement about the server.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free