Skip to content
Back to search

foro

SkillWorks with Claude CodeGitHub

Deploy, debug and monitor the MCP servers you host on foro.sh.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 19 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/foro-sh/foro-plugin with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/foro-sh/foro-plugin'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/foro-sh--foro-plugin/badge.svg)](/listings/foro-sh--foro-plugin)

HTML

<a href="/listings/foro-sh--foro-plugin"><img src="/api/listings/foro-sh--foro-plugin/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/plugin.json · Manifest · 14 lines
  1. {
  2. "name": "foro",
  3. "version": "0.1.0",
  4. "description": "Deploy, debug and monitor the MCP servers you host on foro.sh.",
  5. "author": {
  6. "name": "foro.sh",
  7. "url": "https://foro.sh"
  8. },
  9. "homepage": "https://docs.foro.sh/foro-mcp",
  10. "repository": "https://github.com/foro-sh/foro-plugin",
  11. "license": "MIT",
  12. "privacyPolicyUrl": "https://foro.sh/privacy",
  13. "keywords": ["mcp", "deploy", "hosting", "logs", "developer tools"]
  14. }
README.md · README · 42 lines
  1. # foro
  2. Deploy, debug and monitor the MCP servers you host on [foro.sh](https://foro.sh).
  3. foro hosts MCP servers in the EU: you sign in with GitHub, pick a repository, and get a stable `https://<name>.foro.sh` URL. This plugin lets you run that from Claude. List your servers, deploy or roll back, follow a deploy to live and see why one failed, read and analyze runtime logs, check calls, errors and latency, see who uses a server, and check whether it is ready for a store listing.
  4. It is for developers who already host MCP servers on foro.sh, or who want to start. It acts with your own foro account and only in the workspaces you are a member of.
  5. ## Skills
  6. | Skill | What it does |
  7. | --- | --- |
  8. | `get-started` | Shows your workspaces and servers right after you connect, and suggests a first step. |
  9. | `create-server` | Puts a new server on foro from the library, a template, a repository, an npm package or a folder, sets its secrets and deploys it. |
  10. | `deploy-and-verify` | Deploys, rolls back or cancels a deploy, follows it to live, and explains one that failed. |
  11. | `debug-server` | Finds out why a server is failing, erroring or slow, and proposes a fix. |
  12. | `fleet-check` | Gives a short health overview of all your servers. |
  13. | `usage-and-clients` | Says who uses a server and from which clients, and whether you are heading past your plan's monthly tool-call limit. |
  14. | `security-check` | Checks your servers' dependencies for known vulnerabilities and says how to fix them. |
  15. | `custom-domain` | Puts a server on a domain you own, or explains why one isn't working yet. |
  16. | `prepare-for-store` | Checks whether a server is ready for the Claude, ChatGPT, MCP registry, Cursor and other listings, and writes the fixes. |
  17. | `build-app-view` | Builds the interface for a server's tools (an MCP Apps view) in your own repository. |
  18. ## Connections and data
  19. - **One destination.** The plugin connects only to the foro MCP server at `https://mcp.foro.sh/mcp`. It makes no other network connection of its own, and it ships no scripts, hooks or commands.
  20. - **Sign-in.** You sign in with OAuth under your own foro account the first time a tool runs. The plugin never sees your password, and you can disconnect at any time from your foro account.
  21. - **Permissions.** The connection asks for the `read`, `deploy` and `write` scopes. Everything the tools do, foro's API decides under your account: workspace membership, plan limits and seats apply exactly as in the dashboard.
  22. - **Secrets stay out of chat.** The plugin never reads, asks for or repeats secrets, tokens or passwords. When a server needs a secret, it sends you to a foro page where you set it yourself.
  23. - **It asks first.** Creating a project, deploying, rolling back, cancelling a deploy and deleting a project all ask you to confirm before they run.
  24. - **Limits.** foro's tools cannot edit your repository's code. The `build-app-view` skill writes files only through your client's own file tools, in a checkout you have open. Billing and team management stay in the foro dashboard.
  25. ## Learn more
  26. - Tool reference: [docs.foro.sh/foro-mcp](https://docs.foro.sh/foro-mcp)
  27. - Privacy policy: [foro.sh/privacy](https://foro.sh/privacy)
  28. - Terms of service: [foro.sh/terms](https://foro.sh/terms)
  29. - Support: [foro.sh/support](https://foro.sh/support)
  30. ## License
  31. MIT, see [LICENSE](LICENSE).

Version history

  • v0.1.011/19/2026

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.