Developer · Remote MCP server
Weavz
Governed app access for AI agents: 1,000+ apps & 12,000+ tools via Code Mode MCP.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.weavz/weavz- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-06-23
- Updated
- 2026-06-23
- Publisher
- io.weavz
- Namespace
- Namespace verified by the MCP Registry via the domain weavz.io · how
- Website
- weavz.io
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://platform.weavz.io/mcp/weavz | None |
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 Weavz
Weavz is a remote MCP server: there is nothing to install. Its endpoint is https://platform.weavz.io/mcp/weavz, 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.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
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 |
|---|---|
| Weavatrix GitFast, bounded, read-only Git evidence for local AI coding agents. | Local · stdio |
| Weavatrix JsAlways-fresh local repo graph: LSP-backed impact, Health, dead code, endpoints, architecture. | Local · stdio |
| Weavatrix RefactorTransactional refactoring extension with 11 evidence-backed tools, previews, and rollback. | Local · stdio |
| Weavatrix Refactor JsTransactional refactoring MCP with 11 evidence-backed tools, hash-bound previews, and rollback. | Local · stdio |
| Web & Developer Data ToolsWebsite tech stacks, domain WHOIS/DNS/SSL, sitemaps, PDF text, GitHub trending and more. | Remote · HTTPLive check: sign-in required |
| Web Browser (kogiQA)This web browser has been designed to help your agent debug and develop complex web applications. | Local · stdio |
| Web Content ExtractorExtract and process web content into clean, structured formats optimized for LLMs. | Local · stdio |
| Web FetcherTurns any web page into clean Markdown, page metadata and classified links for LLMs. | Local · stdio |