mcp-registry/news.asha/asha-news · v1.0.0
As of 2026-10-27 07:56 UTC, the Asha News MCP server is up with a Glimind reliability score of 75/100 (grade B). Over the last 30 days it answered 99.2% of Glimind's liveness checks. It had 28 outages in 90 days, with a median recovery of 7 minutes.
Evidence-first news archive: briefs, breaking news, search, Palestine claims, conflict monitor.
Point your MCP client at this streamable-http endpoint: https://asha.news/api/v1/mcp
25 of 25 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
12 parameter(s) across 8 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 8 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fnews.asha%2Fasha-news/fixes
{
"name": "asha_clusters_search",
"description": "Search story clusters by topic. Returns grouped multi-source coverage.",
"inputSchema": {
"type": "object",
"required": [
"q"
],
"properties": {
"q": {
"type": "string"
},
"limit": {
"type": "integer",
"maximum": 50,
"minimum": 1
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "asha_search",
"description": "Unified search across Asha News articles, active story clusters, and published generated briefs. Use this before choosing a narrower endpoint.",
"inputSchema": {
"type": "object",
"required": [
"q"
],
"properties": {
"q": {
"type": "string",
"description": "Search term, e.g. \"palestine\", \"gold\", \"OpenAI\"."
},
"limit": {
"type": "integer",
"maximum": 25,
"minimum": 1,
"description": "Max mixed results (default 10)."
},
"types": {
"type": "string",
"description": "Comma-separated result families: articles, stories, generated, or all."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "asha_search_articles",
"description": "Keyword search across recent Asha News articles. Cite source URLs and Asha article/story URLs when present.",
"inputSchema": {
"type": "object",
"required": [
"q"
],
"properties": {
"q": {
"type": "string",
"description": "Search term, e.g. \"palestine\", \"iran\"."
},
"limit": {
"type": "integer",
"maximum": 100,
"minimum": 1,
"description": "Max results (default 10)."
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/news.asha/asha-news"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/news.asha/asha-news"}) over MCP.
palestine_evidence_search ~361 tokenspalestine_search_archive ~211 tokensasha_subscribe_newsletter ~200 tokenspalestine_evidence_record ~189 tokensasha_blindspot ~184 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fnews.asha%2Fasha-news?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fnews.asha%2Fasha-news?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fnews.asha%2Fasha-news.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fnews.asha%2Fasha-news.svg :target: https://glimind.com/server/mcp-registry%2Fnews.asha%2Fasha-news?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:de8fa1585fcc8f9c…, first seen 2026-10-17, included at leaf 7283 of 78,184. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable news servers · most reliable search servers · most reliable data servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-27 07:56 UTC, the Asha News MCP server is up with a Glimind reliability score of 75/100 (grade B). Over the last 30 days it answered 99.2% of Glimind's liveness checks. It had 28 outages in 90 days, with a median recovery of 7 minutes.
Asha News MCP server advertises 25 tools, including asha_blindspot, asha_breaking, asha_clusters_search, asha_daily_brief, asha_digest.
Point your MCP client at this streamable-http endpoint: https://asha.news/api/v1/mcp
Glimind scanned all 25 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.