io.github.soccervortex/omnistream-mcp
NPM · OMNISTREAM-MCP · SCANNED AUG 17
MCP server for OmniStream. Lets AI assistants discover and call any marketplace API.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 469 tokens (~93/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · omnistream-mcp
claude mcp add soccervortex-omnistream-mcp -- npx -y omnistream-mcp
codex mcp add soccervortex-omnistream-mcp -- npx -y omnistream-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"soccervortex-omnistream-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"omnistream-mcp"
],
"enabled": true
}
}
} openclaw mcp add soccervortex-omnistream-mcp --command npx --arg -y --arg omnistream-mcp
mcp_servers:
soccervortex-omnistream-mcp:
command: "npx"
args: ["-y", "omnistream-mcp"] {
"mcpServers": {
"soccervortex-omnistream-mcp": {
"command": "npx",
"args": [
"-y",
"omnistream-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Aug 26 +1
- Security disclosure: unverified → fail ▼ functional
- 16 Aug 26 0
- Security disclosure: fail → unverified ▼ functional
- 15 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Aug 26 +3
- Security disclosure: unverified → fail ▼ functional
- Stability: unverified → 0.23 ▲ functional
- 11 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 +4
- Known CVEs: partial → pass ▲ security
- Dependency health: partial → 0.85 functional
- 6 Aug 26 +30
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Aug 2026 · Analysed npm/omnistream-mcp@0.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
call_api ~166
Call any published API on the OmniStream marketplace using the proxy. Your Omni key (OMNI_KEY env var) authenticates the request - you never need the upstream API key. Use get_api first to learn the available endpoints and their parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | Request body for POST endpoints. If provided, the request is sent as POST with JSON body. |
| operation | string | yes | The operationId of the endpoint to call (e.g. 'status', 'items-search'). Get these from get_api or list_endpoints. |
| params | object | – | Query string parameters as key-value pairs (e.g. {"q": "ak 47", "limit": "10"}). |
| slug | string | yes | The API slug (e.g. 'skinapi'). |
No output schema declared.
No examples provided.
get_api ~81
Get full details for a specific API: description, base URL, authentication method, all endpoints with their HTTP method, path, parameters, and summary. Use this before calling call_api to understand what parameters an endpoint needs.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The API slug (e.g. 'skinapi'). Get slugs from list_apis or search_apis. |
No output schema declared.
No examples provided.
list_apis ~84
List all published APIs on the OmniStream marketplace. Returns slug, title, category, endpoint count, rating, and uptime for each API. Use this to browse what is available before calling search_apis or get_api.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional: filter by category name (e.g. 'Gaming', 'Finance', 'Weather'). Case-insensitive substring match. |
No output schema declared.
No examples provided.
list_endpoints ~53
List all endpoints for a specific API with their operation IDs, HTTP methods, paths, and required parameters. Lighter than get_api when you only need the endpoint list.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The API slug. |
No output schema declared.
No examples provided.
search_apis ~85
Search the OmniStream marketplace by keyword using BM25 ranking. Searches across API titles, descriptions, tags, and endpoint names. Returns ranked results with relevance scores.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of results to return (default 10, max 50). |
| query | string | yes | Search keywords, e.g. 'cs2 skin prices' or 'weather forecast'. |
No output schema declared.
No examples provided.