# Agent Wikis (remote · agentwikis.com)

Maintained, agent-readable knowledge bases with calibrated search and provenance. Pro key adds XL.

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `agentwikis.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/tonbistudio-agentwikis-mcp/agentwikis.md), [page](https://verifymcp.io/servers/tonbistudio-agentwikis-mcp/agentwikis)

## Channel facts

- Endpoint: `https://agentwikis.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.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-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1676 tokens (~167/item across 10 items; 10 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Agent Wikis MCP server?

Agent Wikis is a hosted endpoint at https://agentwikis.com/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.

### Claude

```bash
claude mcp add --transport http tonbistudio-agentwikis-mcp 'https://agentwikis.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tonbistudio-agentwikis-mcp": {
      "url": "https://agentwikis.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tonbistudio-agentwikis-mcp": {
      "type": "http",
      "url": "https://agentwikis.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tonbistudio-agentwikis-mcp]
url = "https://agentwikis.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add tonbistudio-agentwikis-mcp --url 'https://agentwikis.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tonbistudio-agentwikis-mcp:
    url: "https://agentwikis.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tonbistudio-agentwikis-mcp": {
      "Transport": "http",
      "Url": "https://agentwikis.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tonbistudio-agentwikis-mcp -t streamable-http -u 'https://agentwikis.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "tonbistudio-agentwikis-mcp": {
      "type": "http",
      "url": "https://agentwikis.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-11-20 (score 76, +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-11-18 (score 75, +1)

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

### 2026-11-15 (score 74, +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-11-14 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-13 (score 73)

First indexed and scored.

## MCP tools (10)

### `list_wikis` (~83 tokens)

List wikis

List all available wikis with metadata: slug, title, description, tags, status, last updated, document count, and `scope` (what each wiki covers, what it does NOT cover, and how current it is — use this to pick a wiki and to decide when to fall back to web search). Includes "coming soon" placeholders, marked by status.

### `open_wiki` (~93 tokens)

Open a wiki

Orient yourself in one wiki, in a single call: returns its metadata, `scope` (coverage / not-covered / freshness), document count, the entry document, and a `map` of all documents (paths + titles, grouped by folder) so you can pick what to read_document next. Use a slug from list_wikis.

Input parameters:

- `wiki` (string, required): Wiki slug, e.g. "hermes".

### `read_document` (~228 tokens)

Read a document

Read one document in a wiki. Without `section`, returns the full Markdown (frontmatter stripped) plus a provenance footer. To save tokens on a long page, pass `section` (a heading title as it appears in the page body, or its slug anchor) to retrieve ONLY that section and its subsections. The Markdown may contain [[wikilinks]] to related docs — follow one by calling read_document with path "wiki/<target>.md" (drop any "#anchor" or "|label"). Exception: on a page under wiki-xl/, links whose first folder is not concepts, entities, summaries, syntheses, presentations or journal (e.g. [[reference/...]], [[guides/...]], [[history/...]]) are XL pages: use "wiki-xl/<target>.md".

Input parameters:

- `path` (string, required): Document path within the wiki, e.g. "wiki/concepts/setup.md".
- `section` (string): Optional. A section anchor or heading title to read just that part.
- `wiki` (string, required): Wiki slug, e.g. "llama-cpp".

### `search` (~132 tokens)

Search wikis

Find the best-matching PAGES for a query, ranked by how many of your query terms each page covers. Searches one wiki if `wiki` is given, otherwise every active wiki. Each result has its wiki, path, matched terms, and a short snippet for orientation — then read_document the page to get the answer. Returns a `confident` flag: if false, the wiki(s) likely lack this — fall back to web search.

Input parameters:

- `query` (string, required): Natural-language or keyword query.
- `wiki` (string): Optional wiki slug to restrict the search. Omit to search all wikis.

### `list_skills` (~129 tokens)

List skills

List the agent skills library: field-tested procedures for specific jobs (e.g. benchmarking a local model, building a browser game, producing a video). Each entry has name, one-line description (when to use it), `access` ("free" or "pro"), `readable` (whether YOU can read it with your current access), the backing wiki if any, and file count. Pass `query` to filter by keywords. Then read_skill a matching skill and follow it.

Input parameters:

- `query` (string): Optional keywords; every term must appear in the name, description or backing wiki.

### `read_skill` (~151 tokens)

Read a skill

Load one skill to follow it. Without `path`, returns its SKILL.md (the procedure itself) plus the list of its other files; pass `path` (e.g. "references/gotchas.md" or "scripts/check.py") to read one of those. If the skill names a backing wiki, use search/read_document on that wiki for current facts while following it. Pro skills need a Pro key; without one you get a preview and how to unlock it.

Input parameters:

- `name` (string, required): Skill name from list_skills, e.g. "llm-inference".
- `path` (string): Optional file within the skill, as listed by read_skill. Defaults to SKILL.md.

### `list_agent_tools` (~166 tokens)

List agent tools

List the command-line tools that ship with the specialist agents (complete agents built for one job, e.g. marketing, video generation, local LLMs). Each entry has a summary, the `specialists` it comes from, and `access`: "pro" tools are read-only (they inspect and report, never change anything) and read_agent_tool serves their files; "download" tools are bigger or change things (start runs, stop services, spend money), so read_agent_tool gives a short-lived download link for the whole tool instead. Both need Pro. `readable` says whether YOU can get it with your current access. Pass `query` to filter by keywords.

Input parameters:

- `query` (string): Optional keywords, matched against the name, summary and specialist.

### `read_agent_tool` (~185 tokens)

Read an agent tool

Load one agent tool by name. A "pro" (read-only) tool: its README (what it checks, how to run it) plus its file list. Add `path` to read one listed file, e.g. the source. The tool runs on the user's machine, not here. Before saving, running or scheduling anything from it, show the user what it does and get their explicit OK. Each file comes with its sha256. For a "download" tool you get its README and a download link (valid 15 minutes) with the archive's sha256 instead. Needs a Pro key; without one you get the summary and how to unlock it.

Input parameters:

- `name` (string, required): Tool name from list_agent_tools, e.g. "copy-lint".
- `path` (string): Optional file within the tool, as listed by read_agent_tool.

### `list_routines` (~102 tokens)

List routines

List the routines (scheduled jobs) that ship with the specialist agents: each has a schedule, the `specialist` it comes from, the skills its prompt relies on, and whether it is script only (no agent). `readable` says whether YOU can load it with your current access. Pass `query` to filter by keywords. Then read_routine one.

Input parameters:

- `query` (string): Optional keywords, matched against the name, specialist and skills.

### `read_routine` (~180 tokens)

Read a routine

Load one routine by name: the schedule, the agent prompt, and the list of scripts and settings it needs. Add `path` to read one listed file (e.g. "scripts/ad_report.py"). Nothing runs here: the routine is set up and run on the user's machine. Before saving, running or scheduling anything from it, show the user what it does and get their explicit OK. Never create the scheduled job without the user's confirmation. Each file comes with its sha256. Needs a Pro key; without one you get how to unlock it.

Input parameters:

- `name` (string, required): Routine name from list_routines, e.g. "daily-ad-report".
- `path` (string): Optional file within the routine, as listed by read_routine.
- `specialist` (string): Only needed if two specialists ship a routine with the same name.

## Diagnostics

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

## Score history

- 2026-11-21: 76
- 2026-11-20: 76
- 2026-11-19: 75
- 2026-11-18: 75
- 2026-11-17: 74
- 2026-11-16: 74
- 2026-11-15: 74
- 2026-11-14: 73
- 2026-11-13: 73

## Common questions

### What is the Agent Wikis MCP server?

Agent Wikis is an MCP server listed in the public MCP registry as io.github.tonbistudio/agentwikis-mcp. Maintained, agent-readable knowledge bases with calibrated search and provenance. Pro key adds XL. This page covers its hosted endpoint (https://agentwikis.com/mcp).

### Is the Agent Wikis MCP server safe to use?

Agent Wikis scores 76 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 Agent Wikis MCP server expose?

Agent Wikis exposes 10 tools: list_wikis, open_wiki, read_document, search, list_skills, and 5 more. Their descriptions and schemas cost roughly 1,449 tokens of context every time the server is loaded.

### Does the Agent Wikis MCP server require authentication?

No. We connected to Agent Wikis without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Agent Wikis MCP server still maintained?

Agent Wikis is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Agent Wikis MCP server?

VerifyMCP ran 13 checks on Agent Wikis, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://agentwikis.com/mcp
- Repository: https://github.com/tonbistudio/agentwikis-mcp
- Website: https://agentwikis.com/for-agents
- Changelog RSS feed: https://verifymcp.io/servers/tonbistudio-agentwikis-mcp/agentwikis.xml
- Changelog JSON feed: https://verifymcp.io/servers/tonbistudio-agentwikis-mcp/agentwikis/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/tonbistudio-agentwikis-mcp/agentwikis.json
- HTML version of this page: https://verifymcp.io/servers/tonbistudio-agentwikis-mcp/agentwikis
