accueil / serveurs / Recherche & Web / wiki.agenticweb/probe
wiki.agenticweb/probe
serveur MCP (Model Context Protocol) · agenticweb.wiki 1
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que wiki.agenticweb/probe est sûr ?
Au dernier audit MCP Hub, le serveur MCP « wiki.agenticweb/probe » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 11 outils
- ask≈ 344 tokens
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, and related ones to consider (also_consider carries id, name, step and question).
Paramètres, retour & exemple (3)
Paramètresaudience· string · optionnel · site-owner | agent-builder | platform | standards-bodyquestion· string · requisuse_case· string · optionnel · discover-my-api | expose-tools-to-agents | let-agents-act-on-my-site | serve-content-to-agents | prove-agent-identity | delegate-user-authority | control-ai-crawling | accept-agent-payments
Exemple d'appel{"name": "ask", "arguments": {"question": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - changes≈ 222 tokens
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.
Paramètres, retour & exemple (4)
Paramètresstep· string · optionnellimit· integer · optionnelsince· string · requis
YYYY-MM-DD, or an ISO-8601 timestamp (its offset is applied, then the UTC date is used)record_id· string · optionnel
Exemple d'appel{"name": "changes", "arguments": {"since": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - define≈ 162 tokens
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.
Paramètres, retour & exemple (1)
Paramètresterm· string · requis
Exemple d'appel{"name": "define", "arguments": {"term": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - digest≈ 268 tokens
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, fastest-growing repositories, MCP Registry activity) and how it was made. Every number in an item appears in a source it cites. Human version: https://agenticweb.wiki/digest/.
Paramètres, retour & exemple (2)
Paramètresdate· string · optionnel
YYYY-MM-DD or latest (default)list· boolean · optionnel
true: the index of published dates instead of one digest
Exemple d'appel{"name": "digest", "arguments": {"date": "texte", "list": true}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get≈ 160 tokens
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.
Paramètres, retour & exemple (1)
Paramètresid· string · requis
Exemple d'appel{"name": "get", "arguments": {"id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - has≈ 178 tokens
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.
Paramètres, retour & exemple (2)
Paramètresid· string · requisorigin· string · requis
Exemple d'appel{"name": "has", "arguments": {"id": "texte", "origin": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - probe≈ 164 tokens
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.
Paramètres, retour & exemple (1)
Paramètresorigin· string · requis
Exemple d'appel{"name": "probe", "arguments": {"origin": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - search≈ 164 tokens
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.
Paramètres, retour & exemple (1)
Paramètresq· string · requis
Exemple d'appel{"name": "search", "arguments": {"q": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - stale≈ 170 tokens
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.
Paramètres, retour & exemple (2)
Paramètresdays· integer · optionnelstep· string · optionnel
Exemple d'appel{"name": "stale", "arguments": {"days": 1, "step": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - template≈ 439 tokens
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, contents, the fields to edit, notes on the specification, and the validate_manifest call to run once it is live.
Paramètres, retour & exemple (8)
Paramètresid· string · requis
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-mdname· string · optionneldomain· string · optionnel
bare hostname the file is for, e.g. example.com (default example.com)api_url· string · optionnel
absolute https URL of the OpenAPI descriptioncontact· string · optionnel
mailto:, https: or tel: URI (a bare email gets mailto:)mcp_url· string · optionnel
absolute https URL of the MCP endpointagent_url· string · optionnel
absolute https URL of the A2A endpointdescription· string · optionnel
Exemple d'appel{"name": "template", "arguments": {"id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - validate_manifest≈ 298 tokens
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 warnings (best practice), steps covered, what an agent can call, and the cheapest next steps. The same report is a page at /check/<domain>/ with a badge at /badge/<domain>.svg.
Paramètres, retour & exemple (2)
Paramètresid· string · optionnel · ard | ai-catalog-well-known-file | mcp-server-cards | a2a | llms-txt | agents-md | api-catalog-rfc9727 | ai-crawler-tokens-robotsorigin· string · requis
Exemple d'appel{"name": "validate_manifest", "arguments": {"origin": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».