# Chinng AI-Agent Portal (remote · portal.chinng-lab-srv.dev)

Search news, vulnerability advisories, government documents, and agent-ready websites.

- Trust score: 59/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `portal.chinng-lab-srv.dev`: 59/100 (this document), [markdown](https://verifymcp.io/servers/dev-chinng-lab-srv-portal/portal.md), [page](https://verifymcp.io/servers/dev-chinng-lab-srv-portal/portal)

## Channel facts

- Endpoint: `https://portal.chinng-lab-srv.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.29.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 49/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1986 tokens (~248/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Chinng AI-Agent Portal MCP server?

Chinng AI-Agent Portal is a hosted endpoint at https://portal.chinng-lab-srv.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-chinng-lab-srv-portal 'https://portal.chinng-lab-srv.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-chinng-lab-srv-portal": {
      "url": "https://portal.chinng-lab-srv.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-chinng-lab-srv-portal": {
      "type": "http",
      "url": "https://portal.chinng-lab-srv.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-chinng-lab-srv-portal]
url = "https://portal.chinng-lab-srv.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-chinng-lab-srv-portal": {
      "type": "remote",
      "url": "https://portal.chinng-lab-srv.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-chinng-lab-srv-portal --url 'https://portal.chinng-lab-srv.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-chinng-lab-srv-portal:
    url: "https://portal.chinng-lab-srv.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-chinng-lab-srv-portal": {
      "Transport": "http",
      "Url": "https://portal.chinng-lab-srv.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-chinng-lab-srv-portal -t streamable-http -u 'https://portal.chinng-lab-srv.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-chinng-lab-srv-portal": {
      "type": "http",
      "url": "https://portal.chinng-lab-srv.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 57, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 56, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-14 (score 55)

First indexed and scored.

## MCP tools (8)

### `portal_list` (~343 tokens)

List item metadata (no body, token-light).

Two content families are distinguished by category prefix:
  \- news articles: category="news" (or narrower, e.g. "news/world")
  \- CVE/vulnerability advisories: category="security" (or "security/library" / "security/os" / "security/app")
Omit category to list both together.

Args:
    category: category prefix match. e.g. "news" matches all news/*, "security" matches all CVE, "news/world" narrows it
    status: filter by ingested/processed/enriched/published (all if omitted)
    source: feed identifier. e.g. "ghost-chinng-lab"
    lang: original language. e.g. "ja"
    since: lower bound on published_at (ISO 8601. e.g. "2026-07-01")
    until: upper bound on published_at (ISO 8601)
    q: title substring search
    limit: number of results (default 20, max 100)
    offset: paging start position

Returns:
    {total, count, limit, offset, items[]} — each item includes summary/summary_en/tags/
    entities/related_auto/license_note plus summary_omitted_reason, redistribution,
    keywords_en, entities_en, topics_en and numeric_facts, but **never the body**.

Input parameters:

- `category`
- `lang`
- `limit`
- `offset` (integer)
- `q`
- `since`
- `source`
- `status`
- `until`

### `portal_search` (~412 tokens)

BM25 full-text search over items (no body returned, token-light).

Ranked by weighted BM25 (SQLite FTS5) over the title, the original-language summary,
the English summary, sentence-free English search signals and — for items whose
license permits redistribution — the body.
Japanese text is morphologically segmented at index time, so Japanese queries match
words that a substring search would miss. Results carry score (0-1), rank and a
snippet of the matching passage. Use portal_get to read a matched item's body.

Args:
    q: keyword(s). space-separated terms are ANDed. e.g. "openai gpt"
    category: category prefix match. e.g. "news" or "security"
    status: filter by ingested/processed/enriched/published (all if omitted)
    source: feed identifier. e.g. "ghost-chinng-lab"
    lang: original language. e.g. "ja"
    limit: number of results (default 20, max 100)
    offset: paging start position
    mode: "bm25" (default, relevance-ranked) or "index" (substring match, newest first)

Returns:
    {total, count, limit, offset, query, mode, total_is_capped, items[]} — same
    license-gated item shape as portal_list (summary/summary_en and snippet omitted
    for link-only, omission reason and search signals retained), **never the body**.
    In bm25 mode each item adds score / rank /
    snippet, and total is an estimate capped for cost. If the BM25 index is not
    usable the call transparently falls back to mode "index" and reports why in
    degraded_reason.

Input parameters:

- `category`
- `lang`
- `limit`
- `mode` (string)
- `offset` (integer)
- `q` (string, required)
- `source`
- `status`

### `portal_list_government` (~151 tokens)

List official government documents without their Markdown bodies.

Use country (for example "us", "jp", or "eu") and source to narrow results. Federal
Register document types include "Rule", "Proposed Rule", and "Notice"; Japanese
RSS sources use their configured update class as document_type. EU sources cover
EUR-Lex legislation and case-law (document_number carries the CELEX number) and
European Commission press releases.
Call portal_get for a selected id when its full portal record is needed.

Input parameters:

- `country`
- `document_type`
- `limit`
- `offset` (integer)
- `since`
- `source`
- `until`

### `portal_changes` (~80 tokens)

Return only articles whose existing content_hash changed and were republished.

New article creation and asynchronous enrichment changes are excluded. Save next_cursor
and pass it on the next poll for stable, token-light incremental retrieval.

Input parameters:

- `category`
- `cursor`
- `lang`
- `limit`
- `since`
- `source`

### `portal_list_agent_surfaces` (~356 tokens)

List scanned websites by their AI-agent readiness (the Agent-Readiness directory).

A separate content family from news/CVE: each entry is a domain we actively scanned for
agent-facing surfaces across five categories (Discoverability / Content / Bot Access
Control / API-Auth-MCP-Skill / Commerce). Checks are graded like the Cloudflare
Agent-Ready scanner: each category yields a percentage, and the overall score (0-100,
Commerce excluded as informational) maps to Level 0-3 (0 Unprepared / 1 Agent-Curious /
2 Agent-Aware / 3 Agent-Native). Only scanned domains with results are listed.

Args:
    level: filter to a single readiness level (0-3)
    min_score: only surfaces with overall score (0-100) >= this value
    discovered_via: candidate source filter. e.g. "tranco" / "majestic" / "manual"
    sort: "score" (default, highest readiness first) or "recent" (recently changed first, for level-up tracking)
    limit: number of results (default 20, max 100)
    offset: paging start position

Returns:
    {total, count, limit, offset, items[]} — each item has domain, score (0-100), level,
    level_label, categories[] (per-category pct + pass/fail breakdown), checks[] (every
    check with its HTTP status), llms_txt_url, discovered_via and timestamps.

Input parameters:

- `discovered_via`
- `level`
- `limit`
- `min_score`
- `offset` (integer)
- `sort` (string)

### `portal_get_agent_surface` (~152 tokens)

Fetch one website's full Agent-Readiness assessment by domain.

Args:
    domain: the site's domain (e.g. "example.com"). Normalized (scheme/path/case stripped).

Returns:
    domain, score (0-100 overall), level, level_label, categories[] (per-category pct with
    passed/failed/neutral check ids), checks[] (every verified check with its HTTP status
    and byte size), llms_txt_url / llms_full_txt_url, discovered_via and
    first_seen_at / checked_at / updated_at timestamps.
    Returns {error: "not_found", domain} if the domain has not been scanned.

Input parameters:

- `domain` (string, required)

### `portal_get` (~163 tokens)

Fetch a full article by id.

The body/summary returned is gated by license_note:
  \- full (default): body included
  \- summary-only: no body, summary (summary/summary_en) present
  \- link-only: link and metadata only, no summary or body

Args:
    id: article id (e.g. "news-20260702-4c769f")
    include_body: false to return metadata only, omitting the body (even when license is full)

Returns:
    The article's full metadata + body (body_policy states which policy was applied).
    Returns {error: "not_found", id} if the article does not exist.

Input parameters:

- `id` (string, required)
- `include_body` (boolean)

### `portal_popular` (~95 tokens)

Return the most retrieved portal pages.

Args:
    window: rolling window such as "24h", "7d", "30d" or "90d".
    category: optional category prefix such as "news" or "security".
    limit: number of results (default 10, max 100 on the analytics service).

Input parameters:

- `category`
- `limit` (integer)
- `window` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-chinng-lab-srv-portal/portal#diagnostics

## Score history

- 2026-11-21: 59
- 2026-11-20: 58
- 2026-11-19: 58
- 2026-11-18: 57
- 2026-11-17: 57
- 2026-11-16: 56
- 2026-11-15: 56
- 2026-11-14: 55

## Common questions

### What is the Chinng AI-Agent Portal MCP server?

Chinng AI-Agent Portal is an MCP server listed in the public MCP registry as dev.chinng-lab-srv/portal. Search news, vulnerability advisories, government documents, and agent-ready websites. This page covers its hosted endpoint (https://portal.chinng-lab-srv.dev/mcp).

### Is the Chinng AI-Agent Portal MCP server safe to use?

Chinng AI-Agent Portal scores 59 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Chinng AI-Agent Portal MCP server expose?

Chinng AI-Agent Portal exposes 8 tools: portal_list, portal_search, portal_list_government, portal_changes, portal_list_agent_surfaces, and 3 more. Their descriptions and schemas cost roughly 1,752 tokens of context every time the server is loaded.

### Does the Chinng AI-Agent Portal MCP server require authentication?

No. We connected to Chinng AI-Agent Portal without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Chinng AI-Agent Portal MCP server still maintained?

Chinng AI-Agent Portal is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Chinng AI-Agent Portal MCP server?

VerifyMCP ran 11 checks on Chinng AI-Agent Portal, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Chinng AI-Agent Portal: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://portal.chinng-lab-srv.dev/mcp
- Website: https://portal.chinng-lab-srv.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-chinng-lab-srv-portal/portal.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-chinng-lab-srv-portal/portal/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-chinng-lab-srv-portal/portal.json
- HTML version of this page: https://verifymcp.io/servers/dev-chinng-lab-srv-portal/portal
