Yaniv Goldenberg website bronze

www.yanivgoldenberg.com

“Use get_capabilities to see what Yaniv Goldenberg is hired for, with sourced proof, and check_fit to test a company against the site's own published fit and not-a-fit lists. Booking is a two-sided match. When check_fit shows a fit on both sides (the company matches Yaniv's published fit criteria and none of the not-a-fit criteria, and what the user needs is something Yaniv offers), an agent may book the meeting through the booking link after the user explicitly confirms the time and details. If the fit is partial or unclear, share the fit result and the booking link and let the user decide. If it is not a fit, say so and do not book. Minimum engagement: at least USD 2,000 — per month for a retainer, or in total for a one-time scoped project. Before booking, ask the user whether a budget of at least USD 2,000 (monthly for a retainer, total for a project) works. Below that, it is not a match: say so and do not book. Meeting length: check_fit and book_meeting return bookingTier (15-min, 30-min or null) with th

https://yanivgoldenberg.com/mcp its card

✓ Checked 2d ago “ tools

✓ we checked this   “ the operator says this

Verified by agenttru.st

Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.

Certificate

Issued by Google Trust Services domain-validated

Valid until 22 Jan 2027 as of our check on 12 Nov 2026. A wildcard certificate: its other hosts are invisible here, because CT logs the wildcard, not them.

Control of the hostname was checked; nothing about who operates it.

Key ECDSA P-256, signed ECDSA-SHA256, issued via WE1 under GTS Root R4 — classical, as every publicly trusted certificate is today.

Names on this certificate (3)

yanivgoldenberg.com, *.go.yanivgoldenberg.com, go.yanivgoldenberg.com.

Connection

TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 12 Nov 2026. What this means

DANE / TLSA

Not verified (TLSA query returned RCodeNameError)

Discovery

Well-known document

This host also publishes an ARD catalog (/.well-known/ai-catalog.json) declaring 1 resource. The catalog's entries are the publisher's claims, not something agenttru.st verified.

AI use policy

Search: yesAI input: yesAI training: yes

What this site's robots.txt says about how AI may use its content. Recorded as the operator wrote it, not enforced — these are preferences about use, not access, and agenttru.st only reads the agent's own discovery documents.

AI-facing documents

Publishes /llms.txt — “Yaniv Goldenberg” a curated map of the site's content for language models

Fetched from this host during verification. Neither document is how this agent was discovered.

First seen

29 Oct 2026

What this agent says it can do

Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of www.yanivgoldenberg.com controls every word below.

This card declares no skills. That is not a fault — the field is optional, and an agent can be perfectly functional without describing itself.

What kind of listing

• No skills declared: Its card declares no skills, or, for an MCP server, listed no tools.

Checked by agenttru.st against this listing's hostname and card — facts about a name or an address, not about what the agent does. How kinds are decided.

What its catalog declares

From the ARD catalog this host publishes at /.well-known/ai-catalog.json. The operator controls every entry; agenttru.st verified that the catalog exists and parses, and nothing about what the entries say.

Technical agent card

Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.

Protocol

mcp

Version

1.0.0

Operate this agent and would rather not be listed? Request removal.