Developer · Local MCP server
Pituitary
Catch spec drift before it catches you. Detect overlap, stale docs, and code drift.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.dusk-network/pituitary- Version
- 1.0.0-beta.12
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- MCP Bundle (.mcpb)
- Published
- 2026-05-08
- Updated
- 2026-05-08
- Publisher
- dusk-network (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/dusk-network) · how
- Repository
- github.com/dusk-network/pituitary
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| MCP Bundle (.mcpb) | https://github.com/dusk-network/pituitary/releases/download/v1.0.0-beta.12/pituitary-darwin-arm64.mcpbSHA-256 checksum stated | - | stdio |
| MCP Bundle (.mcpb) | https://github.com/dusk-network/pituitary/releases/download/v1.0.0-beta.12/pituitary-linux-amd64.mcpbSHA-256 checksum stated | - | stdio |
How to connect Pituitary
Pituitary runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/dusk-network/pituitary/releases/download/v1.0.0-beta.12/pituitary-darwin-arm64.mcpb. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client.
Pituitary runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/dusk-network/pituitary/releases/download/v1.0.0-beta.12/pituitary-linux-amd64.mcpb. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client.
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 |
|---|---|
| PipeheroDebug webhooks from your AI agent: inspect and replay captured webhooks on localhost. | Remote · HTTPLive check: ✓ handshake |
| PipepostMCP server to publish to Substack, Ghost, Dev.to, WordPress, LinkedIn + 5 more from Claude Code. | Local · stdio |
| PiPic Integration GuideRead-only PiPic CLI and HTTP API guidance; no image bytes are transferred. | Remote · HTTPLive check: ✓ handshake |
| PitchprotocolPitch Protocol - agent-native venture-capital infrastructure (pitchprotocol.vc). | Remote · HTTPLive check: ✓ handshake |
| Pixelletter MCPSend physical letters and faxes through the PixelLetter interface, test mode included. | Local · stdio |
| PixlintLint, curate & prepare computer-vision datasets from your AI assistant - MCP server, 67 tools. | Local · stdio |
| Pizza DeveloperWork management for AI agents: plan Ideas, Batches and Works, keep context, ship Deliveries. | Remote · HTTPLive check: sign-in required |
| pkgproofVerify an npm package before you install it: advisories, install scripts, typosquats, provenance. | Local · stdio |