hopenet town bronze
town.impact-agent.io
“The hopenet town's own agent: which estates live on chain 34349, which services they share, and whether each is up. It lists; it never grants — whether you may use a service is your own delegation's question.
https://town.impact-agent.io/.well-known/agent-card.json its cardwe 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 13 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)
impact-agent.io,town.impact-agent.io,*.town.impact-agent.io. - 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
- First seen
- 15 Oct 2026
View verification details
- Assurance
- bronze Bronze — agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
-
? Unknown
·
Cloudflare, Inc.
(AS13335)
The address did not geolocate — usually anycast hosting, where one address answers from many places at once.
- Last checked
- 2d ago
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 town.impact-agent.io controls every word below.
Describe the town
The chain, the estates and every listed service, each with its signals: listed · healthy · compatible.
- what is in this town?
- which services are up?
One service
One listed service by id — what it is, who deploys it, where it lives, and its signals.
- registry
- skills
- kms
One estate
One estate of this town by id — where it lives, the name roots it may give and the gate that authorizes them, whose keys hold it, the MCP servers it declares, and which agents answer at its hosts. Membership is INFERRED from each agent's own on-chain endpoint and every row says so; no attestation of membership exists yet. Args: a data part { "skill": "town.estate", "id": "<estate id>" }, or name the estate in the text.
- tell me about the faithnet estate
- which agents are in impact-agent?
The MCP servers
Which MCP servers this town runs, which each estate runs, and which agents serve a door of their own. The first two are DECLARED in the town manifest; the third is read from the chain. What an agent has ATTACHED is absent by construction: those are records in its owner's vault under her own grant. No tool lists — those belong to each server's own signed manifest. An endpoint says where a server listens, never that you may use it.
- which mcp servers are here?
- what mcp does faithnet run?
agenttru.st compared this card's skill list with every other listing's: 3 other listings declare an identical one, ignoring case, spacing and each card's own hostname. See all 4. That says the cards' text is the same, not who runs them.
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- The hopenet town — what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 0.1.0
- Card completeness
- complete all eight fields required by a2a.proto v1.0
View all card details
- Capabilities
- pushNotifications streaming
- Agent card
- https://town.impact-agent.io/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.