Developer · Local MCP server
Overdrive Intel
AI coding ecosystem intelligence - breaking changes, tools, security alerts from 900+ sources.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Looney-tic/intel-overdrive- Version
- 0.9.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-03-25
- Updated
- 2026-03-25
- Publisher
- Looney-tic (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Looney-tic) · how
- Website
- inteloverdrive.com
- Repository
- github.com/Looney-tic/intel-overdrive
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | intel-overdrive-mcp | 0.9.1 | stdio |
How to connect Overdrive Intel
Overdrive Intel runs locally from a Node.js package published to the npm registry: intel-overdrive-mcp version 0.9.1. 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 intel-overdrive-mcp@0.9.1. It reads these environment variables: OVERDRIVE_API_KEY and OVERDRIVE_API_URL; 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": {
"intel-overdrive": {
"command": "npx",
"args": [
"-y",
"intel-overdrive-mcp@0.9.1"
],
"env": {
"OVERDRIVE_API_KEY": "<value>",
"OVERDRIVE_API_URL": "<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 developer servers
| Server | Runs |
|---|---|
| OuterSpace ApizrPython capability compiler: local read-only analysis and explicit MCP/REST exposure planning. | Local · stdio |
| Outflow MCPMCP server exposing an Outflow workspace's live architecture graph as context for AI coding agents. | Local · stdio |
| OutSlideCreative workspace. Public MCP: outline previews for Codex and Claude Code; media in the web app. | Remote · HTTPLive check: ✓ handshake |
| oveccArchitecture guardrails for AI-written code: dependency graph, impact, dead code, CI gate. | Local · stdio |
| OverllmFind the LLM/AI calls you didn't need - where plain code or a regex does the job. No model. | Local · stdio |
| OverskillBuild and publish Overskill apps from Cursor, Claude, ChatGPT, or any MCP client. | Remote · HTTPLive check: sign-in required |
| OverwingGuardrails for LLM output: pass / fail / review verdicts and one recommended action. Hosted or npm. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |
| Ovh Api MCPMCP server for the OVH API. Explore and call any OVH endpoint via sandboxed JS. | Local · stdio |