Eyevinn Open Source Cloud

io.github.EyevinnOSCPublished by GitHub account EyevinnOSCv8.15.3Updated Oct 12, 2026

Deploy open-source services and your own apps on Open Source Cloud (OSC, osaas.io).

The publisher's own server: Source

VerifiedStreamable HTTPWeb executableCloud & Infrastructure

Overview

AI-generated overview

A remote MCP endpoint for Eyevinn Open Source Cloud that lets an assistant deploy open-source services and your own apps on OSC (osaas.io).

What you can do
Connect an assistant to Eyevinn Open Source Cloud (OSC) over a remote HTTP endpoint, so it can work with the platform from a chat session. According to the registry description, this covers deploying open-source services and your own applications on OSC. No individual tools are listed in the manifest, so the exact operations available are not documented here.
When to use it
Useful when you want an assistant to help stand up open-source services or your own apps on Eyevinn Open Source Cloud without leaving the conversation.
Requirements
A remote MCP client that supports streamable HTTP, pointed at the OSC endpoint. The manifest declares no authentication, environment variables or headers, and no local package or runtime is needed.
Before you install
The manifest declares no authentication, so check how the endpoint is secured before relying on it. Deploying services and apps changes state on your OSC account and may incur usage costs; confirm what will be created before approving actions.

Installation

In SourceWeft

  1. Open Eyevinn Open Source Cloud in the dashboard and add it to a workspace.
  2. 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/io.github.EyevinnOSC%2Fosc/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.

{
  "mcpServers": {
    "eyevinn-open-source-cloud": {
      "type": "http",
      "url": "https://mcp.osaas.io/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v8.15.3LatestOct 12, 2026

Score

28% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

Other Source integrations