
Connects Claude to the macvendors.com API for looking up hardware manufacturers from MAC addresses. The OUI (Organizationally Unique Identifier) lookup tells you which company made a given network device based on the first half of its MAC address. Handy when you're troubleshooting network issues, auditing devices on a network, or building tools that need to identify hardware vendors. Part of the Pipeworx gateway ecosystem, so you can either use the standalone endpoint or bundle it with 808+ other data sources through their unified gateway. Supports the ask_pipeworx pattern for plain English queries instead of direct tool calls.
macvendors.com MCP — MAC address (OUI) → hardware manufacturer lookup.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
lookup | macvendors.com = MAC address → hardware manufacturer (OUI) lookup; pass a full MAC or just the first 6 hex digits. Keyless; free tier is rate-limited to ~1 request/second. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"macvendors": {
"url": "https://gateway.pipeworx.io/macvendors/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/macvendors/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Macvendors data" })
The gateway picks the right tool and fills the arguments automatically.
MIT
curl -X POST https://gateway.pipeworx.io/v1/tools/macvendors_lookup \
-H 'Content-Type: application/json' \
-d '{"mac":"FC:FB:FB:01:02:03"}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/macvendors_lookup. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.