Mcp Rpcbind
Expose rpcbind and RPC portmapper controls to your agent when you maintain legacy UNIX services or audit RPC exposure in lab infrastructure.
Overview
io.github.daedalus/mcp-rpcbind is a MCP server for the Operate phase that exposes rpcbind and RPC portmapper functionality to AI models.
What is this MCP server?
- MCP server mcp-rpcbind v0.1.0 on PyPI exposing rpcbind/RPC portmapper functionality via stdio
- Lets agents query or manage RPC program-to-port mappings on compatible hosts
- Targets operators debugging NFS, NIS, or other legacy RPC stacks in controlled environments
- Source repository github.com/daedalus/mcp-rpcbind with MCP registry metadata
- Niche infrastructure bridge—use strict network isolation because portmapper interfaces are sensitive
- Server version 0.1.0 with stdio transport via PyPI identifier mcp-rpcbind
- Registry description: exposes rpcbind/RPC portmapper functionality
What problem does it solve?
Legacy RPC services hide program-to-port mappings behind rpcbind, and your agent cannot diagnose registration issues without dedicated tooling.
Who is it for?
Operators and security testers maintaining isolated legacy UNIX/NFS lab systems who need MCP-guided rpcbind inspection.
Skip if: Typical greenfield SaaS on serverless or container platforms with no ONC RPC dependencies.
What do I get? / Deliverables
After installation, your agent can interact with portmapper operations through MCP while you document infra or security posture changes.
- MCP tool access to rpcbind/portmapper operations on configured hosts
- Agent-assisted diagnosis of RPC program and port mappings
- Documented infra or security review steps for legacy RPC exposure
Recommended MCP Servers
Journey fit
Rpcbind/portmapper concerns appear when you operate or harden legacy network services—not during greenfield SaaS UI work. Infra subphase is the right shelf for MCP tools that manipulate low-level RPC registration and portmapping on servers you already run.
How it compares
Legacy RPC portmapper MCP bridge, not a cloud load-balancer or modern gRPC service mesh skill.
Common Questions / FAQ
Who is mcp-rpcbind for?
Builders and operators who still run or audit ONC RPC style services and want agent-driven rpcbind/portmapper access via MCP.
When should I use mcp-rpcbind?
Use it during Operate infra work when debugging RPC registrations, NFS-related port issues, or lab pentests on portmapper exposure.
How do I add mcp-rpcbind to my agent?
Install mcp-rpcbind from PyPI, configure stdio MCP on a hardened jump host with rpcbind available, wire the server into Claude Code or Cursor, and restrict network access to lab targets only.