MCP Composer MCP server
Aggregate multiple MCP backends behind a single stdio endpoint with namespaced routing.
2 stars
Reviews
Write oneNobody has reviewed MCP Composer yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
MCP Composer tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 67 days ago12/15
- Maintainer identityregistry namespace matches repository owner6/10
Findings (1)
- highPackage @oaslananka/composer not found on npm
code.package-missing
How MCP Composer compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 75/100
- higher than 45% of 48,255 servers
- GitHub stars
- 2
- more than 75% of 28,688 servers
Install MCP Composer in Claude Code, Cursor or VS Code
Runs npx -y @oaslananka/composer on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add composer -- npx -y @oaslananka/composer
What the publisher says
From the MCP Composer repository's README, as published. We do not edit it. Read it on GitHub
MCP Infrastructure Suite
The missing infrastructure layer for Model Context Protocol ecosystems.
flowchart LR
Shared["@oaslananka/shared"]
Forge["@oaslananka/forge"]
Sentinel["@oaslananka/sentinel"]
Atlas["@oaslananka/atlas"]
Composer["@oaslananka/composer"]
Bridge["@oaslananka/bridge"]
Observatory["@oaslananka/observatory"]
Lab["@oaslananka/lab"]
Shared --> Forge
Shared --> Sentinel
Shared --> Atlas
Shared --> Composer
Shared --> Bridge
Shared --> Observatory
Shared --> Lab
Clients["IDE / Agent / SDK clients"] --> Sentinel
Clients --> Composer
Composer --> Backends["Backend MCP servers"]
Sentinel --> Backends
Forge --> Composer
Forge --> Sentinel
Atlas --> Clients
Observatory --> Sentinel
Observatory --> Forge
Lab --> ComposerWhy mcp-suite?
Most MCP projects stop at the server boundary. mcp-suite focuses on the harder production layer around it: transport compatibility, trust boundaries, orchestration, discovery, observability, and operator workflows. That makes it useful once you move past a single local demo and start running MCP in teams, CI, or internal platforms.
The suite is built for guarded GitHub-hosted release automation, with every publishable package prepared for public npm publishing under the @oaslananka scope. The monorepo stays strict TypeScript, Turborepo, pnpm, and release-please manifest based.
Compared with one-off MCP utilities, the packages here are designed to compose: shared defines the protocol/runtime baseline, sentinel and composer control traffic, forge orchestrates work, atlas catalogs capability, bridge generates servers, observatory closes the feedback loop, and lab gives contributors a desktop workbench.
Packages
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
MCP Composer: common questions
- Is MCP Composer MCP server safe?
- Mostly: it is graded B (75/100). Read the MCP Composer safety report
- How do I install MCP Composer?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does MCP Composer need an API key?
- No secret keys are declared. It reads 1 setting from the environment.
- Is MCP Composer maintained?
- The last commit was 105 days ago (2026-07-22). The latest release is v1.0.0.
- How does MCP Composer compare with other MCP servers?
- safety score 75/100 (higher than 45% of 48,255 servers); github stars 2 (more than 75% of 28,688 servers). Full comparison.