← Registry

Databases

ipnex.ai

Provides tools to search and retrieve published, licensable US university patent technologies.

1 endpoint2 known toolsFirst detected August 5, 2026Last detected August 5, 2026

ENDPOINT 1

https://api.ipnex.ai/mcp

No auth detected

MCP server metadata

Name
ipnex
Version
0.2.0
Capabilities
tools
Server instructions

IPNEX serves cited, confidence-stamped patent intelligence over US university technology-transfer (TTO) out-licensing: each marketed technology joined to its real patent picture -- current assignee, live legal status, expected expiry. Call 'search_licensable_ip' to find currently-licensable IP (filter by institution, status, keyword, min_confidence, and licensable_from_institution); call 'get_technology' for the full published view of one TTO docket (point-in-time via 'as_of'). Every result carries an 'ownership' signal -- whether the patent's current assignee of record is the marketing institution or a third party (the patent may not be licensable from that university); set licensable_from_institution=true to exclude the third-party cases. Every result also carries a 'status' interpretation -- the honest reading of the legal status, distinguishing a term-expired patent (public_domain=true: in the public domain, free to practise, nothing left to license) from a revivable fee lapse or a still in-force patent -- and an 'expiry' reading: how many years of exclusive term remain (years_remaining) as of a reference date, and whether it is expired / expiring_soon (under ~2 years left) / active_term, so you can tell a patent marketed as live but nearly out of term from one with two decades to run (status says whether a right exists; expiry says how long it lasts). Each result also carries a 'licensability' score: a gated 0-100 read of whether it is actually licensable, composed from those same ownership + in-force + remaining-term facts (each component shown openly; indicative when an input is unknown). A search response also carries 'facets' -- corpus-level breakdowns over all matches by ownership (institution-owned vs assigned-away / third-party / unknown), by institution, by status (in force vs lapsed vs other vs unknown), by status_detail (the finer split: term-expired vs fee-lapsed vs reinstated ...), and by expiry (expired / expiring_soon / active_term / unknown) -- so you can read the whole-corpus split for a query without paging every result. Every field carries its source citation and a confidence score; unresolved fields are omitted, never guessed -- an unknown docket returns {"found": false}, not an error. Patent data: Google Patents (CC BY 4.0) + USPTO (public domain). Summaries are IPNEX-authored. TTO listing content is linked, not reproduced.

Known tools 2

search_licensable_ip

Search published, licensable US university patent technologies.

Inferred read-only
get_technology

Fetch the published view of one technology by its TTO docket.

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.ipnex]
url = "https://api.ipnex.ai/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "ipnex": {
      "type": "http",
      "url": "https://api.ipnex.ai/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: ipnex
Remote MCP URL: https://api.ipnex.ai/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": {
    "ipnex": {
      "url": "https://api.ipnex.ai/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "ipnex": {
      "type": "http",
      "url": "https://api.ipnex.ai/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "ipnex",
  "transport": "streamable-http",
  "url": "https://api.ipnex.ai/mcp"
}
MCP Inspector

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

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for ipnex.ai was fetched 2026-08-23T10:50:29.094Z.

Trust status Neutral

ipnex.ai is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

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