Skovos Governance

ai.skovosPublished by skovos.aiOfficial publisherv1.0.0Updated Nov 5, 2026

Governance for AI agents in health systems: inventory, scoped permissions, evidence, revocation.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote MCP endpoint that gives AI agents governance controls in health systems: agent inventory, scoped permissions, evidence, and revocation.

What you can do
  • The manifest lists no tools, so capabilities are known only from the short description.
  • Manage an inventory of AI agents operating in health-system settings.
  • Apply scoped permissions that limit what each agent may do.
  • Keep evidence records of agent activity or authorization.
  • Revoke agent access when it is no longer appropriate.
When to use it
Consider it when an assistant or agent fleet runs inside a health system and you need a central place to register agents, constrain their permissions, retain evidence, and revoke access. It is aimed at governance and oversight rather than general-purpose tasks.
Requirements
A remote streamable HTTP endpoint at mcp.skovos.ai; nothing is installed locally. OAuth authentication is required, so a Skovos account or OAuth-capable client is needed. No environment variables or headers are declared.
Before you install
The server governs agent permissions and revocation, so changes made through it can cut off or widen what agents are allowed to do. It handles health-system context, which is sensitive; review what data is sent to the provider. Tool-level behavior is not documented in the manifest, so confirm scope before relying on it.

Installation

In SourceWeft

  1. Open Skovos Governance in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.skovos%2Fgovernance/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "skovos-governance": {
      "type": "http",
      "url": "https://mcp.skovos.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 5, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.