# io.github.engrossa/ipnex (remote · api.ipnex.ai)

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

- Trust score: 59/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.ipnex.ai`: 59/100 (this document), [markdown](https://verifymcp.io/servers/engrossa-ipnex/api.md), [page](https://verifymcp.io/servers/engrossa-ipnex/api)

## Channel facts

- Endpoint: `https://api.ipnex.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1002 tokens (~501/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http engrossa-ipnex https://api.ipnex.ai/mcp
```

### Codex

```toml
[mcp_servers.engrossa-ipnex]
url = "https://api.ipnex.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "engrossa-ipnex": {
      "type": "remote",
      "url": "https://api.ipnex.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add engrossa-ipnex --url https://api.ipnex.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  engrossa-ipnex:
    url: "https://api.ipnex.ai/mcp"
```

### Other

```json
{
  "mcpServers": {
    "engrossa-ipnex": {
      "type": "http",
      "url": "https://api.ipnex.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 58, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 57, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 57, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 56, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 55, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 55)

First indexed and scored.

## MCP tools (2)

### `search_licensable_ip` (~348 tokens)

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.

Input parameters:

- `institution` (string): Marketing institution substring, e.g. 'Wisconsin', 'Stanford'.
- `keyword` (string): Substring matched against the title and our summary.
- `licensable_from_institution` (boolean): When true, exclude hits whose patent's current assignee of record is positively not the marketing institution (assigned-away or third-party owned); honest-unknowns are kept. Default false.
- `limit` (integer): Max results to return (confidence-sorted).
- `min_confidence` (number): Drop results below this join confidence (0-1).
- `status` (string): Legal-status substring, e.g. 'Active', 'Expired'.

### `get_technology` (~125 tokens)

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.

Input parameters:

- `as_of` (string): ISO-8601 timestamp for the point-in-time published view.
- `docket` (string, required): The TTO docket id, e.g. 'P160232US05', 'S17-467'.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/engrossa-ipnex/api#diagnostics

## Score history

- 2026-08-03: 59
- 2026-08-02: 59
- 2026-08-01: 58
- 2026-07-31: 58
- 2026-07-30: 57
- 2026-07-29: 57
- 2026-07-28: 56
- 2026-07-27: 55
- 2026-07-26: 55

## Links

- Remote endpoint: https://api.ipnex.ai/mcp
- Changelog RSS feed: https://verifymcp.io/servers/engrossa-ipnex/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/engrossa-ipnex/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/engrossa-ipnex/api