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.
Available components
Last scanned (23 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Developer Tools
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 Security71
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 27 Oct 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.
- 26 Oct 26 0
- 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 security
- Schema quality: 111 → 148 ▼ functional
- Schema quality: good → excellent functional
- 25 Oct 26 +3
- 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 security
- Schema quality: 75 → 93 ▼ functional
- Schema quality: pass → fail ▼ functional
- Tool coverage: 43% → 100% ▲ functional
- 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 functional
- “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 cosmetic
- 24 Oct 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.
- 23 Oct 26 0
- DNSSEC: fail → pass ▲ 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 security
- Tool “validate_manifest” rewrote its description, which is the text the model reads security
- Tool coverage: 33% → 43% ▲ functional
- Tool coverage: 33% → 39% ▲ functional
- Schema quality: fail → pass ▲ functional
- Schema quality: good → fair functional
- “probe” added an optional parameter “brief” cosmetic
- “validate_manifest” added an optional parameter “brief” cosmetic
- “ask” added an optional parameter “q” cosmetic
- “digest” added an optional parameter “compact” cosmetic
- “digest” added an optional parameter “include_stats” cosmetic
- “probe” added an optional parameter “compact” cosmetic
- “search” added an optional parameter “query” cosmetic
- “validate_manifest” added an optional parameter “compact” cosmetic
- “changes” reworded the description of “since” cosmetic
- “digest” reworded the description of “date” cosmetic
- “digest” reworded the description of “list” cosmetic
- “template” reworded the description of “agent_url” cosmetic
- “template” reworded the description of “api_url” cosmetic
- “template” reworded the description of “contact” cosmetic
- “template” reworded the description of “domain” cosmetic
- “template” reworded the description of “mcp_url” cosmetic
- “template” reworded the description of “id” cosmetic
- “ask” made “question” optional cosmetic
- “search” made “q” optional cosmetic
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 4 Nov 2026 · Probed https://agenticweb.wiki/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agenticweb.wiki | CN=WE1,O=Google Trust Services,C=US | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 10c41b0ed4396b4113a2c9a7aca06c06 |
| SANs: agenticweb.wiki, www.agenticweb.wiki, *.www.agenticweb.wiki | ||||||
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of agenticweb.wiki. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| wiki. | present | 46628 | 13 | Verified |
| agenticweb.wiki. | present | 2371 | 13 | Verified |
| agenticweb.wiki. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' https://static.cloudflareinsights.com; style-src 'self' https://fonts.googleapis.com; font-src https://fonts.gstatic.com; img-src 'self' data:; connect-src 'self' https://api.web3forms.com https://cloudflareinsights.com https://*.cloudflareinsights.com; form-action 'self' https://api.web3forms.com; frame-ancestors 'none'; base-uri 'none'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), camera=(), microphone=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agenticweb.wiki/mcp | Verified | 200 | |
| http (plaintext) | http://agenticweb.wiki/mcp | Inconclusive | 405 |
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 →
ask ~159
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
changes ~189
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | YYYY-MM-DD or ISO-8601 timestamp |
| step | string | – | optional lifecycle step filter (discover, identify, permit, read, act, coordinate, pay, present, account) |
No output schema declared.
No examples provided.
define ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| term | string | yes | glossary term id, name, or alias (e.g. agentic-web, agent card, MCP, x402) |
No output schema declared.
No examples provided.
digest ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
get ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | standard id, acronym, filename, or RFC number (e.g. mcp, ard, llms.txt, RFC 9421) |
No output schema declared.
No examples provided.
has ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | probed standard id or filename (e.g. ard, llms-txt, mcp-server-cards, robots.txt) |
| origin | string | yes | public hostname to check (e.g. agenticweb.wiki, cloudflare.com) |
No output schema declared.
No examples provided.
probe ~284
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 |
No output schema declared.
No examples provided.
search ~130
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.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | – | search query or comparison (e.g. agent discovery, A2A vs MCP, accept payments) |
| query | string | – | alias for q: search query or comparison |
No output schema declared.
No examples provided.
stale ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
template ~349
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 |
No output schema declared.
No examples provided.
validate_manifest ~449
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
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.
remote · agenticweb.wiki
claude mcp add --transport http wiki-agenticweb-probe 'https://agenticweb.wiki/mcp'
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 78 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.