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.

Conference Partner

REMOTE · WWW.MYHUIBAN.COM

Conference & journal CFP deadlines, CCF/ICORE/QUALIS rankings, acceptance rates, research fields.

Available components

0 this week 90 Trust /100

Last scanned (19 hours ago)

Scores higher than 98% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Education and Research

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 Security89
Transport & Reachability100
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1878 tokens (~234/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 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 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
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

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

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.

  • 29 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 201 → 234 ▼ functional
    • Server version: 0.8.0 → 0.9.0 functional
    • “list_conferences” added an optional parameter “field” cosmetic
    • “search_conferences” reworded the description of “ccf_rank” cosmetic
    • “search_conferences” reworded the description of “core_rank” cosmetic
    • “search_conferences” reworded the description of “qualis_rank” cosmetic
    • “search_journals” reworded the description of “ccf_rank” cosmetic
  • 29 Sept 26 0
    • “list_journals” added an optional parameter “field” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 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
  • 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
  • 1 Sept 26 0
    • “list_conferences” reworded the description of “ranking” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 26 Aug 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
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 18 Aug 26 0
    • Tool “get_statistics” rewrote its description, which is the text the model reads security
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 5 Nov 2026 · Probed https://www.myhuiban.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=myhuiban.com CN=WE1,O=Google Trust Services,C=US 25 Oct 2026 23 Jan 2027 ECDSA 256 ECDSA-SHA256 510ff943b6d34d4b0eefc2a00fbd968b
SANs: myhuiban.com, *.myhuiban.com
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 insecure

Validation of www.myhuiban.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
myhuiban.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="huiban-mcp"

Bearer realm="huiban-mcp"
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

Protected resource metadata

Retrieved No
Problem No resource metadata

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.myhuiban.com/mcp Verified 200
http (plaintext) http://www.myhuiban.com/mcp HTTPS enforced 301 https://www.myhuiban.com/mcp
MCP tools · 8 exposed · ~1,448 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
get_conference ~106

Get full details of a conference by id: basics, CFP text, acceptance-rate history, edition history, structured ratings and comments, related conferences/journals. REQUIRES CREDENTIALS: Authorization: Bearer <credential> (free API key from https://www.myhuiban.com/account/api-keys, or a JWT from POST /api/login). responses link to the Conference Partner detail_page, not the venue's external website.

NameTypeReqDescription
idintegeryesConference id

No output schema declared.

No examples provided.

get_journal ~101

Get full details of a journal by id: basics, CFP text, special issues, structured ratings and comments, related journals/conferences. REQUIRES CREDENTIALS: Authorization: Bearer <credential> (free API key from https://www.myhuiban.com/account/api-keys, or a JWT from POST /api/login). responses link to the Conference Partner detail_page, not the venue's external website.

NameTypeReqDescription
idintegeryesJournal id

No output schema declared.

No examples provided.

get_researcher ~110

Get a researcher's public profile by id: name, institution, auto-generated research-interest summary, CV, tracked/attended conferences and tracked journals. REQUIRES CREDENTIALS: Authorization: Bearer <credential> (free API key from https://www.myhuiban.com/account/api-keys, or a JWT from POST /api/login). Never includes contact details; by id only — there is no researcher search or enumeration.

NameTypeReqDescription
idintegeryesResearcher (user) id

No output schema declared.

No examples provided.

get_statistics ~85

Site-level public statistics: conference/journal totals, how many conferences have an open call for papers, upcoming deadlines by month, open CFPs by CCF / ICORE / QUALIS tier, conference country and research-field distributions, journal impact-factor, CCF-tier, publisher and research-field distributions. Research-field keys are the same slugs the search tools accept in their field parameter.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_conferences ~298

Browse conference lists and rankings (open CFPs, ranked venues with a call open now, popularity, most competitive, etc.), paginated. No keyword filtering — use search_conferences for that.

NameTypeReqDescription
fieldstring–Research field filter. Only for ranking=cfp, past_cfp, upcoming, past or cp_index (e.g. ranking=cfp with field=ai = AI conferences still accepting papers, soonest deadline first)
pageinteger–Page number, 1-based
per_pageinteger–Items per page, max 100
rankingstringyescfp=open calls for papers; past_cfp=expired calls; ccf/core/qualis=venues in that tier whose submission deadline has not passed (for the whole tier catalogue use search_conferences with ccf_rank / co…

No output schema declared.

No examples provided.

list_journals ~168

Browse journal lists and rankings (special-issue CFPs, CCF, highest impact factor, popularity, all), paginated. No keyword filtering — use search_journals for that.

NameTypeReqDescription
fieldstring–Research field filter. Only for ranking=cfp or ranking=all (e.g. ranking=cfp with field=network = network journals with an open special issue, soonest deadline first)
pageinteger–Page number, 1-based
per_pageinteger–Items per page, max 100
rankingstringyescfp=special-issue calls for papers; ccf=CCF list; highest_if=highest impact factor; most_viewed/most_tracked=popularity; all=all journals

No output schema declared.

No examples provided.

search_conferences ~374

Search academic conferences. Every parameter is optional — combine any of keyword, CCF/CORE/QUALIS rank, research field and submission/conference date ranges. Filter-only queries work fine (e.g. field=ai plus a submission-deadline window, no keyword). Returns a paginated list.

NameTypeReqDescription
ccf_rankstring–CCF rank: A, B or C. Comma-separate to match any of several (A,B,C = any CCF rank). Venues with no CCF rank have ccf_rank "" in the results
conference_date_endstring–Conference date until (YYYY-MM-DD)
conference_date_startstring–Conference date from (YYYY-MM-DD)
core_rankstring–ICORE rank: A*, A, B or C. Comma-separate to match any of several (A*,A)
fieldstring–Research field (e.g. ai, security, systems, ee, energy) - see the field enum for the full list
pageinteger–Page number, 1-based
per_pageinteger–Items per page, max 100
qualis_rankstring–QUALIS rank: A1, A2, B1..B5. Comma-separate to match any of several (A1,A2)
querystring–Keyword, matched against short/full name
submission_date_endstring–Submission deadline until (YYYY-MM-DD)
submission_date_startstring–Submission deadline from (YYYY-MM-DD)
updated_sincestring–Incremental sync: only venues changed on/after this date (YYYY-MM-DD). Day granularity. Use the updated_at field of the results as your next checkpoint.

No output schema declared.

No examples provided.

search_journals ~206

Search academic journals. Every parameter is optional — combine any of keyword, CCF rank, research field and ISSN. Returns a paginated list.

NameTypeReqDescription
ccf_rankstring–CCF rank: A, B or C. Comma-separate to match any of several (A,B,C = any CCF rank)
fieldstring–Research field (e.g. ai, security, systems, ee, energy) - see the field enum for the full list
issnstring–ISSN (fuzzy match)
pageinteger–Page number, 1-based
per_pageinteger–Items per page, max 100
querystring–Keyword, matched against short/full name
updated_sincestring–Incremental sync: only venues changed on/after this date (YYYY-MM-DD). Day granularity. Use the updated_at field of the results as your next checkpoint.

No output schema declared.

No examples provided.

Install

How do I install the Conference Partner MCP server?

Conference Partner is a hosted endpoint at https://www.myhuiban.com/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 · www.myhuiban.com

# add to Claude Code
claude mcp add --transport http com-myhuiban-www-conference-partner 'https://www.myhuiban.com/mcp'
Common questions

What is the Conference Partner MCP server?

Conference Partner is an MCP server listed in the public MCP registry as com.myhuiban.www/conference-partner. Conference & journal CFP deadlines, CCF/ICORE/QUALIS rankings, acceptance rates, research fields. This page covers its hosted endpoint (https://www.myhuiban.com/mcp).

Is the Conference Partner MCP server safe to use?

Conference Partner scores 90 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 Conference Partner MCP server expose?

Conference Partner exposes 8 tools: search_conferences, search_journals, list_conferences, list_journals, get_conference, and 3 more. Their descriptions and schemas cost roughly 1,448 tokens of context every time the server is loaded.

Does the Conference Partner MCP server require authentication?

Yes. Conference Partner asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Conference Partner MCP server still maintained?

Conference Partner 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.

What did VerifyMCP test on the Conference Partner MCP server?

VerifyMCP ran 13 checks on Conference Partner, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.