ai.ibl/agent-chat
ibl.ai/agent-chat
Is the ibl.ai/agent-chat MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-13.
Add any agent you deploy on ibl.ai to Claude Code, Cursor or Claude Desktop and talk to it there.
needs auth probed 2026-11-15 · unchanged since 2026-11-13 · HTTP 401
Streamable HTTP error: Error POSTing to endpoint: 401 Unauthorized
- Endpoint
- https://asgi.data.iblai.app/mcp/agent-chat/ (streamable-http)
- Host
- asgi.data.iblai.app
- Getting access
- The server answers HTTP 401 with no WWW-Authenticate header and no OAuth metadata, so the publisher's documentation is the only guide.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://ibl.ai
- Registry
- active, updated 2026-11-12 · registry entry
Compare this server with others.
More servers
Servers that mention chat.
- UGC, the Human Ad Network africa.ugc/ugc · needs auth
- 69.ai ai.69ai/69ai · no DNS
- Adako: ad ops for AI assistants ai.adako/ads · needs auth
- adplane ai.adplane/google-ads · needs auth
- AIMentionTracker ai.aimentiontracker/mcp · needs auth
- AppDeploy ai.appdeploy/deploy-app · needs auth
- Amazon Seller MCP Server — AgentXray ai.agentxray/mcp · needs auth
- Askline ai.askline/askline · not found
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.