anots-inter
Registry code: b22e0abee9937856
Discover and query every business on ANOTS — search, ask, or find-and-ask over MCP.
from a public catalogue that lists it, not from the operator
- endpoint
- https://api.anots.com/mcp
- door code
- 5a317241d4cf99b0
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is anots-inter live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is anots-inter free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does anots-inter have?
- 3 tools: find_and_ask, search_businesses, ask_business.
- Is anots-inter safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.5%· all time 99.7%
last good check
of 3 tools
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- search businesses whose agents can answer a need
- ask a business's agent a question
- find and ask several businesses at once
- takes → gives
- text → text, data
- tools
- 3 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
find_and_ask reads unknown 13h ago
Discover the most relevant ANOTS businesses for a need AND ask each one in a single step, returning their answers side by side. The fastest way to answer a purchase-intent or research question across the directory.
{ "type": "object", "required": [ "query" ], "properties": { "limit": { "type": "number", "description": "How many businesses to ask (default 3, max 5)" }, "query": { "type": "string", "description": "The need or question to route across the directory" } } }arguments 16 linessearch_businesses reads unknown 13h ago
Search the ANOTS directory for businesses whose AI agent can answer a question or need. Returns matching businesses with their slug, name, what they do, and agent-card URL. Use this first to discover which agents to ask.
{ "type": "object", "required": [ "query" ], "properties": { "limit": { "type": "number", "description": "Max businesses to return (default 5, max 10)" }, "query": { "type": "string", "description": "What you are looking for (e.g. \"honest product reviews\", \"coffee subscription that ships internationally\")" } } }arguments 16 linesask_business reads unknown never probed
Ask a specific business's ANOTS agent a question, by slug. The agent answers from that business's own knowledge base and tools (live data, not scraped HTML). Get the slug from search_businesses.
{ "type": "object", "required": [ "slug", "question" ], "properties": { "slug": { "type": "string", "description": "The business slug (e.g. \"gyibb\")" }, "question": { "type": "string", "description": "The question to ask that business agent" } } }arguments 17 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idb22e0abee9937856.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/b22e0abee9937856/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/b22e0abee9937856?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 1
- ok
- 1
- failed
- 0
- success rate
- 100%
- median latency
- 137ms
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
1 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.