MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Agentic Web Wiki — standards reference, probe, validate is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Look up 100+ agentic-web standards, live-probe any domain, validate manifests, generate boilerplate.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http agentic-web-wiki-standards-reference-probe-va-mcp https://agenticweb.wiki/mcp
# 2 — ask your agent for something these tools do
# define, get, search and 8 more
Agentic Web Wiki — standards reference, probe, validate costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http agentic-web-wiki-standards-reference-probe-va-mcp https://agenticweb.wiki/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Define a glossary term of the agentic web. Input: term (id, name or alias; plurals tolerated). Returns the definition and related protocol ids. If the word is the name of a standard rather than a term (x402, ARD, AGENTS.md) it returns that standard's summary instead of an error.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| term | string | yes | — |
Get one standard's full record by id: status, governance, version, spec URL, discovery, probe rule, evidence with URLs, disputes, summary, freshness. The id may be written as the file or path it is known by (llms.txt, /.well-known/ard.json, A2A); a miss names the nearest ids.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | — |
Search the standards by name, acronym, alias, question or use case. Input: q (plain words are fine: 'A2A vs MCP', 'pay per request'). Returns up to 10 matches with id, step and status; a word that is a standard's id or acronym ranks first, and acronym clashes such as ACP are all returned.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | yes | — |
Check one public origin for one standard by fetching its well-known path live. Input: origin (hostname), id (standard id). Returns found/absent with the URL, status and reason; an apex that redirects to its www. host is followed and reported as final_origin.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | string | yes | — |
| id | string | yes | — |
Check one public origin for every standard that can be observed without credentials (about 30 GET rules). Input: origin. Returns found, absent and skipped (with reasons) plus coverage by lifecycle step. An apex that redirects to its www. host is followed and reported as final_origin.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | string | yes | — |
What changed on the map since a date. Input: since (YYYY-MM-DD; an ISO-8601 timestamp is cut to its date), optional step, record_id, limit. Returns dated rows with record, kind, field, old and new value, claim, evidence URL and the data commit.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | string | yes | YYYY-MM-DD, or an ISO-8601 timestamp (its offset is applied, then the UTC date is used) |
| step | string | no | — |
| record_id | string | no | — |
| limit | integer | no | — |
Records whose last verification is older than N days (default 30), optionally within one lifecycle step. Returns the matching records (id, name, step, last_verified, freshness) and, always, total_standards, cutoff, oldest_verified and newest_verified so an empty list is still informative.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | — |
| step | string | no | — |
Validate a public origin's agent-facing manifests against their specifications and grade its agentic-web readiness. Input: origin; optional id to check one manifest only (ard, ai-catalog-well-known-file, mcp-server-cards, a2a, llms-txt, agents-md, api-catalog-rfc9727, ai-crawler-tokens-robots, security-txt, auth-md). Returns grade A+ to F with the rubric, per-manifest errors (spec violations) and
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | string | yes | — |
| id | string | no | — |
Spec-compliant boilerplate for an agent-facing file, filled with your domain: ard (and ai-catalog-well-known-file), llms-txt, agents-md, mcp-server-cards (SEP-2127), a2a (agent card 1.0), ai-crawler-tokens-robots, api-catalog-rfc9727, security-txt, auth-md. Input: id; optional domain, name, description, mcp_url, api_url, agent_url, contact. Returns target_path, content_type, recommended_headers, c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | one of ard, ai-catalog-well-known-file, llms-txt, agents-md, mcp-server-cards, a2a, ai-crawler-tokens-robots, api-catalog-rfc9727, security-txt, auth-md |
| domain | string | no | bare hostname the file is for, e.g. example.com (default example.com) |
| name | string | no | — |
| description | string | no | — |
| mcp_url | string | no | absolute https URL of the MCP endpoint |
| api_url | string | no | absolute https URL of the OpenAPI description |
| agent_url | string | no | absolute https URL of the A2A endpoint |
| contact | string | no | mailto:, https: or tel: URI (a bare email gets mailto:) |
Ask what to implement for a goal in plain words, e.g. 'let agents pay per request', 'stop AI training crawls', 'let ChatGPT call my API'. Input: question; optional use_case (one of the 15 use-case ids in the schema) and audience. Returns the matched use case(s), up to 8 standards ranked by fit, maturity and adoption with reasons, do_this_first (prerequisites first), deprecated standards to avoid,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | — |
| use_case | string | no | — |
| audience | string | no | — |
The agentic-web daily digest as structured data. Input: date (YYYY-MM-DD, default latest), or list: true for the index of every published date. Returns headline, lede, items (title, body, why_it_matters, kind, related standards, and the sources each item rests on, labelled VERIFIED or REPORTED), the day's measured stats (adoption and grade changes across a fixed panel of domains re-checked daily,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | YYYY-MM-DD or latest (default) |
| list | boolean | no | true: the index of published dates instead of one digest |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Agentic Web Wiki — standards reference, probe, validate or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| define | no tags | |
| get | no tags | |
| search | no tags | |
| has | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| probe | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| changes | no tags | |
| stale | no tags | |
| validate_manifest | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| template | no tags | |
| ask | no tags | |
| digest | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.2.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Agentic Web Wiki — standards reference, probe, validate can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.