MCP.Market

Invigil MCP server

by invigil·io.github.invigil/invigil·v1.7.1·1 stars
No reviews yet

Linters check your code. Invigil checks whether your repo is legible — to newcomers and AI agents.

A91/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A91/100

full report

Adoption
Growing

1 stars28 downloads/wk

Reviews

Write one

Nobody has reviewed Invigil yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Invigil tools (3, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • check_groupwrite action

    Run one check group offline (fast). Groups: ai, doors, errors, evidence, layout, secrets, supply-chain.

  • evaluate_repo

    Score a repo against the quality doctrine. `format` is "llm" (one line per finding, each with a fix) or "json" (full scorecard).

  • preview_fixes

    List the file mutations `invigil --fix` would apply, without writing anything. Apply them with your own edit tools, then re-run evaluate_repo.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • Code scan39 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 3 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Invigil compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 85% of 48,255 servers
Tools
3
the typical server has 7
Tools that change things
33%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
1
more than 65% of 28,688 servers
Downloads a week
28
more than 15% of 12,191 servers with a package

What its tools let an agent do: 1 read · 1 change · 1 run or deploy

Install Invigil in Claude Code, Cursor or VS Code

claude mcp add invigil -- uvx invigil
Add to Cursor

What the publisher says

From the Invigil repository's README, as published. We do not edit it. Read it on GitHub

Invigil

Linters check your code. Invigil checks whether your project is legible.

Ruff has your syntax. Dependabot has your dependencies. Scorecard has your supply chain. Nothing checks whether someone arriving cold can act on the project: boot it in ten minutes, get an error that tells them the fix, install the thing from PyPI today, read a README that's still a landing page and not a 600-line wall.

That's the test every project takes when someone new finds it — a new engineer, or increasingly an AI agent with a context window instead of patience. If they can't reach "hello world" in 10 minutes, they leave. If the published artifact is broken because CI only tests the source tree, they leave. If the error is a silent stack trace, they leave. Nobody files an issue on the way out.

Invigil turns those promises into mechanical checks, runs them in CI, and prints the exact fix for every failure — so the project speaks for itself.

invigilate — to watch over an exam and enforce its rules.

How Invigil fits in your stack

Invigil does not replace your existing tools; it covers the product-quality gaps they leave behind.

Why

You already wrote the doctrine; you just enforce it by hand. Every failing Invigil check tells you what's wrong, why it matters, and the exact command to fix it — because a gate that can't tell you how to pass it is the same broken-error-message anti-pattern it's meant to catch.

It grades against seven Gates, each a legibility promise to a different cold-start reader:

A repo reaches Gn only when every mandatory check for gates ≤ n passes, and gets a letter grade from its weighted score.

Install

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Invigil: common questions

Is Invigil MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the Invigil safety report
How do I install Invigil?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Invigil need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Invigil maintained?
The last commit was 44 days ago (2026-09-21). The latest release is v1.7.1.
What can I use instead of Invigil?
Servers from other publishers that do the same job: Contact Affordance MCP server and Business Contact Finder MCP server.
How does Invigil compare with other MCP servers?
safety score 91/100 (higher than 85% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Invigil

Same job from other publishers: the closest match first, then the best rated.

  • Contact Affordance
    Check how to contact a business website, and whether that contact path actually works.
    A
  • Business Contact Finder
    Check how to contact a business website, and whether that contact path actually works.
    A