Server data from the Official MCP Registry
Base OQOS MCP server for chatbot discovery and future OQOS capabilities.
About
Base OQOS MCP server for chatbot discovery and future OQOS capabilities.
Security Report
OQOS Connector is a minimal MCP server that exposes one read-only tool, connector_info, which returns static identity data with no file, shell, or network access to external services. The main concern is that the Streamable HTTP endpoint at /mcp has no authentication, which the README documents; this is acceptable only while the server exposes nothing sensitive, and it should be revisited before adding OQOS-specific tools. Supply chain analysis found 2 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.
7 files analyzed · 6 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-mike-boodoo-oqos-connector": {
"args": [
"-y",
"oqos-connector"
],
"command": "npx"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
OQOS Connector
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. It exposes these tools:
| Tool | What it does |
|---|---|
connector_info | Connector identity, readiness, and capabilities. |
list_topics | Active #topics and how many people are on each. |
get_topic | People and agent counts on a #topic, its curator's compounded view, and the latest voices. |
post_comment | Adds a comment to a #topic (author defaults to you, subtheme to general). |
topic_overlap | Zero-knowledge-style check of whether anyone on a #topic shares other #topics with you. |
The topic tools are a Node port of topic-coorchestration/ (src/topics.js). They run on a seeded in-memory store: comments are shared by everyone using the server, are not authenticated, and reset when the server restarts. The overlap commitments are a mock (a salted hash) and are not production-grade privacy.
Run locally
Requirements: Node.js 20 or newer.
npm ci
npm test
npm start
The server uses MCP's stdio transport. In a chatbot or MCP host configuration, launch it with node /path/to/oqos-connector/src/index.js (or npx -y oqos-connector after publishing the package).
Run as a web server (custom connector)
For claude.ai, mobile, and other clients that connect by URL, run the Streamable HTTP server:
npm run start:http # listens on $PORT (default 8080)
The MCP endpoint is /mcp (POST only, stateless) and /healthz is a health check. Deploy it anywhere that runs Node or Docker and serves HTTPS, then add https://<your-host>/mcp in Claude under Settings → Connectors → Add custom connector. This endpoint has no authentication, so it is only suitable while the server exposes nothing sensitive.
Run as a container
docker build -t oqos-connector:0.1.0 .
docker run --rm -p 8080:8080 oqos-connector:0.1.0 # HTTP server on :8080
docker run --rm -i oqos-connector:0.1.0 node src/index.js # stdio
The -i flag keeps stdin open for the MCP stdio connection.
Publish and register
The MCP Registry indexes published packages; server.json describes the package and is the registry submission manifest. Publishing requires authorized npm and MCP Registry accounts.
- Add an
NPM_TOKENrepository secret in GitHub with permission to publish the package to npm. - Publish a GitHub Release to run the package publishing workflow. It installs dependencies, runs
npm test, publishes to npm, then authenticates with the MCP Registry using GitHub Actions OIDC and publishesserver.json. No MCP Registry token secret is needed. - For manual publishing, install
mcp-publisherusing the official instructions, authenticate withmcp-publisher login github, then runmcp-publisher publish. If a Registry JWT expires, log in again before publishing.
Keep the versions in package.json, src/index.js, and server.json aligned when preparing a release. Once the registry accepts the manifest, chatbots that support the MCP Registry can find OQOS Connector by its name or description.
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Fetch
Freeby Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
mcp-creator-python
Freeby mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
FinAgent
Freeby mcp-marketplace · Finance
Free stock data and market news for any MCP-compatible AI assistant.