mcp-registry/com.compamir/news · v1.0.0
As of 2026-10-26 19:00 UTC, the Compamir News MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Search structured COMPAMIR news in Japanese and English, with links to source reports.
Point your MCP client at this streamable-http endpoint: https://api.compamir.com/mcp
8 parameter(s) across 3 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 →
3 of 3 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 →
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. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.compamir%2Fnews/fixes
{
"name": "get_event",
"description": "Get a single COMPAMIR event by id, including its source links and conflict note if any.",
"inputSchema": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string"
},
"lang": {
"enum": [
"jp",
"en",
"both"
],
"type": "string",
"default": "both"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "list_conflicts",
"description": "List events where reporting diverges across sources (the signature Conflict Watch). Each item includes a plain-language note on what differs and the source links.",
"inputSchema": {
"type": "object",
"properties": {
"limit": {
"type": "integer",
"default": 20,
"maximum": 50,
"minimum": 1
},
"since": {
"type": "string",
"description": "occurred_at >= (YYYY-MM-DD)"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "search_events",
"description": "Search COMPAMIR structured news events. Events are deduplicated across multiple sources into single items, with reporting conflicts flagged, in Japanese and English. Each result carries source links. Note: produced by automated AI processing, not exhaustive human verification — cite the provided source links.",
"inputSchema": {
"type": "object",
"properties": {
"lang": {
"enum": [
"jp",
"en",
"both"
],
"type": "string",
"default": "both"
},
"genre": {
"enum": [
"Politics",
"Business",
"Tech",
"Global"
],
"type": "string"
},
"limit": {
"type": "integer",
"default": 20,
"maximum": 50,
"minimum": 1
},
"query": {
"type": "string",
"description": "Free-text title search"
},
"since": {
"type": "string",
"description": "occurred_at >= (YYYY-MM-DD)"
},
"until": {
"type": "string",
"description": "occurred_at <= (YYYY-MM-DD)"
},
"region": {
"enum": [
"Asia",
"Europe",
"Americas",
"Middle East",
"Africa",
"Oceania",
"Global"
],
"type": "string"
},
"status": {
"enum": [
"confirmed",
"speculative",
"disputed"
],
"type": "string"
}
}
},
"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/com.compamir/news"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.compamir/news"}) over MCP.
search_events ~275 tokenslist_conflicts ~108 tokensget_event ~78 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%2Fcom.compamir%2Fnews?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.compamir%2Fnews?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.compamir%2Fnews.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.compamir%2Fnews.svg :target: https://glimind.com/server/mcp-registry%2Fcom.compamir%2Fnews?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:56b2e9575ad73179…, first seen 2026-10-17, included at leaf 11920 of 74,914. Version history · verify what your client received.
Compare: most reliable retrieval servers · most reliable search 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-26 19:00 UTC, the Compamir News MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Compamir News MCP server advertises 3 tools, including get_event, list_conflicts, search_events.
Point your MCP client at this streamable-http endpoint: https://api.compamir.com/mcp
Glimind scanned all 3 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.