Skip to content

MCP servers › org.clinx › clinx

MCP server · registry snapshot 2026-11-17 · last tested 2026-11-17

clinx MCP server

Registry name org.clinx/clinx

ClinX open data: 340B and health centers — the publisher's title

by clinx.org · domain (the registry's namespace rule)repository owner on GitHub: VVillBerchtold (personal account)Source ↗Website ↗

Read-only public data on the 340B drug program and federally funded health centers. No sign-in. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-11-17version 0.3.3JavaScriptstreamable HTTP17 tools

Summary

org.clinx/clinx is a remote MCP server listed in the official MCP registry at version 0.3.3, under the namespace of the domain clinx.org. Its linked repository is github.com/VVillBerchtold/clinx-mcp; GitHub reports its owner as VVillBerchtold, a personal account. On 2026-11-17 ProtocolProbe connected to it in read-only mode and read its inventory: 17 tools, 0 resources and 0 prompts.

Record checks

4 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Repository
public
Tools
17
Last tested
2026-11-17

Tool list size

7,093 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (17 tools). Counted with Anthropic's token counter on 2026-11-17, from the tool list we read on 2026-11-17. Median across 28,560 counted servers: 2,657 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-17 (clinx.org), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (0.3.3).

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-17
Mode
read-only (no tool calls)
Latest version
0.3.3, published 2026-11-17 (registry, as of the 2026-11-17 snapshot)
First listed version
2026-11-17 (earliest version still in the registry; older removed versions would be earlier)
Version history
3 versions listed, all on 2026-11-17; 3 in the 90 days before the 2026-11-17 snapshot.
Most recent 3 versions
  • 0.3.3 · 2026-11-17
  • 0.3.2 · 2026-11-17
  • 0.3.1 · 2026-11-17
(versions still listed in the registry only)
Registry data
snapshot 2026-11-17
Package and repository
checked 2026-11-17
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-16, listed on 2026-11-17 with version 0.3.3 (published 2026-11-17).

Source: the official MCP Registry list on 2026-11-16 and on 2026-11-17.

What it is

What does this server offer?

Observed inventory
17tools
0resources
0prompts

None of its 17 tools are described as changing anything. For 17 the reading was uncertain, so no mark is shown.

  • “Search the bills in Congress and the state legislatures that name the federal 340B drug pricing program.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    6 inputs
    • statestring“Two-letter state code such as RI or TX.”
    • textstring“Words to look for in the bill number, title and summary.”
    • stagestring“How far the bill has gone.”
    • rolestring
    • kindstring“What the bill does about 340B.”
    • limitinteger“How many to return (default 20).”
  • “Everything the table holds about one bill, by its bill_id from find_bills: sponsor, stage, latest step in the legislature's own words, the passage that names 340B, links to the official page and text…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • bill_idstringrequired“For example ri-2025-h5634 or us-119-hr4581.”
  • find_laws

    “Search the state laws on the books that name the 340B program (not bills: laws already passed).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs
    • statestring“Two-letter state code such as RI or TX.”
    • kindstring“What the law does, for example contract-pharmacy, payer-nondiscrimination or reporting.”
    • textstring“Words to look for in the citation, title and summary.”
    • limitinteger“How many to return (default 20).”
  • “Everything the table holds about one state law, by its law_id from find_laws: citation, who it binds, what it limits, how it is enforced, dates, the passage that names 340B and the link to the offici…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • law_idstringrequired
  • find_notices

    “Search the rules, proposed rules and notices that federal agencies have published in the Federal Register since January 2025 and that name the 340B program.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    7 inputs
    • textstring“Words to look for in the title, citation, document number, agency, docket and summary.”
    • typestring“The Federal Register's kind of document.”
    • rolestring
    • open_for_commentboolean“True for documents whose last day for public comments has not passed.”
    • fromstring“Published on or after this day, year-month-day.”
    • tostring“Published on or before this day, year-month-day.”
    • limitinteger“How many to return (default 20).”
  • “Everything the table holds about one federal rule or notice, by its notice_id from find_notices (its Federal Register citation, such as 91 FR 48883, also works): the kind of document, the agency that…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • notice_idstringrequired“For example fr-2026-15633.”
  • “Dated events for 340B bills and federal notices: each bill's steps (introduced, sent to committee, votes, signed, vetoed, became law), the days a state's 340B report is due (report due), hearings tha…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    7 inputs
    • statestring“Two-letter state code such as RI or TX, US for Congress, or FED for federal agencies (rules and notices in the Federal Register).”
    • fromstring“First day, year-month-day.”
    • tostring“Last day, year-month-day.”
    • kindstring
    • bill_idstring“Only this bill's dates.”
    • notice_idstring“Only this federal rule's or notice's dates, for example fr-2026-15633.”
    • limitinteger“How many to return (default 20).”
  • reporting_states

    “The states whose law requires 340B reports, grouped by what the public can see: each filer's own report is posted; one state report gives a figure for each named entity; one state report gives totals…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • statestring“Two-letter state code such as RI or TX.”
    • groupstring“One group of states: own-reports, named-in-state-report, state-totals or not-posted-yet.”
  • find_filings

    “Search the reports that covered entities and states have filed about 340B, which the Scorecard holds.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    7 inputs
    • statestring“Two-letter state code such as RI or TX.”
    • yearinteger“The reporting year, such as 2025.”
    • entitystring“Words in the entity's name as filed or in HRSA's name for it (Ohio's workbooks print an ID and no name), or its city, or a 340B ID such as DSH410009.”
    • entity_typestring“For example hospital, health_center or state_total.”
    • record_kindstring“For example filing (an entity's own report), state_report_row (a row a state printed about an entity) or state_report_totals.”
    • formstring“The form's id, as listed by about_the_data.”
    • limitinteger“How many to return (default 20).”
  • “One filed report by its filing_id from find_filings: every line as filed with its label, unit and amount; which claim counts are withheld and why (counts of 1 to 5 are never given); how each figure w…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs, 1 required
    • filing_idstringrequired“For example ri-2025-east-bay-cap.”
    • schedulestring“Only the lines of this schedule, as the line list names it (for example G).”
    • offsetinteger“How many lines to skip, for the next part of a long report (default 0).”
    • limitinteger“How many lines to return (default 100, at most 150).”
  • state_overview

    “A short picture of 340B law and legislation in one state (or US for Congress): how many laws are on the books and of what kind, how many bills name 340B and how far they have gone, which group of rep…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • statestringrequired“Two-letter state code such as RI or TX, US for Congress, or FED for federal agencies (rules and notices in the Federal Register).”
  • find_health_centers

    “Search the federally funded health centers (community health centers that hold a Health Center Program grant from HRSA) whose yearly reports to HRSA are held by ClinX.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs
    • statestring“Two-letter state code such as RI or MA.”
    • textstring“Words to look for in the name (this year's or an earlier one), the city, the key or the grant number.”
    • yearinteger“Only health centers with a report for this year, such as 2025.”
    • limitinteger“How many to return (default 20).”
Show 5 more tools
  • get_health_center_report

    “What one health center reported to HRSA in the Uniform Data System for one year, by its key or grant number from find_health_centers.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    7 inputs, 1 required
    • health_centerstringrequired“The health center's key (for example 010120) or its grant number (for example H80CS00001).”
    • yearinteger“The reporting year.”
    • tablestring“One table of the report, as the answer without a table lists them: for example Table 3A, Table 5, Table 7, Table 9D, Table HIT, ODE or WFC.”
    • linestring“Only this line of the table, as the table lists it (for example L10 or 21a).”
    • textstring“Only the lines whose title holds these words.”
    • offsetinteger“How many lines to skip, for the next part of a long table (default 0).”
    • limitinteger“How many lines to return (default 40).”
  • find_funding_opportunities

    “Search the funding opportunities HRSA (the federal agency that funds health centers) lists on Grants.gov, both forecasts and posted notices.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    6 inputs
    • textstring“Words to look for in the title, the opportunity number and the description.”
    • health_center_programboolean“True for only the opportunities HRSA files under the Health Center Program itself.”
    • statusstring“forecasted: HRSA plans to publish it, dates are estimates.”
    • open_onstring“Only notices posted on or before this day whose applications are due on or after it, year-month-day.”
    • opportunitystring“One opportunity in full, by its number (for example HRSA-27-006) or its Grants.gov id (for example 363419).”
    • limitinteger“How many to return (default 20).”
  • health_center_calendar

    “Dated lines for health center funding: for each HRSA funding opportunity on Grants.gov the day its notice is expected, the day applications are due and the day awards are expected, and for Federal Re…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    6 inputs
    • fromstring“First day, year-month-day.”
    • tostring“Last day, year-month-day.”
    • kindstring
    • sourcestring“grants.gov for funding opportunities, federal register for rules and notices.”
    • textstring“Words to look for in the title.”
    • limitinteger“How many to return (default 20).”
  • shortage_area_changes

    “HRSA's shortage designations (primary care, dental health and mental health professional shortage areas, and medically underserved areas and populations) and its list of health center sites, for one …”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    6 inputs
    • statestring“Two-letter code of a state or territory, such as RI, DC or PR.”
    • showstring“counts (default), or one list of rows: recent, proposed or sites.”
    • kindstring“For recent and proposed, one kind of designation: hpsa-pc primary care, hpsa-dh dental health, hpsa-mh mental health, mua medically underserved areas and popul…”
    • eventstring“For recent, one kind of event.”
    • textstring“For a list, words to look for in the name, county, city or id.”
    • limitinteger“How many to return (default 20).”
  • about_the_dataon 1 other server

    “What ClinX's open data holds (the 340B tables and the health center sets), where each part comes from, when each was last brought up to date or read, what the marks in a health center report mean, th…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-17.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
93% of 70
Tools with a description
100% of 17
Typical description length
454 characters

The tool set

Counted from the listing

Tools
17
Size of the list
about 5,485 tokens for an agent to load (characters ÷ 4)
Naming
16 of 17 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 17 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-17 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://clinx.org/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "clinx": {
      "url": "https://clinx.org/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "clinx": {
      "type": "http",
      "url": "https://clinx.org/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"clinx","type":"http","url":"https://clinx.org/mcp"}'
Claude Code
claude mcp add --transport http clinx https://clinx.org/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "clinx": {
      "type": "streamableHttp",
      "url": "https://clinx.org/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "clinx": {
      "httpUrl": "https://clinx.org/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.clinx]
url = "https://clinx.org/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "clinx": {
      "url": "https://clinx.org/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://clinx.org/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-17. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-17. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-17. Source: read 2026-11-17.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-17. Source: read 2026-11-17.

Own host

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint clinx.org/mcpSession openedmatchesour test · 2026-11-17
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-17
Repository github.com/VVillBerchtold/clinx-mcpOpens publiclymatchesapi.github.com · 2026-11-17

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
org.clinx
GitHub owner
a personal account (VVillBerchtold)
Repository
github.com/VVillBerchtold/clinx-mcp
Stars
0
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-11-17; security policy read from GitHub · 2026-11-17.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-17 (security policy 2026-11-17). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about org.clinx/clinx

Answered from the data above

Who publishes org.clinx/clinx?

The registry ties the namespace org.clinx to the domain clinx.org; only its owner can publish under it. Its linked repository is github.com/VVillBerchtold/clinx-mcp; GitHub reports its owner as VVillBerchtold, a personal account. These are facts from the registry and GitHub, not a rating.

Is org.clinx/clinx safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does org.clinx/clinx need an API key or sign-in?

It opened a session without any credential on 2026-11-17. The registry entry declares no required credential; no declaration is not a guarantee.

Has org.clinx/clinx been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.

Does org.clinx/clinx publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of org.clinx/clinx?

In github.com/VVillBerchtold/clinx-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (no operator permission)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-17
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-11-17, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 814 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 17 tools, 0 resources, 0 prompts.
  4. 2,414 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-17; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
api.github.com · 2026-11-17
Hosting type
registry · 2026-11-17
MCP capability
tools
our test · 2026-11-17
Transport
streamable HTTP
registry · 2026-11-17
Required credentials
none declared
registry · 2026-11-17 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-17
Lifecycle status
registry · 2026-11-17
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: a personal account · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-11-17
Maintenance
api.github.com · 2026-11-17
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-17

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “org.clinx/clinx: MCP server record.” Data checked 2026-11-17. https://protocolprobe.com/mcp/servers/org.clinx/clinx

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/org.clinx/clinx)](https://protocolprobe.com/mcp/servers/org.clinx/clinx)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology