io.github.aimnis/search
REMOTE · AIMNIS.COM · SCANNED AUG 3
Collaborative, cache-first web search for agents — cited answers from a shared live-web pool.
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 →
Endpoint Security60
- 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 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. 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · aimnis.com
claude mcp add --transport http aimnis-search https://aimnis.com/mcp
[mcp_servers.aimnis-search] url = "https://aimnis.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"aimnis-search": {
"type": "remote",
"url": "https://aimnis.com/mcp",
"enabled": true
}
}
} openclaw mcp add aimnis-search --url https://aimnis.com/mcp --transport streamable-http
mcp_servers:
aimnis-search:
url: "https://aimnis.com/mcp" {
"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.
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.
- 3 Aug 26 +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.
- 31 Jul 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
- 30 Jul 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
- 28 Jul 26 +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.
- 27 Jul 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
- 26 Jul 26 61
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 3 Aug 2026 · Probed https://aimnis.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=aimnis.com | CN=WE1,O=Google Trust Services,C=US | 3 Jul 2026 | 1 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 42b92bb4be2817c50e112317a8dd1b55 |
| SANs: aimnis.com, *.aimnis.com | ||||||
| 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 |
DNSSEC secure
Validation of aimnis.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| aimnis.com. | present | 2371 | 13 | Verified |
| aimnis.com. | Verified address RRset verified with the apex keys |
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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://aimnis.com/mcp | Verified | 200 | |
| http (plaintext) | http://aimnis.com/mcp | HTTPS enforced | 301 | https://aimnis.com/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.
register ~174
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
search ~187
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
stats ~79
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.