io.github.engrossa/ipnex
REMOTE · API.IPNEX.AI · SCANNED SEP 20
Cited, confidence-stamped patent intelligence over US university tech-transfer out-licensing.
Available components
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.engrossa/ipnex MCP server?
io.github.engrossa/ipnex is a hosted endpoint at https://api.ipnex.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.ipnex.ai
claude mcp add --transport http engrossa-ipnex 'https://api.ipnex.ai/mcp'
{
"mcpServers": {
"engrossa-ipnex": {
"url": "https://api.ipnex.ai/mcp"
}
}
} {
"servers": {
"engrossa-ipnex": {
"type": "http",
"url": "https://api.ipnex.ai/mcp"
}
}
} [mcp_servers.engrossa-ipnex] url = "https://api.ipnex.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"engrossa-ipnex": {
"type": "remote",
"url": "https://api.ipnex.ai/mcp",
"enabled": true
}
}
} openclaw mcp add engrossa-ipnex --url 'https://api.ipnex.ai/mcp' --transport streamable-http
mcp_servers:
engrossa-ipnex:
url: "https://api.ipnex.ai/mcp" {
"McpServers": {
"engrossa-ipnex": {
"Transport": "http",
"Url": "https://api.ipnex.ai/mcp"
}
}
} assistant mcp add engrossa-ipnex -t streamable-http -u 'https://api.ipnex.ai/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.ipnex.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.ipnex.ai | CN=WE1,O=Google Trust Services,C=US | 2 Aug 2026 | 31 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | c19d066301da4cb10edb7bb0f4f73efb |
| SANs: api.ipnex.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.ipnex.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| ipnex.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.ipnex.ai/mcp | Verified | 200 | |
| http (plaintext) | http://api.ipnex.ai/mcp | HTTPS enforced | 301 | https://api.ipnex.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_technology ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | ISO-8601 timestamp for the point-in-time published view. |
| docket | string | yes | The TTO docket id, e.g. 'P160232US05', 'S17-467'. |
No output schema declared.
No examples provided.
search_licensable_ip ~348
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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'. |
No output schema declared.
No examples provided.
What is the io.github.engrossa/ipnex MCP server?
io.github.engrossa/ipnex is an MCP server listed in the public MCP registry as io.github.engrossa/ipnex. Cited, confidence-stamped patent intelligence over US university tech-transfer out-licensing. This page covers its hosted endpoint (https://api.ipnex.ai/mcp).
Is the io.github.engrossa/ipnex MCP server safe to use?
io.github.engrossa/ipnex scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.engrossa/ipnex MCP server expose?
io.github.engrossa/ipnex exposes 2 tools: search_licensable_ip, get_technology. Their descriptions and schemas cost roughly 473 tokens of context every time the server is loaded.
Does the io.github.engrossa/ipnex MCP server require authentication?
No. We connected to io.github.engrossa/ipnex without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.engrossa/ipnex MCP server still maintained?
io.github.engrossa/ipnex is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.