Databases

device.dev

Enables searching and retrieving cited hardware component, module, and dev-board data by attributes, MPN, category, or manufacturer.

1 endpoint19 known toolsFirst detected October 4, 2026Last detected October 4, 2026

ENDPOINT 1

https://mcp.device.dev/mcp

No auth detected

MCP server metadata

Name: device-dev-mcp
Version: 0.1.0

Capabilities

tools.listChanged

Server instructions

device.dev answers questions about electronic parts from a cited corpus. Rules across tools: 1. Branch on `outcome`, never on whether a field is null or empty. 2. A negative answer (miss, unknown, not_stated, held: false, *_NOT_FOUND) is about device.dev's corpus, never the world: keep a part you verified elsewhere. 3. A tool error carries no `outcome` and never means not stated. 4. Retry SERVICE_UNAVAILABLE after a pause; never retry INTERNAL, which fails the same way again. 5. A part number from a user, datasheet or distributor goes to resolve_hardware first, with its maker, no other words; then get_hardware (facts), ask_hardware (one value) or get_hardware_manifest (pins). 6. A miss (HARDWARE_NOT_FOUND, not_held, held: false) covers that address only. Its `next` NAMES the read door, not your next call: search first. 7. Addresses are case-sensitive: pass each exactly as returned, never retyped or recased. 8. A key repeats, one row per qualifier and condition: pick by qualifier and condition, never by position (size a rail on the max). A ± rating is one max row; the quote alone carries its sign. 9. A typical (typ) value never satisfies a threshold query. 10. MCP refuses an unknown argument, even nested, naming it; REST ignores one. 11. Paged {items, total, nextOffset?}: `total` counts every match; follow nextOffset until absent. 12. Never send platform-stamped `provenance`, `related`, `coverage`, facts[].citation, artifacts[].retrievalNote, artifacts[].image. 13. A citation names the document device.dev read, not always the manufacturer's: check safety-critical values against the manufacturer's own. Full reference: <https://device.dev/mcp.md>

Known tools 19

list_categories

List the device.dev category vocabulary: each category's slug (the `category` other tools take), name, and attribute and part counts.

Inferred read-only

list_attributes

Inferred read-only

get_account

Your own account: handle, plan, scopes, the credit wallet and request quota.

Inferred read-only

filter_hardware

Select parts, modules and dev boards by numbers (clock, flash, voltage…), MPN substring, category, kind or manufacturer: "which parts have at least N of X".

Inferred read-only

get_hardware

One part's cited record by manufacturerSlug and mpn: attributes, `coverage`, document shelf, related edges and `tier`; no structures.

Inferred read-only

ask_hardware

Answer ONE named question about one part from its facts and recorded observations, never its pins or GPIO.

Inferred read-only

search

Resolve a query you can name (part number, package, series, manufacturer) to ONE entity and its manifest, not a ranked page.

Inferred read-only

resolve_hardware

Turn a loose part string into a canonical manufacturer and MPN.

Inferred read-only

search_entities

Search every entity type (parts, manufacturers, software, standards, certifications, suppliers, part families and series, documents) by name or slug substring, optionally limited to `types`.

Inferred read-only

get_related

Every graph edge touching one entity, both directions, each resolved to the entity at its other end.

Inferred read-only

get_hardware_manifest

Generate a part's hardware.json: facts, structures (pinouts, registers, electrical, memories), edges, artifacts.

Inferred read-only

get_hardware_image

Read one image of a held part by the sha256 of its role-image artifact: the raw bytes, base64, with media type and pixel size.

Inferred read-only

get_software_manifest

Generate a software package's software.json (SDK, RTOS, framework, library, driver, toolchain, tool): identity (namespace, name, kind), homepage and registry URLs, and the parts it runs on.

Inferred read-only

get_device_manifest

Generate a composed device's device.json: its bill of materials (hardware and software rows) and the device's own facts.

Inferred read-only

get_compliance_manifest

Generate compliance.json for a standard, regulation or protocol spec: name, issuing body, identifier, standardKind (protocol, regulatory, safety, environmental, industry), and url and description when held.

Inferred read-only

list_findings

List the closed catalog of finding codes validate_manifest, submit_manifest and their REST twins return: {code, severity, meaning} each.

Inferred read-only

validate_manifest

Validate a manifest of any device.dev profile and say what submit_manifest will do with it.

Inferred read-only

submit_manifest

Publish a manifest to the device.dev corpus, through REST's POST /v1/manifests/submit door.

Potential side effects

request_hardware

NOT_ENABLED on device.dev's hosted MCP today.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.device-dev-mcp]
url = "https://mcp.device.dev/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "device-dev-mcp": {
      "type": "http",
      "url": "https://mcp.device.dev/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: device-dev-mcp
Remote MCP URL: https://mcp.device.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "device-dev-mcp": {
      "url": "https://mcp.device.dev/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "device-dev-mcp": {
      "type": "http",
      "url": "https://mcp.device.dev/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "device-dev-mcp",
  "transport": "streamable-http",
  "url": "https://mcp.device.dev/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.