macadress

io.github.samymassoudPublished by GitHub account samymassoudv1.0.0Updated Oct 25, 2026

MAC address and OUI vendor lookup over Model Context Protocol.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

A remote MCP server that lets an assistant look up MAC addresses and identify the vendor behind an OUI prefix.

What you can do
Look up MAC addresses and resolve them to hardware vendors via OUI data, so an assistant can identify device manufacturers from address prefixes. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when an assistant needs to identify the manufacturer of a network device from its MAC address or OUI prefix, for example during network inventory, troubleshooting, or device classification work.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. A macadress.com API key is required and sent as a bearer token in the Authorization header; the key is obtained by signing up at macadress.com.
Before you install
The API key is a secret sent in the Authorization header, so keep it out of logs and shared transcripts. Lookups are sent to a third-party service (macadress.com), which may log the addresses queried.

Installation

In SourceWeft

  1. Open macadress in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.samymassoud%2Fmacadress/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "macadress": {
      "type": "http",
      "url": "https://mcp.macadress.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.