Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
License icon

License

A fully local open-source license reference — lookup, compare, choose, and check compatibility

Unify Dynamics LLC

Documentation
Tools9read-only
Sign-inNoneno account, no key
Data keptNoneprocessed in memory
PriceFreeoptional Pro limits
StatusLiveMCP + REST
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

What license is MIT and what does it require?
Tools called
license_lookup
Find licenses with 'creative commons' in the name
Tools called
license_search
Compare MIT and GPL-3.0
Tools called
compare_licenses
What license should I use for a permissive library with patent protection?
Tools called
choose_a_license
Can I use MIT code in a GPL project?
Tools called
is_compatible
List OSI-approved licenses
Tools called
osi_approved_list
What are the strong copyleft licenses?
Tools called
copyleft_list
Give me a license badge for my README
Tools called
license_badge_snippet
What does copyleft mean?
Tools called
license_glossary
Are GPL-2.0 and GPL-3.0 compatible?
Tools called
is_compatible

About

License is a fully local open-source license reference. license_lookup gives one license's SPDX id, full name, OSI-approved and FSF-libre flags, an original plain-English summary of what it permits and requires (for the most common licenses), and the canonical reference URL for the actual legal text — never reproduced here. license_search finds licenses by id or name keyword across the full SPDX list. compare_licenses returns a hand-curated comparison table (commercial use, modification, distribution, patent grant, copyleft strength, must-disclose-source, same-license-required, trademark use, liability/warranty disclaimer) for the ~25 most common licenses. choose_a_license suggests 2-3 candidate licenses from a list of priorities, with reasoning. is_compatible gives a conservative, clearly-caveated compatibility note for a pair of licenses. osi_approved_list and copyleft_list return filtered lists. license_badge_snippet generates a shields.io-style badge (markdown/HTML/RST/URL). license_glossary defines common licensing terms. Keyless; fully local; general information, not legal advice.

Sources: SPDX License List Data (CC0-licensed metadata: ids, names, OSI/FSF flags, reference URLs) plus hand-authored summaries, comparison matrix, compatibility notes and glossary; fully local, zero upstream calls at request time

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.
Privacy policyTerms

What it can do

9 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Lookup & search2 tools
  • License lookupFull detail for one license: SPDX id, full name, OSI-approved and FSF-libre flags, a plain-English one- paragraph summary (in our own words --…
  • License searchSearch the full SPDX license list by id or name keyword.
Compare & choose3 tools
  • Compare licensesA plain-language, hand-curated comparison table between two licenses across key dimensions: commercial use, modification, distribution, patent…
  • Choose a licenseGiven a list of priorities, suggest 2-3 candidate licenses with reasoning, drawn from the comparison matrix.
  • Is compatibleA best-effort, clearly-caveated compatibility note for combining code under two licenses (e.g. can MIT code go into a GPL project).
Filters2 tools
  • Osi approved listThe list of OSI-approved (or, with only_osi=false, all non-deprecated SPDX) licenses.
  • Copyleft listLicenses grouped by copyleft strength (none, weak, strong, network), from the hand-curated comparison matrix.
Utilities2 tools
  • License badge snippetA shields.io-style badge snippet referencing a license, in markdown, HTML, RST, or as a plain image URL.
  • License glossaryDefinitions of common open-source licensing terms (copyleft, permissive, patent grant, share-alike, dual licensing, SPDX identifier, OSI-approved,…

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forGlobal
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://license.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide

More like this

Phase (BYOK)

Read your Phase secrets-manager setup: apps, environments, roles, service accounts and teams (names and settings only, never secret values) with your own service account token

Live · MCP + REST10 tools

Prowler Cloud (BYOK)

Read your Prowler Cloud security posture: connected cloud accounts, scans, findings, resources and compliance results with your own API key

Live · MCP + REST8 tools

Files.com (BYOK)

Read your Files.com site settings, usage and storage, automations, syncs, sync runs and groups with your own API key

Live · MCP + REST9 tools

PractiTest (BYOK)

Read your PractiTest test management data (projects, requirements, tests, steps, test sets, instances, runs, milestones, issues and fields) with your own API token

Live · MCP + REST12 tools

Mintlify (BYOK)

Read your Mintlify documentation analytics (page views, visitors, searches, feedback, assistant usage) and deployment status with your own admin API key

Live · MCP + REST7 tools

OpsLevel (BYOK)

Read your OpsLevel software catalog services, teams, systems, domains, scorecards, deploys and infrastructure with your own API token

Live · MCP + REST12 tools

Documentation

Back to top

License — connector documentation

  • MCP endpoint: https://license.connectorbay.com/mcp
  • REST API: POST https://license.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://license.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: none required. An optional Authorization: Bearer <key> raises rate limits.
  • Health: https://license.connectorbay.com/health · Tool schemas: https://license.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/license · agent@connectorbay.com

What License is for

The question that comes up in every "can I use this dependency" or "what license should I pick" moment — what does MIT actually require, is GPL-3.0 OSI-approved, can I mix this Apache-licensed library into my GPL project, what's the difference between MIT and the GPL — answered instantly, from a fully local reference, instead of hunting through a wiki page or a license's own dense legal text.

What it does

license_lookup gives one license's SPDX id, full name, OSI-approved and FSF-libre flags, and — for the most common licenses — an original, plain-English one-paragraph summary of what it permits and requires, plus the canonical reference URL for the actual legal text. license_search finds licenses by id or name keyword across the full SPDX license list. compare_licenses returns a hand-curated, plain-language comparison table (commercial use, modification, distribution, patent grant, copyleft strength, must-disclose-source, same-license-required, trademark use, liability/warranty disclaimer) for the roughly 25 licenses people actually run into day to day. choose_a_license takes a list of priorities — permissive, copyleft, patent protection, public domain, and more — and suggests 2-3 candidate licenses with reasoning. is_compatible gives a conservative, clearly-caveated compatibility note for combining code under two licenses, falling back to "check a lawyer or the FSF/SPDX compatibility notes" whenever it isn't confident, rather than guessing. osi_approved_list and copyleft_list return filtered lists. license_badge_snippet generates a shields.io-style badge in markdown, HTML, RST, or as a plain image URL — pure string templating, no network call. license_glossary defines about a dozen common licensing terms (copyleft, permissive, patent grant, share-alike, dual licensing, SPDX identifier, and more).

Where the data comes from

The full license identifier list (id, full name, OSI-approved / FSF-libre flags, canonical reference URL) is built at deploy time from the SPDX License List Data project, CC0-licensed metadata maintained by the Linux Foundation's SPDX project — the same identifier list most software tooling (package managers, SBOM generators, GitHub's own license detector) already relies on. That upstream file does not include full license legal text, and this connector doesn't either: every plain-English summary, comparison-matrix entry, compatibility note, and glossary definition is written from scratch in our own words, describing what a license does rather than reproducing what it says. Nothing is fetched at request time — the whole dataset is bundled with the server.

What it is not

Not a lawyer, and not a substitute for reading the actual license. Every response carries a "general information, not legal advice" disclaimer, and every lookup links to the license's canonical reference URL for the authoritative text — this connector never quotes or reproduces full license legal text itself. choose_a_license and is_compatible both end with an explicit reminder to consult a lawyer for anything with real stakes; is_compatible in particular is deliberately conservative and will say "uncertain — check the FSF/SPDX notes or a lawyer" rather than guess about a pairing it isn't confident on.

Tools

Lookup & search

license_lookup — Full detail for one license: SPDX id, full name, OSI-approved and FSF-libre flags, a plain-English one- paragraph summary (in our own words -- never the license's own legal text) of what it permits and requires, and the canonical reference URL for the real legal text. Use for "what license is MIT", "tell me about the GPL-3.0 license". Args: spdx_id_or_name.

license_search — Search the full SPDX license list by id or name keyword. Use for "find licenses with 'commons' in the name", "what BSD variants exist". Args: query.

Compare & choose

compare_licenses — A plain-language, hand-curated comparison table between two licenses across key dimensions: commercial use, modification, distribution, patent grant, copyleft strength (none/weak/strong/network), must-disclose- source, same-license-required, trademark use, and liability/warranty disclaimer. Covers the ~25 most common licenses (see comparable_ids in the error if a license isn't covered). Use for "compare MIT and GPL-3.0", "how does Apache-2.0 differ from BSD-3-Clause". Args: spdx_id_a, spdx_id_b.

choose_a_license — Given a list of priorities, suggest 2-3 candidate licenses with reasoning, drawn from the comparison matrix. Always ends with a reminder this is not legal advice. Use for "what license should I use for a permissive library with patent protection", "I want a copyleft license that closes the SaaS loophole". Args: priorities.

is_compatible — A best-effort, clearly-caveated compatibility note for combining code under two licenses (e.g. can MIT code go into a GPL project). Conservative by design: for pairs we're not confident about, it says to check a lawyer or the FSF/SPDX compatibility notes rather than guessing. Use for "can I use MIT code in a GPL project", "are GPL-2.0 and GPL-3.0 compatible". Args: spdx_id_a, spdx_id_b.

Filters

osi_approved_list — The list of OSI-approved (or, with only_osi=false, all non-deprecated SPDX) licenses. Use for "list OSI- approved licenses", "is this license OSI approved". Args: only_osi.

copyleft_list — Licenses grouped by copyleft strength (none, weak, strong, network), from the hand-curated comparison matrix. Use for "list strong copyleft licenses", "what weak copyleft licenses exist". Args: strength.

Utilities

license_badge_snippet — A shields.io-style badge snippet referencing a license, in markdown, HTML, RST, or as a plain image URL. Pure string templating -- no network call is made. Use for "give me a license badge for my README". Args: spdx_id, style.

license_glossary — Definitions of common open-source licensing terms (copyleft, permissive, patent grant, share-alike, dual licensing, SPDX identifier, OSI-approved, and more). Use for "what does copyleft mean", "what's a patent grant". Args: term.

Conventions

  • Read-only. Every tool reads public data or computes; nothing is written anywhere and nothing about the user is stored.
  • Result envelope. ok: true with data, or ok: false with a structured error (bad_input, not_found, upstream_error). degraded lists optional sources that were unreachable.
  • Rate limits. Free tier 60 tool calls/minute and 300/day per user (keyed on the user identifier supplied by the host agent, else client IP); Pro keys raise this. Over-limit calls return HTTP 429 with Retry-After. initialize and tools/list are never counted.

Support

agent@connectorbay.com · connectorbay.com/license/support

Privacy policy

Back to top

License — Privacy Policy

Effective 24 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What License is. License is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a fully local open-source license reference: SPDX-derived license lookup and search, a hand-curated comparison matrix, license-choice guidance, compatibility notes, OSI/copyleft filters, badge snippets, and a glossary. You interact with your assistant; the assistant sends us only the arguments needed for that one lookup.

What we receive. The arguments of each tool call — a license identifier or name, a search keyword, a pair of licenses to compare, a list of priorities, or a glossary term — the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.

Everything is answered from a bundled reference dataset and nothing is stored. No request is forwarded to any third party — there is no upstream call at all, live or otherwise — and no query is logged in request bodies, recorded, or used to train anything.

What we do not receive or store. We do not receive your conversation with the assistant or your name, and we do not build a profile from your queries: each request is answered independently and nothing carries over between requests. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.

Sub-processors. None — the entire dataset is bundled with the server and answered locally. Hosting: Vercel (United States regions).

Legal bases and your rights. Our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.

Children. License is a general-audience service operated by the adult using the assistant.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

License — Terms of Service

Effective 24 September 2026. These terms govern use of the License connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. License returns a fully local open-source license reference — SPDX-derived license lookup and search, a hand-curated plain-language comparison matrix, license-choice guidance, best-effort compatibility notes, OSI-approved and copyleft filters, shields.io badge snippets, and a glossary. It is accessed through an AI assistant or directly over MCP or HTTP.
  2. General information, not legal advice. The Service provides general information about open-source licenses for reference purposes only. It is not legal advice, does not create an attorney-client relationship between you and Unify Dynamics LLC or anyone else, and must not be relied on as a substitute for reading the actual license text or consulting a qualified lawyer — especially for choose_a_license and is_compatible, which are explicitly best-effort and conservative rather than authoritative. Every relevant response says so.
  3. No full license text. The Service never reproduces full license legal text. Summaries, comparisons and compatibility notes are our own original, plain-English descriptions; each response links to the license's canonical reference URL for the authoritative text.
  4. Data reflects a point in time. License identifiers, names, and OSI/FSF flags are built from the SPDX License List Data project as of the Service's stated build date; the SPDX list itself is periodically updated, so always check spdx.org for the current authoritative list if precision matters.
  5. Acceptable use. Automated use within the published rate limits is welcome.
  6. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
  7. Data. Our Privacy Policy describes what we process. In short: your query is answered from a bundled reference dataset, and nothing is stored.
  8. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
  9. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any decision about license choice, compliance or compatibility made using it. Our total liability is limited to US $100.
  10. Governing law. California law; venue in San Mateo County, California.
  11. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/license

Support

Back to top

License support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. License never asks for them.

Get License

Free · No sign-in · Read-only

Streamable HTTP, stateless, no authentication. Paste the endpoint into any MCP-capable agent.

https://license.connectorbay.com/mcp
{
  "mcpServers": {
    "license": {
      "type": "http",
      "url": "https://license.connectorbay.com/mcp"
    }
  }
}