MacAdress - The MacAddress Lookup
About
Connect AI agents to macadress.com for real-time MAC address and OUI vendor lookups via MCP. Identify manufacturers, IEEE assignments, address types, and randomization indicators using your existing API key, with no separate account required.
Details
- Author
- Unknown
- Categories
- Developer Tools, Infrastructure, API, Other
Jump to
Connect AI agents to macadress.com for real-time MAC address and OUI vendor lookups via MCP. Identify manufacturers, IEEE assignments, address types, and randomization indicators using your existing API key, with no separate account required.
The same MAC/OUI vendor lookup as tools an AI agent can call directly, over Model Context Protocol. Same data, same API key, no separate account.
Endpoint:https://mcp.macadress.com/mcp, Streamable HTTP transport, stateless, no session to manage.
Point any MCP-compatible client at the endpoint above and authenticate with the same API key the REST API uses (sign upfor one, visible any time on youraccount page): send it as anAuthorization: Bearerheader. There's no separate OAuth connect flow: the MCP spec makes authorization optional for HTTP transports, and a bearer token is spec-legal without running a full OAuth 2.1 authorization server. If your client supports a raw JSON config, this is the shape most expect:
{ "mcpServers": { "macadress": { "url": "https://mcp.macadress.com/mcp", "headers": { "Authorization": "Bearer mk_your_api_key" } } } }
Every tool call is authenticated and billable; there's no free tier of tools here the way/v1/healthzis free on the REST API.
Enforced against the same per-plan numbers as the REST API (seepricingand theAPI docs' rate-limit/quota sections). A key's monthly lookup budget and requests-per-minute cap are shared concepts across both surfaces, even though each runs as its own process and converges its usage count independently rather than sharing one live counter.
MCP's authorization spec is optional for HTTP transports, not required. Implementing it (PKCE, dynamic client registration, a resource-metadata endpoint) buys one-click "connect your account" provisioning in clients that support it, at the cost of running a real authorization server. Pasting an existing API key works today in every MCP client we're aware of and is exactly as secure as the header the REST API already accepts.
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
GeoIP and ASN intelligence for AI agents with country, city, timezone, network ownership and ASN lookups.
Real-time Amazon data API built for AI agents. 200M+ products, 1B+ reviews, live BSR, pricing, and competitor data as clean JSON. 10 agent skills for market research, competitor monitoring, pricing, listing audits, and more. 1,000 free credits.
MCP to read the Codex crypto data API so agents can write GraphQL queries.
A high-performance MCP server providing structured, real-time price data for AI hardware across global marketplaces, built with a focus on agent-native discovery over hardcoded endpoints.
Interact with Alchemy's blockchain APIs to query data without writing code.
A hosted API /MCP platform providing developer-friendly JSON endpoints for user-agent parsing, postal code search with spatial queries, country/subdivision lookup, cryptographic hashing, IP geolocation, email risk scoring, and more.
Integrates the Korea Meteorological Administration's public weather API to provide climate data.
Query the BuiltWith API to discover the technology stacks of websites. Requires a BuiltWith API key.
An MCP server for interacting with the Clay API, which requires a Clay API key.
Coral Query Plane is a paid remote MCP endpoint for AI SDK data query MCP. It exposes structured JSON tools, a public server card, token-based access, usage receipts, and audit-ready workflo
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
