Developer · Remote MCP server
ZopDev MCP
Cloud cost, inventory and governance on AWS/Azure/GCP. Read-only by default, optional scoped writes.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.zop/zopdev-mcp- Version
- 1.5.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-10-01
- Updated
- 2026-10-01
- Publisher
- dev.zop
- Namespace
- Namespace verified by the MCP Registry via the domain zop.dev · how
- Listed under
- AWS MCP servers, Azure MCP servers, Google Cloud MCP servers
- Website
- zop.dev
- Repository
- github.com/zopdev/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.zop.dev/mcp-server | Authorization (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect ZopDev MCP
ZopDev MCP is a remote MCP server: there is nothing to install. Its endpoint is https://api.zop.dev/mcp-server, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. 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 |
|---|---|
| ZKshareZKshare stdio MCP: store/prove/share, semantic search, sandbox proxy to HTTPS /api/v1/context. | Local · stdio |
| Zoekt MCPFast indexed code search for AI agents, powered by Sourcegraph Zoekt. | Local · stdio |
| ZoneFoundry for SonosControl Sonos from any MCP client. No bridge hardware; connects over OAuth - no API key to paste. | Remote · HTTPLive check: sign-in required |
| ZopafNegotiation math engine. Pareto frontier, counteroffer generation, zero LLM tokens. | Remote · HTTPLive check: ✗ no handshake |
| ZordonSupervise a local dev stack - databases, brokers and services declared in an Alphasfile - over MCP. | Local · stdio |
| Zotero Native MCPRead and write your local Zotero 10 library. No plugin, no zotero.org API key, no cloud. | Local · stdio |
| Zoxron MCPYour AI agent deploys, migrates & upgrades self-hosted Odoo ERP on a server you own. | Remote · HTTPLive check: sign-in required |
| zRev AIGrade any llms.txt, cold-read a homepage, run a B2B GTM ROI model, get a GTM diligence checklist. | Remote · HTTPLive check: ✓ handshake |