Oqos Connector

io.github.mike-boodooPublished by GitHub account mike-boodoov0.1.0Updated Oct 24, 2026

Base OQOS MCP server for chatbot discovery and future OQOS capabilities.

VerifiedSTDIODesktop onlyDeveloper ToolsAI & ML

Overview

AI-generated overview

A base OQOS MCP server that exposes a connector_info tool so chatbots can discover OQOS and future capabilities.

What you can do
OQOS Connector is a deployable base Model Context Protocol server for OQOS. Its name and description are registered in server.json so MCP registries and compatible chatbot clients can discover it. The initial server exposes only the connector_info tool; OQOS-specific tools can be added after deployment. It runs over MCP's stdio transport.
When to use it
Use it when you want a minimal, deployable MCP server that registers OQOS in a registry and lets compatible chatbots discover it. It is a starting point rather than a feature-complete integration, since only connector_info is exposed initially.
Requirements
Node.js 20 or newer. Run locally with npm ci, npm test, and npm start, or launch it in an MCP host with node /path/to/oqos-connector/src/index.js or npx -y oqos-connector after publishing. A Docker option is also provided; the -i flag keeps stdin open for the stdio connection.
Before you install
Publishing and registering the package requires authorized npm and MCP Registry accounts. The README mentions adding an NPM_TOKEN repository secret with permission to publish to npm; keep such credentials private. The server itself declares no authentication, environment variables, or headers.

Installation

In SourceWeft

  1. Open Oqos Connector in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestOct 15, 2026

Score

25% 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 days25 pts

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

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

  • License10 pts

    Declare a license in the repository or the registry entry.