A2A agent grounded in Joost de Valk's published posts and video transcripts. Answers natural-language questions about SEO, WordPress, the open web, AI, and open source, with a citation for every claim.

MCP server over Joost de Valk's writing on SEO, WordPress, AI, and the open web. ask_joost returns answers grounded in his posts and talks with source URLs; list_recent_content lists published posts filtered by topic and date.

REST API for registering schemas, circuits, and documents; submitting zero-knowledge proofs; and querying verified attributes. Agents use this API to integrate verifiable provenance into their workflows without handling plaintext data.

Verifiable provenance for AI agents — ZK proofs over confidential documents, no plaintext exposure. Register schemas, circuits, and documents; submit and query zero-knowledge proofs; verify attributes without revealing underlying data.

First stop in the Agentic Resource Discovery treasure hunt. Connect and call the tool to begin.

Export an entity's beneficial ownership and control graph as Beneficial Ownership Data Standard (BODS v0.4) statements in JSON, JSON-Lines or a zipped bundle (GET /export?lei=&format=json|jsonl|zip). Each entity statement carries the cross-reference identifiers GLEIF publishes against the LEI (BIC, MIC, ISIN, OpenCorporates, S&P CIQ, QCC) plus national company-register numbers, so the LEI connects to datasets worldwide.

Find a company's Legal Entity Identifier (LEI) from a name or a national company-registration number. Free-text fan-out search across GLEIF and connected registers (GET /search?q=&kind=entity), plus national-ID to LEI reverse resolution via GLEIF registration-authority codes. Use this first to obtain the LEI that drives the due-diligence lookup.

Run customer due diligence on a legal entity from its Legal Entity Identifier (LEI). Resolves the GLEIF record, fans out to 30+ national company registers and open datasets, maps results to the Beneficial Ownership Data Standard (BODS v0.4), and returns an ownership-and-control graph annotated with sanctions, PEP, debarment, offshore-leaks, FATF-jurisdiction and complex-structure risk signals. Primary endpoint: GET /lookup?lei=. Streaming variant for incremental results: GET /lookup-stream. Open data, no API key required.

Model Context Protocol server (streamable HTTP at https://api.opencheck.world/mcp) exposing OpenCheck as agent-native tools: opencheck_search and opencheck_resolve_national_id to obtain an LEI, opencheck_lookup for owners/controllers and sanctions/PEP/debarment risk, opencheck_export_bods for the BODS v0.4 ownership graph, and opencheck_list_sources. The most directly invocable surface for AI agents.

No description was published for this resource.

No description was published for this resource.

Read-only A2A agent that answers natural-language questions about The Website Specification and returns matching topics with status, canonical URL, and a body excerpt.

The entire specification as an Open Knowledge Format bundle: one Markdown concept per check, a mirrored concept per cited standard, plus index and change-log files. Browsable at /okf/ or downloadable as a single gzipped tar. The media type is interim and unregistered pending a blessed OKF media type.

Read-only MCP server exposing every spec page as queryable tools — search, list_topics, get_topic, get_checklist, get_categories — plus an audit_url prompt.

Agent Skill teaching a compatible agent when and how to query The Website Specification — the per-page Markdown over HTTP, llms.txt, and the MCP server. Served as SKILL.md (text/markdown, not a packaged zip) and discoverable via /.well-known/agent-skills/index.json.

MCP server for vreeman.com — search Simon Vreeman's technical-marketing tools (GA4 UTM builder, Measurement Protocol hit builder, CRO tools, experiment hypothesis builder) and Stoic philosophy library (Seneca's letters, Marcus Aurelius' Meditations, Epictetus' Discourses, Stockdale's essays, classic poems).

An Open Knowledge Format v0.1 bundle of this site's Stoic library — concepts, persons, works, and Seneca's letters as cross-linked Markdown — generated from the same data as the EntityMap.

FAFA's A2A v1.0 AgentCard — the discovery card for its live message/send door. Projected from the .fafa (one context, every door).

The canonical FAF agent descriptor for FAFA (the Voice of FAF) — a narrow-domain, cite-or-refuse agent. Declares its MCP, A2A, and HTTP endpoints. Completes the FAF context/memory/agent trinity.

Real-time MCP context delivery at the edge — the hosting layer behind the claude/grok/gemini FAF endpoints. Independently published sub-catalog.

Deterministic, IANA-registered project context — the .faf source of truth a repo's CLAUDE.md / AGENTS.md are generated from.

The .faf for xai-faf-zeph (ZEPH): a pure Zig→WebAssembly microsecond context engine, the xAI collaboration channel. .faf context on a radically different stack — a Zig/WASM engine, not a website.

Live MCP server carrying FAF context in its reverse-DNS _meta["one.faf/context"] slot.

IANA-registered multi-profile agent memory format — permanent context recall across sessions.

A public .fafm authored by Grok (xAI): durable memory of FAF's context layer, the vROM/RAM model, and the ZEPH engine — a frontier-model demonstration of the memory format.

Hugging Face Hub CLI (`hf`) for downloading, uploading, and managing models, datasets, spaces, buckets, repos, papers, jobs, and more on the Hugging Face Hub.

Set up an isolated Python environment for SageMaker / AWS work, with the right Python version and current boto3.

Plan and coordinate the deployment of a model to Amazon SageMaker AI.

Create a SageMaker endpoint (real-time, real-time scale-to-zero, or async) with autoscaling, CloudWatch alarms, and tagging enabled by default.

Pick the right serving container for a SageMaker model deployment and find its current image URI.