Library

Skills and plugins for FORGE. Verified entries are reviewed and pinned: skills by sha256, so the file you install is byte-for-byte the file that was reviewed. Community entries are unreviewed; FORGE warns you and keeps their tools behind ask-permission either way.

Verified

Community

Not reviewed. These come straight from the public MCP registry and community submissions. Nobody has read this code or skill text on your behalf. An MCP server runs as your user the moment you connect it; read the source before installing, exactly as you would any package. FORGE keeps every community tool behind ask-permission: it can never run a call you did not approve.

Loading from the public MCP registry…

Publish to the library

Anyone can submit. Every submission lands in the community tier and waits for review; submitting never publishes, and never grants Verified. The full criteria are in REGISTRY.md.

Open a pull request

Fork github.com/Blacknapoleon99/forge-harness
Add your entry to site/registry.json (tier: community); skills also add a SKILL.md under site/registry/skills/<id>/
Open a PR; a maintainer review can promote it to Verified

A maintainer merges the entry into site/registry.json. Only a maintainer can set the verified tier, and a verified skill is always sha256-pinned in the same change.

There is a submission API as well (POST /api/registry/submit, token-authenticated), but it is not open for sign-ups yet: it requires a verified email address and this deployment has no mail provider configured, so an account created today could never finish verifying. Rather than show you a form that cannot complete, the pull request above is the route that actually works. The API opens when the accounts side is finished.