mcpbeat

Ipnex MCP Server

io.github.engrossa/ipnex
answering

Ipnex is answering right now. Last checked 8 min ago. It exposes 2 tools.

Cited, confidence-stamped patent intelligence over US university tech-transfer out-licensing.

Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
359 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add ipnex --transport http https://api.ipnex.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "ipnex": {
      "url": "https://api.ipnex.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.ipnex]
url = "https://api.ipnex.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "ipnex": {
      "url": "https://api.ipnex.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "ipnex": {
      "url": "https://api.ipnex.ai/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

licensable
search_licensable_ip
Search published, licensable US university patent technologies. Answers 'what currently-Active US university IP is licensable from X?'. Every result is cited (Google Patents / USPTO), confidence-stamped, and carries an 'ownership' signal flagging whether the patent's current assignee of record is the marketing institution or a third party, a 'status' interpretation flagging public-domain (term-expired) vs revivable fee-lapsed vs in-force patents, and an 'expiry' reading of how many years of exclusive term remain (expired / expiring_soon / active_term). The response also carries 'facets' -- corpus-level breakdowns over all matches by ownership, institution, status, status_detail, and expiry (the whole-query split, without paging). Patent data: Google Patents (CC BY 4.0) + USPTO (public domain). Summaries are IPNEX-authored. TTO listing content is linked, not reproduced.
technology
get_technology
Fetch the published view of one technology by its TTO docket. Cited + confidence-stamped; point-in-time via 'as_of'. Patent data: Google Patents (CC BY 4.0) + USPTO (public domain). Summaries are IPNEX-authored. TTO listing content is linked, not reproduced.

Endpoints

URLTransportStateLatencyChecked
https://api.ipnex.ai/mcp streamable-http answering 284 ms 8 min ago

Ipnex — questions

Answers built from our own checks of this server.

What can Ipnex do?
It exposes 2 tools, read directly from the server on our last check. Among them: get_technology, search_licensable_ip. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Ipnex working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 359 ms. The bar chart above shows every period we have measured.
How do I connect Ipnex?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Ipnex need an API key?
No. Ipnex completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Ipnex?
It answers our handshake in 359 ms on average, which is faster than 39% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.