BioAI 日知
REMOTE · BIOAI-RIZHI.PAGES.DEV
Read-only AI biopharma news, research records, companies, and source status from BioAI 日知.
Available components
Last scanned (3 hours ago)
Scores higher than 68% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Health and Science
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 700 tokens (~140/item across 5 items; 5 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 Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage77
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 19% of tool parameters carry a description.Partial
- 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 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.
- 14 Oct 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.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 10. That category is still filling its 30-day observation window: 1 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.
- 10 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
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 24 Oct 2026 · Probed https://bioai-rizhi.pages.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bioai-rizhi.pages.dev | CN=YE1,O=Let's Encrypt,C=US | 8 Oct 2026 | 6 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 590d86c7f88e911e32bd2f37d584b5705c3 |
| SANs: *.bioai-rizhi.pages.dev, bioai-rizhi.pages.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bioai-rizhi.pages.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| pages.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bioai-rizhi.pages.dev/mcp | Verified | 200 | |
| http (plaintext) | http://bioai-rizhi.pages.dev/mcp | HTTPS enforced | 301 | https://bioai-rizhi.pages.dev/mcp |
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 →
get_company Read a BioAI company profile ~75
Read one company directory profile with name/alias provenance, public source verification status and up to 20 published events. Official-website fields in directory metadata are not automatically verified sources.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Optional presentation language. Omit for legacy copy. Source text remains in its original language. |
| slug | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| coverage_note | string | yes | – |
| data | object | yes | – |
| interpretation_note | string | – | – |
| language | object | yes | – |
No examples provided.
get_resource Read a BioAI resource ~91
Read one stored source record by UUID, or an editor-reviewed event when kind='event'. Returns up to 6000 characters of stored source text, original URLs, publication status and provenance. It never retrieves arbitrary external URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| kind | string | – | – |
| language | string | – | Optional presentation language. Omit for legacy copy. Source text remains in its original language. |
| Name | Type | Req | Description |
|---|---|---|---|
| coverage_note | string | yes | – |
| data | object | yes | – |
| interpretation_note | string | – | – |
| language | object | yes | – |
No examples provided.
get_source_status Inspect source coverage and topics ~106
Inspect a bounded page of publicly visible source verification/collection status and the current topic definitions. last_success_at reports successful source collection, not when every source was last updated. No credentials, configuration or internal error logs are returned.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| language | string | – | Optional presentation language. Omit for legacy copy. Source text remains in its original language. |
| limit | integer | – | – |
| offset | integer | – | – |
| query | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| coverage_note | string | yes | – |
| data | object | yes | – |
| interpretation_note | string | – | – |
| language | object | yes | – |
No examples provided.
search_companies Search the BioAI company directory ~117
Find directory companies by current or historical name, topic, track or region. Topic matches and directory metadata are discovery aids, not a complete market census or source verification certificate.
| Name | Type | Req | Description |
|---|---|---|---|
| history | boolean | – | – |
| language | string | – | Optional presentation language. Omit for legacy copy. Source text remains in its original language. |
| limit | integer | – | – |
| offset | integer | – | – |
| query | string | – | – |
| region_group | string | – | – |
| topic | string | – | – |
| track | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| coverage_note | string | yes | – |
| interpretation_note | string | – | – |
| items | array | yes | – |
| language | object | yes | – |
| limit | integer | yes | – |
| offset | integer | yes | – |
| total | integer | yes | – |
No examples provided.
search_resources Search BioAI resources ~136
Search stored public research abstracts and industry source records by keywords, topic, academic/industry category and time window. days=0 searches all stored dates. This tool searches source records; it does not claim they are editor-reviewed news.
| Name | Type | Req | Description |
|---|---|---|---|
| academic | string | – | – |
| company | string | – | – |
| days | integer | – | – |
| journal_tier | string | – | – |
| language | string | – | Optional presentation language. Omit for legacy copy. Source text remains in its original language. |
| limit | integer | – | – |
| offset | integer | – | – |
| query | string | – | – |
| topic | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| coverage_note | string | yes | – |
| interpretation_note | string | – | – |
| items | array | yes | – |
| language | object | yes | – |
| limit | integer | yes | – |
| offset | integer | yes | – |
| total | integer | yes | – |
No examples provided.
How do I install the BioAI 日知 MCP server?
BioAI 日知 is a hosted endpoint at https://bioai-rizhi.pages.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 · bioai-rizhi.pages.dev
claude mcp add --transport http minsyang-bioai-rizhi 'https://bioai-rizhi.pages.dev/mcp'
What is the BioAI 日知 MCP server?
BioAI 日知 is an MCP server listed in the public MCP registry as io.github.MInsYang/bioai-rizhi. Read-only AI biopharma news, research records, companies, and source status from BioAI 日知. This page covers its hosted endpoint (https://bioai-rizhi.pages.dev/mcp).
Is the BioAI 日知 MCP server safe to use?
BioAI 日知 scores 75 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 BioAI 日知 MCP server expose?
BioAI 日知 exposes 5 tools: search_resources, get_resource, search_companies, get_company, get_source_status. Their descriptions and schemas cost roughly 525 tokens of context every time the server is loaded.
Does the BioAI 日知 MCP server require authentication?
No. We connected to BioAI 日知 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BioAI 日知 MCP server still maintained?
BioAI 日知 is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.