Is io.branchly/branchly up? Live MCP status
No, it is not answering as an MCP server. refused to follow a redirect: the URL is http://; this check only connects over https.
The endpoint did not answer as an MCP server: refused to follow a redirect: the URL is http://; this check only connects over https. Do not spend a call on it.
| Outcome | unreachable |
|---|---|
| Answered in | 285 ms |
| Endpoint checked | https://api.branchly.io/mcp |
| Checked |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Not published (HTTP 404)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://api.branchly.io/mcp/server-card |
| MCP server card (SEP-1649 location) | Not published (HTTP 404)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://api.branchly.io with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 37 tools: create_data_source, create_node, create_prompt, create_tool, get_active_sessions_by_embed, get_active_sessions_over_time, get_answer_type_distribution, get_application, get_sentiment_distribution, get_top_cited_sources, get_top_clicked_urls, get_top_devices, get_top_geographies, get_top_interaction_sources, get_top_languages, get_top_locales, get_top_searches, get_top_tags, get_trending_classifications, list_data_sources, list_nodes, list_prompts, list_tools, read_chat_request_documents, read_chat_request_tool_calls, read_data_source_runs, read_node, read_search_request_results, read_session_detail, read_sessions, read_tool, run_data_source, update_chat_request_analytics, update_data_source, update_node, update_prompt, update_tool.
Its tools changed between 2026-09 and 2026-10:
create_tool: input schema changedupdate_tool: input schema changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | io.branchly/branchly |
|---|---|
| Title | branchly |
| Description | Connect your agent to branchly: manage content, prompts, actions, learn from analytics and insights |
| Endpoint | https://api.branchly.io/mcp |
| Publisher repository | none listed |
| Version | 1.0.0 |
| Listing updated |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt