# Agentic Web Wiki — standards reference, probe, validate, template (remote · agenticweb.wiki)

Look up 133 agentic-web standards, live-probe any domain, validate manifests, generate boilerplate.

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

## Components

- remote · `agenticweb.wiki`: 79/100 (this document), [markdown](https://verifymcp.io/servers/wiki-agenticweb-probe/agenticweb.md), [page](https://verifymcp.io/servers/wiki-agenticweb-probe/agenticweb)

## Channel facts

- Endpoint: `https://agenticweb.wiki/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.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-05.

- **Endpoint Security**: 71/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2532 tokens (~148/item across 17 items; 11 tools + 6 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 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 Agentic Web Wiki — standards reference, probe, validate… MCP server?

Agentic Web Wiki — standards reference, probe, validate… is a hosted endpoint at https://agenticweb.wiki/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 wiki-agenticweb-probe 'https://agenticweb.wiki/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "wiki-agenticweb-probe": {
      "url": "https://agenticweb.wiki/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "wiki-agenticweb-probe": {
      "type": "http",
      "url": "https://agenticweb.wiki/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.wiki-agenticweb-probe]
url = "https://agenticweb.wiki/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wiki-agenticweb-probe": {
      "type": "remote",
      "url": "https://agenticweb.wiki/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add wiki-agenticweb-probe --url 'https://agenticweb.wiki/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  wiki-agenticweb-probe:
    url: "https://agenticweb.wiki/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "wiki-agenticweb-probe": {
      "Transport": "http",
      "Url": "https://agenticweb.wiki/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add wiki-agenticweb-probe -t streamable-http -u 'https://agenticweb.wiki/mcp'
```

### Other

```json
{
  "mcpServers": {
    "wiki-agenticweb-probe": {
      "type": "http",
      "url": "https://agenticweb.wiki/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-05 (score 79, +1)

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

### 2026-11-02 (score 78, +1)

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

### 2026-10-31 (score 77, +1)

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

### 2026-10-29 (score 76, +1)

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

### 2026-10-27 (score 75, +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-10-26 (score 74, 0)

- [security] Tool “validate_manifest” rewrote its description, which is the text the model reads
- [security] Tool “ask” rewrote its description, which is the text the model reads
- [security] Tool “changes” rewrote its description, which is the text the model reads
- [security] Tool “define” rewrote its description, which is the text the model reads
- [security] Tool “digest” rewrote its description, which is the text the model reads
- [security] Tool “get” rewrote its description, which is the text the model reads
- [security] Tool “has” rewrote its description, which is the text the model reads
- [security] Tool “probe” rewrote its description, which is the text the model reads
- [security] Tool “search” rewrote its description, which is the text the model reads
- [security] Tool “stale” rewrote its description, which is the text the model reads
- [security] Tool “template” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 111 → 148
- [functional] Schema quality: good → excellent

### 2026-10-25 (score 74, +3)

- [security] The server changed its declared name: agenticweb.wiki → wiki.agenticweb/probe
- [security] Tool “template” rewrote its description, which is the text the model reads
- [security] Tool “probe” rewrote its description, which is the text the model reads
- [security] Tool “search” rewrote its description, which is the text the model reads
- [security] Tool “validate_manifest” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 75 → 93
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 43% → 100%
- [functional improvement] Tool coverage: 43% → 60%
- [functional] Schema quality: fair → good
- [functional] New resource “census”
- [functional] New resource “versions”
- [functional] Server version: 1.20261025.0 → 1.3.0
- [functional] Server version: 1 → 1.20261025.0
- [cosmetic] “probe” added an optional parameter “fresh”
- [cosmetic] “probe” added an optional parameter “id”
- [cosmetic] “probe” added an optional parameter “verify”
- [cosmetic] “template” added an optional parameter “from_live”
- [cosmetic] “validate_manifest” added an optional parameter “bridge”
- [cosmetic] “validate_manifest” added an optional parameter “content”
- [cosmetic] “validate_manifest” added an optional parameter “content_type”
- [cosmetic] “validate_manifest” added an optional parameter “diff”
- [cosmetic] “validate_manifest” added an optional parameter “fresh”
- [cosmetic] “validate_manifest” added an optional parameter “verify”
- [cosmetic] “stale” reworded the description of “step”
- [cosmetic] “ask” reworded the description of “audience”
- [cosmetic] “ask” reworded the description of “q”
- [cosmetic] “ask” reworded the description of “question”
- [cosmetic] “ask” reworded the description of “use_case”
- [cosmetic] “changes” reworded the description of “limit”
- [cosmetic] “changes” reworded the description of “record_id”
- [cosmetic] “changes” reworded the description of “step”
- [cosmetic] “define” reworded the description of “term”
- [cosmetic] “get” reworded the description of “id”
- [cosmetic] “has” reworded the description of “id”
- [cosmetic] “has” reworded the description of “origin”
- [cosmetic] “probe” reworded the description of “origin”
- [cosmetic] “search” reworded the description of “q”
- [cosmetic] “search” reworded the description of “query”
- [cosmetic] “stale” reworded the description of “days”
- [cosmetic] “template” reworded the description of “description”
- [cosmetic] “template” reworded the description of “name”
- [cosmetic] “validate_manifest” reworded the description of “id”
- [cosmetic] “validate_manifest” reworded the description of “origin”
- [cosmetic] “validate_manifest” made “origin” optional

### 2026-10-24 (score 71, +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.

## MCP tools (11)

### `define` (~105 tokens)

Define an agentic-web glossary term or standard by id, name, or alias. Returns { kind, id, name, definition_md, related_protocols, url } (or nearest-term hints on unknown-term error). Use define for concept definitions; use get when you need a standard's full specification record, or search for keyword discovery.

Input parameters:

- `term` (string, required): glossary term id, name, or alias (e.g. agentic-web, agent card, MCP, x402)

### `get` (~113 tokens)

Fetch one standard's complete specification record by id, acronym, filename, or RFC number. Returns { id, name, step, status, governance, version, spec_url, probe, adoption, summary_md, url } (or unknown-id error with nearest matches). Use get for a known standard; use search to find unknown ids or define for glossary concepts.

Input parameters:

- `id` (string, required): standard id, acronym, filename, or RFC number (e.g. mcp, ard, llms.txt, RFC 9421)

### `search` (~130 tokens)

Search 132 standards and 52 glossary terms by keyword, acronym, alias, or 'A vs B' pair (pass q or alias query, 2–200 chars). Returns { results (top 10 ranked by title/alias/body match), matching_terms, comparison_url } or nearest_ids hints when empty. Use search for keyword discovery; use get for an exact id or ask for stack recommendations.

Input parameters:

- `q` (string): search query or comparison (e.g. agent discovery, A2A vs MCP, accept payments)
- `query` (string): alias for q: search query or comparison

### `has` (~140 tokens)

Check one public origin over HTTPS for a single standard or manifest (rate-limited to 120/min). Returns { origin, id, found, outcome, status, url, reason, article } without grading the full site. Use has for a fast single-file check; use probe to scan all 37 paths at once, or validate_manifest for A+–F conformance grading.

Input parameters:

- `id` (string, required): probed standard id or filename (e.g. ard, llms-txt, mcp-server-cards, robots.txt)
- `origin` (string, required): public hostname to check (e.g. agenticweb.wiki, cloudflare.com)

### `probe` (~284 tokens)

Scan a public origin across 37 agent-facing paths and headers (24h KV cache by default; pass fresh: true to re-probe live with a 5-min per-origin cooldown, rate-limited to 30/min). Returns { found_ids, found, absent, coverage, extracted, connect_recipe }; pass brief: true for found_ids + extracted endpoints only, compact: true to replace absent/skipped maps with absent_ids[], or verify: true to handshake MCP/A2A endpoints. Use probe for raw multi-path discovery; use has for one standard, or validate_manifest for A+–F conformance scoring.

Input parameters:

- `brief` (boolean): true: return only found_ids, non-empty coverage, and key extracted resources
- `compact` (boolean): true: return absent_ids[] instead of full absent/skipped maps
- `fresh` (boolean): true: bypass the 24h KV cache and re-probe live (5-minute per-origin cooldown)
- `id` (string): optional single standard id or filename (e.g. ard, llms.txt) for a lean single-resource check
- `origin` (string, required): public hostname to probe across all 37 paths and HTTP headers (e.g. agenticweb.wiki)
- `verify` (boolean): true: actively handshake declared MCP (POST initialize) and A2A endpoints to verify liveness

### `changes` (~189 tokens)

List machine-verified specification changes since a YYYY-MM-DD date or ISO-8601 timestamp (newest first, default 50, max 200). Returns { since, count, entries: [{ date, record_id, field, old, new, source }] } filtered optionally by lifecycle step or record_id. Use changes for field-level spec diffs; use stale to audit unverified records or digest for daily ecosystem news.

Input parameters:

- `limit` (integer): maximum number of change entries to return (default 50, max 200)
- `record_id` (string): optional standard id or acronym to filter changes (e.g. mcp, a2a, x402)
- `since` (string, required): YYYY-MM-DD or ISO-8601 timestamp
- `step` (string): optional lifecycle step filter (discover, identify, permit, read, act, coordinate, pay, present, account)

### `stale` (~126 tokens)

List standards whose last_verified date is older than N days (default 30, oldest first), optionally filtered by lifecycle step. Returns { threshold_days, count, records: [{ id, name, step, last_verified, days_since_verified }] }. Use stale to audit verification freshness; use changes to inspect actual specification edits since a date.

Input parameters:

- `days` (integer): return standards whose last_verified date is older than this many days (default 30)
- `step` (string): optional lifecycle step filter (discover, identify, permit, read, act, coordinate, pay, present, account)

### `validate_manifest` (~449 tokens)

Audit a public origin across 37 agent manifests (24h KV cache; fresh: true re-probes live with 5-min cooldown, 30/min limit) or validate local file text in-memory before deploy (pass id + content, no network fetch). Returns { grade (A+ to F), score, subscores, conformance_summary, connect_recipe, permissions, manifests }; combine verify: true (live MCP/A2A handshakes), bridge: true (ARD cross-manifest check), diff: true (score_delta vs prior snapshot), or brief/compact payload trimming. Use validate_manifest for conformance grading and local linting; use probe for ungraded discovery or template to generate starter files.

Input parameters:

- `bridge` (boolean): true: fetch and validate each entry inside /.well-known/ard.json or ai-catalog.json against its target spec and check cross-manifest coherence
- `brief` (boolean): true: return concise routing, callable endpoints, subscores, and permissions only
- `compact` (boolean): true: omit nested probe packet and absent manifests
- `content` (string): raw local JSON, Markdown, or text content to validate in-memory without network fetches
- `content_type` (string): optional Content-Type header when validating local content
- `diff` (boolean): true: compare the current report against the previous KV cached snapshot or bundled census baseline (score_delta, manifests_added/removed/changed, new_errors)
- `fresh` (boolean): true: bypass the 24h KV cache and re-probe live (5-minute per-origin cooldown)
- `id` (string): manifest id or filename (ard, ai-catalog-well-known-file, mcp-server-cards, a2a, llms-txt, agents-md, anthropic-agent-skills-format, api-catalog-rfc9727, ai-crawler-tokens-robots, security-txt, auth-…
- `origin` (string): public hostname to fetch (optional when passing content + id for local pre-commit validation)
- `verify` (boolean): true: actively handshake declared MCP and A2A endpoints and withhold credit for dead endpoints

### `template` (~349 tokens)

Generate in-memory starter boilerplate for any of the 12 supported manifest ids (ard, ai-catalog-well-known-file, llms-txt, agents-md, anthropic-agent-skills-format, mcp-server-cards, a2a, ai-crawler-tokens-robots, api-catalog-rfc9727, security-txt, auth-md, okf) without writing to disk. Returns { id, path, content_type, contents, validate_with }; when from_live: true is passed with domain, it probes the public origin over HTTPS to pre-fill discovered MCP, OpenAPI, A2A, and contact URLs. Use template to author a new manifest; use validate_manifest to lint existing content.

Input parameters:

- `agent_url` (string): https URL of A2A endpoint
- `api_url` (string): https URL of OpenAPI spec
- `contact` (string): mailto:, https: or tel: URI
- `description` (string): one-sentence description of the service or agent capability
- `domain` (string): hostname, e.g. example.com
- `from_live` (boolean): true: probe domain live and pre-populate template URLs/metadata from its discovered endpoints
- `id` (string, required): one of ard, ai-catalog-well-known-file, llms-txt, agents-md, anthropic-agent-skills-format, mcp-server-cards, a2a, ai-crawler-tokens-robots, api-catalog-rfc9727, security-txt, auth-md, okf
- `mcp_url` (string): https URL of MCP endpoint
- `name` (string): service or project display name

### `ask` (~159 tokens)

Recommend and rank standards to implement for an engineering goal (pass question/q and/or use_case + audience filters), or compare named protocols head-to-head when the query names 2+ standards. Returns { use_case, audience, standards (ranked by tier and adoption), starter_bundle, comparisons }. Use ask for architecture and stack decisions; use search for keyword lookup or get for one standard's record.

Input parameters:

- `audience` (string): target audience filter (site-owner, agent-builder, platform, standards-body)
- `q` (string): alias for question: natural-language implementation question
- `question` (string): natural-language implementation question (e.g. How do I accept payments from agents?)
- `use_case` (string): optional explicit use-case id filter

### `digest` (~139 tokens)

Fetch the curated daily agentic-web news and adoption digest for a YYYY-MM-DD date (defaults to latest). Returns { date, headline, highlights, new_instances, spec_changes, stats }; pass list: true to return available dates only, or compact: true (alias: include_stats: false) to omit the census stats block. Use digest for daily narrative summaries; use changes for raw field-level diffs.

Input parameters:

- `compact` (boolean): true: omit stats block
- `date` (string): YYYY-MM-DD or latest
- `include_stats` (boolean): false: omit stats block
- `list` (boolean): true: list published dates

## Diagnostics

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

## Score history

- 2026-11-05: 79
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 77
- 2026-10-31: 77
- 2026-10-30: 76
- 2026-10-29: 76
- 2026-10-28: 75
- 2026-10-27: 75
- 2026-10-26: 74
- 2026-10-25: 74
- 2026-10-24: 71
- 2026-10-23: 70
- 2026-10-22: 70
- 2026-10-21: 69
- 2026-10-20: 69
- 2026-10-19: 68

## Common questions

### What is the Agentic Web Wiki — standards reference, probe, validate… MCP server?

Agentic Web Wiki — standards reference, probe, validate… is an MCP server listed in the public MCP registry as wiki.agenticweb/probe. Look up 133 agentic-web standards, live-probe any domain, validate manifests, generate boilerplate. This page covers its hosted endpoint (https://agenticweb.wiki/mcp).

### Is the Agentic Web Wiki — standards reference, probe, validate… MCP server safe to use?

Agentic Web Wiki — standards reference, probe, validate… scores 79 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 Agentic Web Wiki — standards reference, probe, validate… MCP server expose?

Agentic Web Wiki — standards reference, probe, validate… exposes 11 tools: define, get, search, has, probe, and 6 more. Their descriptions and schemas cost roughly 2,183 tokens of context every time the server is loaded.

### Does the Agentic Web Wiki — standards reference, probe, validate… MCP server require authentication?

No. We connected to Agentic Web Wiki — standards reference, probe, validate… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Agentic Web Wiki — standards reference, probe, validate… MCP server still maintained?

Agentic Web Wiki — standards reference, probe, validate… is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://agenticweb.wiki/mcp
- Repository: https://github.com/Belgravia-Labs/agenticweb-data
- Website: https://agenticweb.wiki/
- Changelog RSS feed: https://verifymcp.io/servers/wiki-agenticweb-probe/agenticweb.xml
- Changelog JSON feed: https://verifymcp.io/servers/wiki-agenticweb-probe/agenticweb.json
- HTML version of this page: https://verifymcp.io/servers/wiki-agenticweb-probe/agenticweb