add tiza to the agent finders

[miguelaeh]

We have been working for some time on finding and curating MCP tools and A2A agents, live-proving them and making them searchable by agents.
When we heard about the ARD protocol, we decided to implement it, so this PR adds the tiza catalog to the seed agent finders.

(more info in comment #2 (comment))

[rvguha]

Thank you for the contribution. Since Tiza is not as well known as Hugging Face or GitHub, can you add to your description with more about Tiza?

[miguelaeh]

Hi @rvguha sure.

At Tiza the goal is to provide consumer agents with a place they can trust to search tools.

A bit on how tiza works internally:

• We crawl the web daily looking for MCP servers and A2A agents.
• We return hosted results only - we don't return anything that would make a client agent run untrusted code locally. (Skills are on the roadmap but gated, since we consider them riskier.)
• Results are live-probed before indexing - every MCP server gets a real connection, handshake, and tools/list call, so an indexed result is a verified-working result, not just a scraped link.

How we implemented ARD:

We participate in ARD in both spec roles:

1. As a host, we publish a capability manifest at /.well-known/ai-catalog.json with an https trustManifest identity anchored to tiza.cc, advertising three entries: the registry (application/ai-registry+json), our A2A agent, and our MCP server. Identifiers are domain-anchored URNs (urn:air:tiza.cc:…).
2. As a registry, we expose the mandatory POST /search interface at https://tiza.cc/api/ard/v1/search. It's a thin, conformant adapter over our native search engine:
   - Accepts ARD query.text + query.filter (by IANA media type and tags), federation, and opaque pageToken/pageSize cursor pagination.
   - Returns results following §3.4 value-or-reference: each result carries exactly one of url (a dereferenceable card) or data (the artifact inline).
   - Artifacts are served verbatim from the authentic upstream document (the original server.json / agent card). We strip the local packages path too (to avoid consumer agents running untrusted code), so only hosted remotes remain.

You can verify both endpoints directly:

• Host manifest

curl https://tiza.cc/.well-known/ai-catalog.json

• Registry search

curl -X POST https://tiza.cc/api/ard/v1/search \
   -H 'Content-Type: application/json' \
   -d '{"query":{"text":"github issues","filter":{"type":["application/mcp-server-card+json"]}},"pageSize":3}'

Let me know if this is the kind of information you are looking for or if you would like to know more about something specific.