Your team already installs MCPs

What already works

• Private MCPs. Your internal server is visible only to your team — it is absent from the public catalog, search and sitemap, and isolated from other tenants.
• One gateway for the whole team. A member connects gateway.unyly.org/mcp in their client once and gets exactly the set of servers the team allows. No handing out per-server keys.
• Prepaid balance. A shared team wallet. Debits are atomic — going negative is impossible: if the funds are not there, the call simply does not run. No invoices after the fact.
• Per-member cap.A spend ceiling per person; past it, that member's calls stop while the rest of the team keeps working.
• Per-tool pricing. Basic tools free, heavy ones at a flat price or a markup over cost. Configurable per tool.
• A log of every call. Who, which server, which tool, when, and what it cost — double-entry, so the balance always reconciles with the history.
• Roles. Owner, admin, member. OAuth 2.1 (DCR + PKCE) — no secrets pasted into a chat, tokens revoked in one click.

What is not there yet

Stated plainly, so you do not find out during a security review:

• SOC 2 and ISO 27001 — not certified;
• SAML / OIDC / SCIM — sign-in is Google and GitHub; no corporate IdP yet;
• SIEM export, DPA, on-prem and EU data residency — on request, not out of the box;
• no public status page with an SLA yet.

Getting started

Create a team from your account: /account/teams. Then top up the balance, invite members, set per-tool prices and caps.

If you need a private registry, a pilot, or answers for your security team, write to [email protected] or use the contact form. The server-review methodology is at /security.