Agentic Web Wiki — standards reference, probe, validate, template

wiki.agenticwebPublished by agenticweb.wikiOfficial publisherv1.3.0Updated Oct 26, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Public read-only reference on agentic-web standards: look up specs and glossary terms, probe domains, validate manifests, and generate boilerplate.

What you can do
  • Look up and search standards and glossary terms, including head-to-head comparisons and ranked recommendations for an engineering goal
  • Fetch a single standard's full record by id, acronym, RFC number or well-known path
  • Probe a public origin for agent-facing files and check for one specific standard
  • Validate an origin's agent manifests with a letter grade, or validate local file text before deploy
  • Generate starter boilerplate for supported manifest types without writing to disk
  • Review spec change history, verification freshness and a daily news digest
When to use it
Useful when an assistant needs to answer questions about agentic-web protocols, decide which standards to implement, or audit and prepare a domain or repository so agents can discover and use it.
Requirements
Remote Streamable HTTP endpoint; no authentication, API keys or environment variables are required. Probing and validation tools need network access to the target public origin over HTTPS.
Before you install
All tools are described as read-only and deterministic, and templates are generated in memory only. Probe, has and validate_manifest send requests to whatever public origin you name, so only point them at domains you are authorized to scan; live re-probes are rate-limited and cached.

Installation

In SourceWeft

  1. Open Agentic Web Wiki — standards reference, probe, validate, template in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/wiki.agenticweb%2Fprobe/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "agentic-web-wiki-standards-reference-pro": {
      "type": "http",
      "url": "https://agenticweb.wiki/mcp"
    }
  }
}

README

agenticweb-data (wiki.agenticweb/probe)

Canonical Open Dataset, JSON Schemas, Bi-Temporal Change Log, Executable Probe Rules & Stateless MCP Server (https://agenticweb.wiki/mcp) for agenticweb.wiki

[Live Site] [Live MCP Endpoint] [License: MIT] [Data License: CC BY 4.0]

Maintained by Belgravia Labs LLC ([email protected]), agenticweb-data is the verified, schema-enforced ground-truth repository powering agenticweb.wiki and its public Model Context Protocol (MCP) server wiki.agenticweb/probe at https://agenticweb.wiki/mcp.

Every merged commit on main is validated in CI against strict JSON Schemas and automatically ingested to rebuild the public registry (132 standards, 51 glossary terms, 151 head-to-head comparisons, 1,137+ probed origins) and the 11-tool stateless Streamable HTTP MCP server.


Connect to the MCP Server (https://agenticweb.wiki/mcp)

Quick Configuration (claude_desktop_config.json / .mcp.json / Cursor)

json
{  "mcpServers": {    "agenticweb": {      "type": "http",      "url": "https://agenticweb.wiki/mcp"    }  }}
bash
claude mcp add --transport http agenticweb https://agenticweb.wiki/mcp

Tools (tools/list & tools/call — 11 Tools)

All 11 tools are deterministic, read-only (readOnlyHint: true, destructiveHint: false, idempotentHint: true), and execute at the Cloudflare edge in <15 ms.

ToolParametersDescription
defineterm: stringDefine an agentic-web glossary term (51 terms) or standard (132 protocols) by id, name, or alias. Returns definition_md, related_protocols, and standard_summary_md.
getid: stringFetch one standard's complete record by id ("mcp"), acronym ("A2A"), RFC ("RFC 9421"), or well-known path ("llms.txt", "/.well-known/ard.json"): status, governance, version, spec URL, probe rule, evidence, disputes, and freshness.
searchq?: string, query?: stringSearch all 132 standards and 51 glossary terms by name, acronym, alias, question, or use case ("A2A vs MCP", "mcp.auth"). Returns top 10 matches plus nearest_ids and nearest_terms on misses.
askquestion?: string, q?: string, use_case?: string, audience?: stringRecommend and rank standards to implement for an engineering goal ("let agents pay per request"), or compare named protocols head-to-head with /compare/<slug>/ links.
hasorigin: string, id: stringLive-check a public origin for one standard ("llms-txt", "ard", "mcp-server-cards"). Returns found, url, status, reason, and article.
probeorigin: string, brief?: boolean, compact?: booleanLive-scan a public origin across 35 agent-facing standards in parallel (24h KV cached). Pass brief: true for found_ids + extracted resources only, or compact: true to return absent_ids[] instead of full absent/skipped maps (~85% smaller).
validate_manifestorigin?: string, id?: string, content?: string, verify?: boolean, bridge?: boolean, brief?: boolean, compact?: booleanValidate an origin's 12 agent manifests (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-md, okf) live or validate local content pre-commit, grade readiness (A+ to F), and return agent_routing + connect_recipe.
templateid: string, domain?: string, from_live?: boolean, name?: string, description?: string, mcp_url?: string, api_url?: string, agent_url?: string, contact?: stringGenerate spec-compliant starter boilerplate (contents, target_path, content_type, recommended_headers) for any of the 10 publishable agent manifests (or pass from_live: true to pre-populate from the origin's live files).
changessince: string, step?: string, record_id?: string, limit?: numberQuery machine-verified changelog diffs (old -> new, summary, evidence URL, date) since YYYY-MM-DD.
staledays?: number, step?: stringList standards whose last_verified date is older than days (default 30), optionally filtered by lifecycle step.
digestdate?: string, list?: boolean, compact?: boolean, include_stats?: booleanFetch the daily Agentic Web Digest (date: "latest" or "YYYY-MM-DD"), list all published dates (list: true), or pass compact: true / include_stats: false to omit the stats block.

Example JSON-RPC 2.0 Calls

bash
# 1. Define a term or protocolcurl -sS -X POST https://agenticweb.wiki/mcp \  -H "Content-Type: application/json" -H "Accept: application/json" \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"define","arguments":{"term":"MCP"}}}'
# 2. Validate a domain in compact modecurl -sS -X POST https://agenticweb.wiki/mcp \  -H "Content-Type: application/json" -H "Accept: application/json" \  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"validate_manifest","arguments":{"origin":"cloudflare.com","compact":true}}}'

MCP Resources (resources/list & resources/read — 6 Resources)

  • agenticweb://standards/all — All 132 protocol records + the 9-step facet vocabulary (https://agenticweb.wiki/data/standards.json).
  • agenticweb://glossary/all — All 51 glossary terms with definitions, aliases, and sources (https://agenticweb.wiki/data/terms.json).
  • agenticweb://use-cases/all — All 15 engineering use cases mapped to the standards that serve them.
  • agenticweb://probes/all — All 132 probe rules and skip reasons (https://agenticweb.wiki/data/probes.json).
  • agenticweb://versions/all — Spec versions, canonical paths, deprecated paths, and legacy shapes (https://agenticweb.wiki/data/versions.json).
  • agenticweb://census/summary — Empirical adoption census summary across 1,137+ probed origins and 906 panel domains.

MCP Prompts (prompts/list & prompts/get — 3 Workflows)

  • audit-domain ({ domain }) — Audit a domain's manifests, explain spec violations, and recommend the 3 highest-impact missing files.
  • make-repo-agent-ready ({ domain, project_type? }) — Generate all agent-facing files for a repository using template().
  • compare-protocols ({ first, second }) — Compare two standards side-by-side across all 12 schema dimensions.

Repository Contents

File / DirectoryDescriptionSchema
protocols.jsonCanonical records for 132 agentic-web standards, specifications, IETF drafts, and conventions across 9 lifecycle steps (discover, identify, permit, read, act, coordinate, pay, present, account).schema/protocols.schema.json
terms.json51 technical glossary terms with multi-paragraph definitions, aliases, related protocol IDs, and verified sources.schema/terms.schema.json
probes.jsonExecutable HTTP probe rules (35 active GET/HEAD rules + skip reasons) used by /check/<domain>/, probe, has, and validate_manifest.schema/probes.schema.json
changes.jsonBi-temporal change ledger recording specification version bumps, draft renewals, and status transitions.schema/changes.schema.json
instances.jsonVerified live production deployments implementing agentic-web protocols in the wild.schema/instances.schema.json
census.json & ecosystem-census.jsonEmpirical origin-probe adoption census across 1,137+ probed domains and 906 readiness panel domains.—
digests/ & stats/Daily cited Agentic Web Digest issues and panel adoption telemetry snapshots.schema/digest.schema.json
server.jsonOfficial MCP Registry descriptor (wiki.agenticweb/probe, v1.20261025.0).—

Security & License

Source: README.md at commit b12ff25

Tools

11

define

Define a term

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.

Parameterstermrequired

get

Get a standard

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.

Parametersidrequired

has

Check an origin for one standard

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.

Parametersidrequiredoriginrequired

probe

Probe an origin

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.

Parametersidbrieffreshoriginrequiredverifycompact

changes

What changed since a date

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.

Parameterssteplimitsincerequiredrecord_id

stale

Stale records

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.

Parametersdaysstep

validate_manifest

Validate an origin's manifests and grade it

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.

Parametersiddiffbrieffreshbridgeoriginverifycompactcontentcontent_type

template

Boilerplate for an agent-facing file

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.

Parametersidrequirednamedomainapi_urlcontactmcp_urlagent_urlfrom_livedescription

ask

What should I implement?

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.

Parametersqaudiencequestionuse_case

digest

Agentic web daily digest

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.

Parametersdatelistcompactinclude_stats

Version history

4
  1. v1.3.0LatestOct 26, 2026
  2. v1.2.3Oct 23, 2026
  3. v1.2.2Oct 23, 2026
  4. v1.2.0Oct 18, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts