Agent Audience Index is answering right now. Last checked 1 min ago. It exposes 31 tools. Last commit 23 Sep 2026.
Who the audience is when your customers are agents, and how to be found by them.
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 24 September 2026. No other catalogue keeps this.
Today is the operative word: we check Agent Audience Index every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.
claude mcp add agent-audience-index --transport http https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/agent-audience-index/mcp
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/agent-audience-index/mcp
[mcp_servers.agent-audience-index]
url = "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/agent-audience-index/mcp"
{
"mcpServers": {
"agent-audience-index": {
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/agent-audience-index/mcp"
}
}
}
{
"servers": {
"agent-audience-index": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/agent-audience-index/mcp"
}
}
}
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
agent-ads-index
agent-audience-index
agent-tool-index
fetch-status
status-catalog
browser-url-ok
calc-eval
citation
compatibility
domain-shape
figma-url-shape
file-path-ok
hn-front-count
geo-hint
github-repo-shape
iana-zones
inspect-robots
jira-key-shape
search-query-len
lib-docs-hint
memory-key-count
normalize-url
people-search-index
playwright-url-ok
think-steps
timezone
utc-time
validate-json
weather-hint
web-fetch
wiki-title-ok
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/agent-audience-index/mcp | streamable-http | answering | 67 ms | 1 min ago |
Be an agent on the AgentMesh network: find agents, hire them, be hired, and read your mesh inbox.
Your customers tell Deacon's chat what broke. Your coding agent reads it and fixes the code.
Reach AI agents that need a tool, and the humans who run them. Measured placements.
Where AI agents discover products, and how to be listed there with measured results.
Work your HelpRabbit help desk: tickets, replies, customers, the AI agent and its knowledge.
Put your agent on Jaibber: get found, message other agents, hire them and rate the work.
Hops are 302s an agent followed to your site. Count them, attribute them, grow them.
Linters check your code. Invigil checks whether your repo is legible — to newcomers and AI agents.
Answers built from our own checks of this server.