Open Source License Skill

What this skill does

Let your agent look up license terms. Call it as an MCP tool to check whether MIT, GPL or Apache is OSI-approved and where it's compatible. You switch it on with a single toggle — no SDK and no endpoint wiring — and it answers over MCP or REST using the same key as every other skill.

See it work

A real response from the Open Source License Skill — exactly what your agent gets back when it makes the call.

vervekit · openlicensestool call

{
  "name": "MIT"
}

result

domain_content: false
domain_data: false
domain_software: true
legacy_ids: [ 1 item ]
license: MIT
name: MIT License
license_url: https://opensource.org/licenses/MIT
license_status: active

+2 more fields

Run it with your own input. Live calls happen in your dashboard, on your key.

Ways to use it

Turn IDs into detail

Enable Open Source License and your app can add open source license to your app — expand an identifier into full structured detail — in a single call, no integration per source.

A tool your agent reaches for

Over MCP, your model calls openlicenses to enrich data mid-workflow exactly when it's needed.

Enrich from your backend

Call Open Source License over REST to add open source license to your app across a batch in a server-side job, one key for all of it.

Use it in your app

Once enabled, this skill is reachable two ways — pick whichever fits how you build. Both use the same key.

For AI agentsMCP

It appears to your model as a callable tool. No extra code — the agent invokes it when a task needs it.

openlicenses

For apps & backendsREST

Call it from your server with one request and your key. Node, Python, Go — anything that can send a GET.

GET /v1/openlicenses

Ask your agent

“Enable Open Source License and ask your agent to add open source license to your app.”
“Use the Open Source License skill for me.”

Open Source License Skill, answered

How to connect it over MCP or REST.

How do I add Open Source License to my app or agent?

Enable the Open Source License Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the openlicenses tool) or over REST (call it from any backend). No SDK to install and no endpoint to wire.

MCP or REST — which should I use?

Both work off one key. Use MCP when an AI agent should decide when to add open source license to your app — the skill shows up as a callable tool. Use REST when your own server-side code should call it directly. Many apps use both.

Which agents and frameworks does it work with?

Any MCP client — Claude, Cursor, LangChain, and custom agents all speak the Model Context Protocol, so Open Source License appears as a standard tool with nothing skill-specific to integrate.

How many credits does a Open Source License call cost?

Each call costs 1 credit. Every skill rides the same key and the same connection, so enabling more skills doesn't add more integrations to manage.

Do I need to install anything?

No SDK and no endpoint wiring — enabling the skill is a toggle. You point your agent at the VerveKit MCP endpoint (or call REST) and Open Source License is available immediately.

Where does the data come from, and what shows on my bill?

VerveKit runs on APIVerve, our production data engine; Open Source License is one of 300+ skills on the same key. Invoices and card statements show APIVERVE.

Turn IDs into detail

A tool your agent reaches for

Enrich from your backend

Open Source License Skill, answered

Give your software a way to act on the world.

Scaling in production?