Skip to content
External endpointresponds

Conference Partner

Academic conference & journal CFP deadlines, CCF/ICORE/QUALIS rankings, acceptance rates.

Endpoint URL
https://www.myhuiban.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:08 AM UTC
Check
MCP initialize · 8s limit
Latency
353 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
com.myhuiban.www/conference-partner

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
huiban-mcp
Version
0.8.0
Capability keys
tools, prompts
Tool names
search_conferences, search_journals, list_conferences, list_journals, get_conference, get_journal, get_researcher, get_statistics
Instructions excerpt

Academic conference and journal data from Conference Partner (myhuiban.com). Use search_conferences / search_journals for keyword search; list_conferences / list_journals to browse curated lists (ranking parameter); get_conference / get_journal for full detail by id; get_statistics for site-level stats; get_researcher for a researcher's public profile by id (no search/enumeration of researchers). Every tool has a REST twin under /api/* returning identical payloads. Rank fields: ccf_rank (A/B/C), core_rank (A*/A/B/C). Search tools also accept a research-field filter (field parameter) and updated_since for incremental sync (day resolution; checkpoint on the updated_at field). Access: search_conferences, search_journals, list_conferences, list_journals and get_statistics need NO credentials — call them directly (rate-limited per client IP). The detail tools get_conference / get_journal / get_researcher require a free-account credential sent as an Authorization: Bearer <credential> reque

Reported Aug 17, 2026, 05:08 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 290ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 718ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 333ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 353ms