MAA Intelligence
REMOTE · MEDICALAIALLIANCE.ORG
Korean listed medical AI, biotech and device companies linked to MFDS and FDA regulatory records.
Available components
Last scanned (4 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 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 Security63
- 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 5 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 825 tokens (~165/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 2 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- Stability: 0.97 → pass security
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Aug 26 0
- Tool “get_company” rewrote its description, which is the text the model reads security
- Schema quality: 668 → 825 ▼ functional
- New tool “get_stock_quote” functional
- 28 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 27 Aug 26 0
First indexed and scored.
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 5 Nov 2026 · Probed https://medicalaialliance.org/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=medicalaialliance.org | CN=YR2,O=Let's Encrypt,C=US | 24 Sept 2026 | 23 Dec 2026 | RSA 2048 | SHA256-RSA | 641ac4915494a2bc83418c840b451ad3231 |
| SANs: medicalaialliance.org | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of medicalaialliance.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 725, 26974 | 8, 8 | Verified |
| medicalaialliance.org. | 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 |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline' https://api.fontshare.com https://cdn.jsdelivr.net; img-src 'self' data: blob: https:; font-src 'self' data: https://api.fontshare.com https://cdn.jsdelivr.net; connect-src 'self' https://*.supabase.co; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://medicalaialliance.org/api/mcp | Verified | 200 | |
| http (plaintext) | http://medicalaialliance.org/api/mcp | HTTPS enforced | 308 | https://medicalaialliance.org/api/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 ~179
Full profile of one company: business overview, products, R&D, financials for the last three years, a breakdown of its regulatory record (MFDS device and drug approvals, clinical trial authorisations, Innovative Medical Device and Orphan Drug designations, US FDA 510(k) clearances and FDA drug approvals), global clinical trials (ClinicalTrials.gov, updated weekly), research publications (PubMed, updated daily), patents (KIPRIS, updated monthly) and key exchange disclosures (KRX KIND — contracts, capital changes, market actions, updated daily). For the live stock quote use get_stock_quote.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Company name, KRX ticker (e.g. '328130'), or index slug (e.g. 'lunit-328130'). |
| language | string | – | Language for narrative fields. Default en. |
No output schema declared.
No examples provided.
get_stock_quote ~92
Live stock quote for one indexed company: price (KRW), daily change, market cap, PER, PBR, 52-week range. Real-time market data — call again for current values; do not treat a quoted price as durable.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Company name, KRX ticker (e.g. '328130'), or index slug (e.g. 'lunit-328130'). |
No output schema declared.
No examples provided.
industry_overview ~70
Aggregate view of the Korean medical AI and biotech sector as indexed by MAA: company counts by sector, total regulatory records by source, and measured AI visibility (how well these companies' own websites can be read by AI systems). Use this for questions about the sector as a whole rather than one company.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_approvals ~244
Search regulatory records across all indexed companies. Sources: Korea MFDS (device approvals, drug approvals, clinical trial authorisations, Innovative Medical Device designations, Orphan Drug designations) and the US FDA (510(k)). Use agency='MFDS_INNO' for Innovative Medical Device designations — only 136 exist nationwide, so holding one is a strong signal. Use agency='MFDS_TRIAL' for pipeline.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | FDA=US 510(k) · MFDS=Korean device approval · MFDS_DRUG=Korean drug approval · MFDS_TRIAL=clinical trial authorisation (pipeline, not an approval) · MFDS_INNO=Innovative Medical Device designation ·… |
| company | string | – | Restrict to one company (name or ticker). |
| limit | number | – | Max results (default 25, cap 50). |
| query | string | – | Keyword in the product name, e.g. 'stroke', '심전도', 'CAR-T'. |
| since | string | – | Only records decided on or after this date (YYYY-MM-DD). |
No output schema declared.
No examples provided.
search_companies ~170
Search Korean listed medical AI, biotech, medical device, pharma and healthcare infrastructure companies. Use this to find companies by name, business keyword, sector, or stock exchange. Returns a summary line per company. Call get_company afterwards for full detail on a specific one.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Sector filter. |
| has_fda | boolean | – | Only companies holding US FDA 510(k) clearances. |
| limit | number | – | Max results (default 20, cap 50). |
| member_only | boolean | – | Only MAA member companies. |
| query | string | – | Company name (Korean or English) or business keyword, e.g. 'Lunit', '루닛', 'colorectal cancer diagnostics', 'CAR-T'. Omit to list by category alone. |
No output schema declared.
No examples provided.
How do I install the MAA Intelligence MCP server?
MAA Intelligence is a hosted endpoint at https://medicalaialliance.org/api/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 · medicalaialliance.org
claude mcp add --transport http org-medicalaialliance-intelligence 'https://medicalaialliance.org/api/mcp'
What is the MAA Intelligence MCP server?
MAA Intelligence is an MCP server listed in the public MCP registry as org.medicalaialliance/intelligence. Korean listed medical AI, biotech and device companies linked to MFDS and FDA regulatory records. This page covers its hosted endpoint (https://medicalaialliance.org/api/mcp).
Is the MAA Intelligence MCP server safe to use?
MAA Intelligence scores 78 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 MAA Intelligence MCP server expose?
MAA Intelligence exposes 5 tools: search_companies, get_company, get_stock_quote, search_approvals, industry_overview. Their descriptions and schemas cost roughly 755 tokens of context every time the server is loaded.
Does the MAA Intelligence MCP server require authentication?
No. We connected to MAA Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MAA Intelligence MCP server still maintained?
MAA Intelligence is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.