Note · 2026-11-04
How We Licence-Check an MCP Server Before Listing It
Before an MCP server joins our catalog, we ask three questions: is there a licence file, what does it forbid beyond internal use, and did it change lately?
Short answer: we ask three questions of every repo before it goes in the catalog. Is there a licence file at all? What does that licence forbid beyond internal use? And did the licence change at the last tagged release? If any answer is unclear, the tool waits.
Talk to us about a build · +1 224-256-7011
Last updated: November 2, 2026. Licence terms change; check the repo before you rely on this.
Why does an MCP server need a licence check at all?
An MCP server is code you run next to real client systems. If it's popular, it's easy to assume it's free to use however you like. That assumption is where agencies get into trouble.
GitHub's own documentation is blunt about the default: without a license, the default copyright laws apply, meaning the author keeps all rights and no one may reproduce, distribute or create derivative works. Choose a License says the same thing: a creative work, code included, is under exclusive copyright by default. A public repo is visible, not permitted.
For a catalog that credits every tool, "we found it on GitHub" isn't a licence.
Question 1: Is there a licence file, and what is it?
We open the repo root and look for LICENSE, LICENSE.md or COPYING, then match it against the SPDX License List so we're using the standard identifier, not a guess from the README badge.
What we record:
- The SPDX identifier (for example
MIT,Apache-2.0,AGPL-3.0-only). - Whether it's OSI-approved. The Open Source Initiative's licence list is the reference. Not every licence that says "source available" is open source.
- Where the licence lives. If the package registry metadata and the repo file disagree, the repo file wins and we flag the mismatch.
No licence file means the server doesn't enter the catalog. We may still read it to learn from it, but we don't run it on client work.
Question 2: What does it forbid beyond internal use?
Internal use is usually the easy case. The questions that matter for an agency are about what happens when the tool touches client work:
- Can we run it for a client? Some source-available licences allow internal business use but limit offering the software to others as a service.
- Can we host it and give a client access? Network-use clauses, like the one in the AGPL, can bring obligations when users interact with the software over a network.
- Can we modify it and keep the changes private? Copyleft licences may require sharing changes under some conditions.
- Is production use allowed at all? The Business Source License 1.1, for example, grants non-production use by default and lets the licensor add an "Additional Use Grant" that permits limited production use. The grant text is what tells you whether your use is covered.
We write the answer as one plain sentence per question in the catalog entry. If we can't answer a question from the licence text itself, the entry says so instead of guessing. We're not lawyers, and for anything ambiguous on a client contract we ask one.
We cover a real example of this, n8n's fair-code licence, on our n8n tool page.
Question 3: What changed at the last tagged release?
Licences change. A project can move from a permissive licence to a source-available one between versions, and the BSL itself is written so the terms apply per version, with a Change Date that can differ for each release.
So we check three things:
- The licence at the tag we actually run, not just the default branch today.
- The commit history of the licence file, to see whether and when it changed.
- The release notes around that change, for any note about commercial use.
We pin the version in the catalog entry next to the licence. If we upgrade, the licence check runs again.
What does a catalog entry look like after the check?
Each entry carries the same short block:
| Field | Example of what we fill in |
|---|---|
| Licence (SPDX) | The identifier from the repo file |
| OSI-approved | Yes, no, or not listed |
| Client use | One sentence from the licence text |
| Hosted access for clients | One sentence, or "unclear, not offered" |
| Version checked | The tag and the date we checked |
That block is the credit and the guardrail at the same time. It tells the author's licence apart from our opinion about the tool, and it keeps the date visible so stale checks are easy to spot.
Common mistakes
- Trusting the README badge. Badges go stale. Read the licence file at the tag you run.
- Treating "open source" and "source available" as the same thing. Check the OSI list.
- Checking once. A licence check is tied to a version, not to the project forever.
- Ignoring dependencies. A permissive server can pull in a package with stricter terms. For anything we host, we look at the main dependencies too.
FAQ
Is a public GitHub repo free to use? Not by default. Without a licence, the author keeps all rights. Visibility isn't permission.
Is MIT or Apache-2.0 enough for client work? Both are permissive and OSI-approved, and they generally allow commercial use. You still need to keep the copyright and licence notices they ask for.
What if the licence is unclear? Treat the tool as not cleared. Open an issue asking the author, or skip it until the terms are clear.
Does this replace legal advice? No. It's a first pass that catches the obvious problems. Contract-level questions go to a lawyer.
Want help vetting the tools your team runs?
R21 Labs checks and wires the tools agencies use on client work, with the licence and version on record. Talk to us about a build or call +1 224-256-7011. More notes on the R21 Labs blog, including when not to put API keys in prompts and keeping secrets out of the prompt with MCP connectors.