# io.github.aimnis/search (remote · aimnis.com)

Collaborative, cache-first web search for agents — cited answers from a shared live-web pool.

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

## Components

- remote · `aimnis.com`: 66/100 (this document), [markdown](https://verifymcp.io/servers/aimnis-search/aimnis.md), [page](https://verifymcp.io/servers/aimnis-search/aimnis)

## Channel facts

- Endpoint: `https://aimnis.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.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**: 60/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 3 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 is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 519 tokens (~173/item across 3 items; 3 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http aimnis-search https://aimnis.com/mcp
```

### Codex

```toml
[mcp_servers.aimnis-search]
url = "https://aimnis.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "aimnis-search": {
      "type": "remote",
      "url": "https://aimnis.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add aimnis-search --url https://aimnis.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  aimnis-search:
    url: "https://aimnis.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "aimnis-search": {
      "type": "http",
      "url": "https://aimnis.com/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-03 (score 66, +1)

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

### 2026-07-31 (score 65, +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 64, +1)

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

### 2026-07-28 (score 63, +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 62, +1)

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

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

First indexed and scored.

## MCP tools (3)

### `search` (~187 tokens)

Search the web via Aimnis.

    Returns cached, provenance-tagged results instantly when the question (or a
    semantically similar one) has been seen before; otherwise fetches live
    results and adds them to the shared knowledge pool. Prefer this for factual
    lookups, library/API/docs questions, and error messages.

    If a cached answer does not match your question (it echoes the question it
    was cached for), retry the same query with `reject_entry` set to the entry id
    from that response — the mismatched entry is skipped and the search runs live.

Input parameters:

- `query` (string, required): The natural-language question, error message, or library/API/docs lookup to search for.
- `reject_entry`: Entry id from a previous response whose cached answer did not match your question; set it to skip that entry and force a live search on retry.

Output parameters:

- `result` (string)

### `stats` (~79 tokens)

Report Aimnis flywheel statistics: knowledge-pool (cache) size, cache hit
    rate (all-time and recent), and the most-reused queries.

    This is the Gate 1 pass/kill metric — cache hit rate should climb as the
    corpus grows. Call it to see whether the compounding-pool thesis is holding.

Output parameters:

- `result` (string)

### `register` (~174 tokens)

Get your user a free Aimnis API key (no credit card, takes one call).

    Ask your user for their email address first. The key comes back in this tool
    result — relay it to the user so they can save it and add it to your MCP
    connection ('Authorization: Bearer aim_...'). A key raises the daily
    live-search limits; cached answers are always free, with or without a key.
    Re-registering with the same email rotates (replaces) that email's key.

Input parameters:

- `email` (string, required): Your USER'S email address — ask them for it first, never invent or guess one. The key is returned in this result and a copy is emailed to this address.
- `use_case`: Optional one-line note on what the key will be used for.

Output parameters:

- `result` (string)

## Diagnostics

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

## Score history

- 2026-08-03: 66
- 2026-08-02: 65
- 2026-08-01: 65
- 2026-07-31: 65
- 2026-07-30: 64
- 2026-07-29: 63
- 2026-07-28: 63
- 2026-07-27: 62
- 2026-07-26: 61

## Links

- Remote endpoint: https://aimnis.com/mcp
- Authorisation metadata: https://aimnis.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/aimnis/aimnis
- Website: https://aimnis.com/
- Changelog RSS feed: https://verifymcp.io/servers/aimnis-search/aimnis/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/aimnis-search/aimnis/changelog.json
- HTML version of this page: https://verifymcp.io/servers/aimnis-search/aimnis