MACLookup MCP Server

At a glance

Runs where

On their server. What you send to it goes to them.

What you need

Nothing: it answered without a login

Tools

2 tools

Its own safety labels

2 read-only

Memory it takes

About 1,800 tokens of your AI's memory, just for its tool descriptions

Largest answer

About 0.8 KB in our test

Speed

Average answer in our test: 274 ms

Tokens are an estimate: the characters in its tool names, descriptions and inputs, divided by 4. The exact number depends on your AI model. Safety labels are what the server says about itself. From our latest test, 7 Nov 2026.

Is MACLookup MCP Server server safe?

• None of the hidden-instruction wordings we know were found in its 2 tool descriptions.
• Its error messages showed no secrets or internal details.
• All 2 of its tools are labeled read-only.
• Overall it scored 100/100 on 7 Nov 2026.

A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.

What this test does not check

• Its source code and packages.
• What a tool quietly does behind the scenes, such as writing a file or calling another service.
• Instructions hidden inside live tool answers. We only look for those in tool descriptions.
• Hidden instructions worded in a way our list doesn't know yet.
• Tools that could change something. Those are read, never run.

What QAmcp can and can't see · How to tell if an MCP server is safe · Hidden instructions · Prompt injection

Known security advisories

It lists no public code, so there is nothing to look up in GitHub Security Advisories or OSV.dev. QAmcp tests how a server behaves. It does not scan source code.

What it can do

2 tools, in the server's own words.

Test results

Safe mode: only tools labeled read-only were run. How the test works

• !
  Follows MCP best practices (not scored yet)

  1 tip (not scored)

  • !batch_lookup_mac: Labeled read-only, but it has a "macAddresses" input described as "raw command". A read-only label can't promise much when the tool runs whatever it's sent; make the tool itself refuse changes (for example with a read-only database user), o
  note
• ✓
  ConnectsConnected in 504 ms
  pass
• ✓
  Ready for the newest MCP versionUses the latest MCP version (2026-07-28)
  pass
• ✓
  Lists its toolsFound 2 tools
  pass
• ✓
  Every tool is describedAll 2 tools and their inputs are described
  pass
• ✓
  Tools are labeled safe or dangerousEvery tool has a safety label
  pass
• ✓
  No known hidden instructionsNone of the hidden-instruction wordings we know were found in tool descriptions. New wordings can get past this check.
  pass
• ✓
  Tools work with good inputs

  All good

  • ✓lookup_mac: Worked (274 ms)
  • –batch_lookup_mac: Not run: labeled read-only, but it has a "macAddresses" input described as "raw command", so what it does depends on what it's sent. Skipped to be safe: if you own this server, test again with --owner
  pass
• ✓
  Bad inputs give a clean error

  All good

  • ✓lookup_mac: Refused missing required input "mac" with a clear error
  • ✓lookup_mac: Refused wrong type for "mac" with a clear error
  pass
• ✓
  Fast enough

  All good

  • ✓Connecting took 504 ms
  • ✓Listing tools took 353 ms
  • ✓Average tool answer: 274 ms
  • ✓lookup_mac: Slowest tool: lookup_mac (274 ms)
  pass
• ✓
  No secrets leakedChecked 2 error messages: no secrets or internal details
  pass
• –
  Tools work togetherNo tool's answer could be fed into another tool, so there were no chains to test (not counted either way)
  not tested

Test it yourself

Free and open source. Same checks, same score.

Show this score on GitHub

Free for every server in the directory. Paste this into your README: the badge shows the score from our latest test.

Score over time

• 7 Nov 2026100

One test so far. New tests will show here.

Reviews

Coming soon: reviews from people who use MACLookup MCP Server, signed in with GitHub, one per person. Reviews never change the score.