SiteCheck Company Records

MAC address vendor lookup: returns the registered hardware

b2b_macvendors_lookup

Read-only

MAC address vendor lookup (IEEE OUI registry via macvendors.com): returns the registered hardware vendor for a MAC address or OUI prefix. Public free API; vendor name only, no device data. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mac": "<mac>"
    },
    "name": "b2b_macvendors_lookup"
  }
}

Input Schema

Name	Required	Description	Default
`mac`	Yes	MAC address or OUI, e.g. 44:38:39:ff:ef:57 or 443839

Output Schema

Name	Required	Description	Default
`mac`	No
`oui`	No
`source`	No
`vendor`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.2/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond readOnlyHint/openWorldHint, the description discloses source and provenance (IEEE OUI registry via macvendors.com), the exact result scope (vendor name only, no device data), and full commercial behavior: $0.002 USDC per successful call, x402 payment on Base/Solana/Arc, and that failed calls are not charged. That cost-and-charging disclosure is behavior an agent cannot infer from annotations and materially affects invocation decisions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with purpose and followed by scope then pricing; nothing is off-topic. It is slightly dense with payment-rail specifics ('Base, Solana or Arc') that are the least essential content, but they earn their place by describing billing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter lookup with an output schema already present, the description covers everything the agent needs: what it returns, what it does not return, the data source, and the payment model including the no-charge-on-failure rule.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single 'mac' property already carries an example of both accepted forms, so the schema does the heavy lifting. The description restates 'MAC address or OUI prefix' without adding format normalization or edge-case rules, matching the baseline 3 for a fully documented one-parameter schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb-plus-resource statement ('MAC address vendor lookup ... returns the registered hardware vendor for a MAC address or OUI prefix') and names the underlying registry. The resource domain is completely distinct from every sibling tool (business/procurement/health registries), so no sibling disambiguation is needed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is strongly implied: supply a MAC or OUI prefix to get a vendor. The line 'vendor name only, no device data' usefully bounds what an agent should expect, but there is no explicit when-to-use/when-not framing, no mention of what to do when an OUI is unregistered, and no named alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SiteCheck Company Records tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?