Agent Wikis
REMOTE · AGENTWIKIS.COM
Maintained, agent-readable knowledge bases with calibrated search and provenance. Pro key adds XL.
Available components
Last scanned (16 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Memory and Knowledge
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability70
- AI-judged instruction clarity (excellent).Pass
- 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. 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +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.
- 18 Nov 26 +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.
- 15 Nov 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.
- 14 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Nov 26 73
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 21 Nov 2026 · Probed https://agentwikis.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agentwikis.com | CN=YR2,O=Let's Encrypt,C=US | 10 Nov 2026 | 8 Feb 2027 | RSA 2048 | SHA256-RSA | 6c4822fc8505b3d58de3aba1c356dbde12b |
| SANs: agentwikis.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agentwikis.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| agentwikis.com. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'none'; style-src 'self'; img-src 'self' data: https:; font-src 'self'; connect-src 'self'; base-uri 'none'; form-action 'self' https://checkout.stripe.com https://billing.stripe.com; frame-ancestors 'none'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agentwikis.com/mcp | Verified | 200 | |
| http (plaintext) | http://agentwikis.com/mcp | HTTPS enforced | 301 | https://agentwikis.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. 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 →
list_agent_tools List agent tools ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Optional keywords, matched against the name, summary and specialist. |
No output schema declared.
No examples provided.
list_routines List routines ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Optional keywords, matched against the name, specialist and skills. |
No output schema declared.
No examples provided.
list_skills List skills ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Optional keywords; every term must appear in the name, description or backing wiki. |
No output schema declared.
No examples provided.
list_wikis List wikis ~83
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
open_wiki Open a wiki ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| wiki | string | yes | Wiki slug, e.g. "hermes". |
No output schema declared.
No examples provided.
read_agent_tool Read an agent tool ~185
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Tool name from list_agent_tools, e.g. "copy-lint". |
| path | string | – | Optional file within the tool, as listed by read_agent_tool. |
No output schema declared.
No examples provided.
read_document Read a document ~228
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".
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | 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 | yes | Wiki slug, e.g. "llama-cpp". |
No output schema declared.
No examples provided.
read_routine Read a routine ~180
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | 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. |
No output schema declared.
No examples provided.
read_skill Read a skill ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | 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. |
No output schema declared.
No examples provided.
search Search wikis ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Natural-language or keyword query. |
| wiki | string | – | Optional wiki slug to restrict the search. Omit to search all wikis. |
No output schema declared.
No examples provided.
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.
remote · agentwikis.com
claude mcp add --transport http tonbistudio-agentwikis-mcp 'https://agentwikis.com/mcp'
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.