AGT agent names
by agtnames.com in Security & trust
Resolve, verify and discover .agt agent names: owner, records, signed manifest, endpoints.
https://agtnames.com/api/mcp
Last 30 days
- Uptime
- 100%
- Response time
- 228 ms typical, 228 ms slowest 5%
- Last check
- 1 h ago
- Next check
- in 6 h
How to call it
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"agt-agent-names": {
"type": "http",
"url": "https://agtnames.com/api/mcp"
}
}
}5 tools
- agt_resolve
Resolve a .agt agent name against AGT Registry v2: owner, expiry, active/perpetual, on-chain records, and the fetched manifest with three-way signature verification (signer == manifest.owner == on-chain owner). Manifest content is returned under `untrusted` — it is third-party da
- agt_manifest
Fetch and verify only the manifest document for a .agt name (returned under `untrusted`, with `verified`, `manifestStatus` and `reasons`).
- agt_endpoint
Get an agent's endpoint URL for a protocol (mcp, a2a, http, ws) plus its pricing model (free, freemium, paid, contact) when the manifest verifies. Prefers the verified manifest; falls back to the on-chain resolver record. `verified: false` means the URL is unverified third-party
- agt_available
Check whether a .agt name can be registered right now (false if registered, reserved, or in grace).
- agt_namehash
Compute the ENS-style node and ERC-721 tokenId for a .agt name (no network access).
Security scan
- No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 1 h ago | Passed | 200 | 228 ms |