Health · Local MCP server
Compete Competitive Intelligence
Typed access to monitored competitive changes, evidence, dossiers, research, and collection health.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.niyonzimabryan/compete- Version
- 0.6.0
- Status
- Active
- Category
- health
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-05
- Updated
- 2026-09-05
- Publisher
- niyonzimabryan (GitHub)
- Website
- github.com/niyonzimabryan/sentinel/tree/main/packages/compete-mcp
- Repository
- github.com/niyonzimabryan/sentinel
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | compete-mcp | 0.6.0 | stdio |
How to connect Compete Competitive Intelligence
Compete Competitive Intelligence runs locally from a Node.js package published to the npm registry: compete-mcp version 0.6.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y compete-mcp@0.6.0. It reads these environment variables: COMPETE_API_KEY (required, secret), COMPETE_URL (required), COMPETE_REPO and COMPETE_TIMEOUT_MS; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"compete": {
"command": "npx",
"args": [
"-y",
"compete-mcp@0.6.0"
],
"env": {
"COMPETE_API_KEY": "<secret>",
"COMPETE_URL": "<value>",
"COMPETE_REPO": "<value>",
"COMPETE_TIMEOUT_MS": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More health servers
| Server | Runs |
|---|---|
| Coach WattsRemote MCP server for training, nutrition, wellness, and performance data with OAuth 2.0. | Remote · HTTP |
| Cochrane Medical ReviewsSystematic medical reviews and evidence-based healthcare research. | Remote · HTTP |
| Codesentinel MCPCodebase health MCP: dead code, cycles, coupling, architectural drift. | Local · stdio |
| CohearenceTrack, curate, and analyze data about your health, habits, and goals. | Remote · HTTP |
| Constat MCP — FDA Device Evidence LifecycleFDA and CMS evidence for AI medical devices: 510(k), postmarket, reimbursement, and compliance. | Remote · HTTP |
| Context First MCP37-tool MCP server: context health, memory, reasoning, truthfulness & research pipeline. | Local · stdio |
| context-doctorProfile LLM context: token breakdown, wasted-context findings and fixes for chats and agents. | Local · stdio |
| Convergent Provider DirectorySearch a healthcare provider directory and get full provider details by id. | Remote · HTTP |