Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Chinng AI-Agent Portal

REMOTE · PORTAL.CHINNG-LAB-SRV.DEV

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

+4 this week 59 Trust /100

Last scanned (16 hours ago)

Scores higher than 44% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security49
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Unverified
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability56
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (11)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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 in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +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.

  • 15 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 14 Nov 26 55

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://portal.chinng-lab-srv.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=chinng-lab-srv.dev CN=WE1,O=Google Trust Services,C=US 2 Oct 2026 31 Dec 2026 ECDSA 256 ECDSA-SHA256 4bf13ff902da1a3513869455a2673835
SANs: chinng-lab-srv.dev, *.chinng-lab-srv.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of portal.chinng-lab-srv.dev. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
chinng-lab-srv.dev. DS published 2371 13 Verified
portal.chinng-lab-srv.dev. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://portal.chinng-lab-srv.dev/mcp Verified 200
http (plaintext) http://portal.chinng-lab-srv.dev/mcp Inconclusive 406
MCP tools · 8 exposed · ~1,752 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
portal_changes ~80

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.

NameTypeReqDescription
category–––
cursor–––
lang–––
limit–––
since–––
source–––

Structured output declared, but exposes no named fields.

No examples provided.

portal_get ~163

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.

NameTypeReqDescription
idstringyes–
include_bodyboolean––

Structured output declared, but exposes no named fields.

No examples provided.

portal_get_agent_surface ~152

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.

NameTypeReqDescription
domainstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

portal_list ~343

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**.

NameTypeReqDescription
category–––
lang–––
limit–––
offsetinteger––
q–––
since–––
source–––
status–––
until–––

Structured output declared, but exposes no named fields.

No examples provided.

portal_list_agent_surfaces ~356

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.

NameTypeReqDescription
discovered_via–––
level–––
limit–––
min_score–––
offsetinteger––
sortstring––

Structured output declared, but exposes no named fields.

No examples provided.

portal_list_government ~151

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.

NameTypeReqDescription
country–––
document_type–––
limit–––
offsetinteger––
since–––
source–––
until–––

Structured output declared, but exposes no named fields.

No examples provided.

portal_popular ~95

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).

NameTypeReqDescription
category–––
limitinteger––
windowstring––

Structured output declared, but exposes no named fields.

No examples provided.

portal_search ~412

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.

NameTypeReqDescription
category–––
lang–––
limit–––
modestring––
offsetinteger––
qstringyes–
source–––
status–––

Structured output declared, but exposes no named fields.

No examples provided.

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.

remote · portal.chinng-lab-srv.dev

# add to Claude Code
claude mcp add --transport http dev-chinng-lab-srv-portal 'https://portal.chinng-lab-srv.dev/mcp'
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.