_ registry / mcp streamable-http · checked 1h ago

huiban-mcp

https://www.myhuiban.com

Registry code: 1f574d69928d15c6

api record

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…

endpoint
https://www.myhuiban.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
198ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 8 tools
3 open 5 never probed 3 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_journals open 3h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "issn": {
      "type": "string",
      "description": "ISSN (fuzzy match)"
    },
    "page": {
      "type": "integer",
      "default": 1,
      "minimum": 1,
      "description": "Page number, 1-based"
    },
    "field": {
      "enum": [
        "ai",
        "vision",
        "nlp",
        "data",
        "network",
        "security",
        "se",
        "systems",
        "theory",
        "hci",
        "graphics",
        "bio",
        "robotics",
        "web",
        "ee",
        "energy",
        "materials",
        "civil",
        "education",
        "management",
        "math"
      ],
      "type": "string",
      "description": "Research field (e.g. ai, security, systems, ee, energy) - see the field enum for the full list"
    },
    "query": {
      "type": "string",
      "description": "Keyword, matched against short/full name"
    },
    "ccf_rank": {
      "enum": [
        "A",
        "B",
        "C"
      ],
      "type": "string",
      "description": "CCF rank"
    },
    "per_page": {
      "type": "integer",
      "default": 10,
      "maximum": 100,
      "minimum": 1,
      "description": "Items per page, max 100"
    },
    "updated_since": {
      "type": "string",
      "description": "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."
    }
  }
}
    arguments 66 lines
  • get_statistics open 3h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • search_conferences open 3h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "page": {
      "type": "integer",
      "default": 1,
      "minimum": 1,
      "description": "Page number, 1-based"
    },
    "field": {
      "enum": [
        "ai",
        "vision",
        "nlp",
        "data",
        "network",
        "security",
        "se",
        "systems",
        "theory",
        "hci",
        "graphics",
        "bio",
        "robotics",
        "web",
        "ee",
        "energy",
        "materials",
        "civil",
        "education",
        "management",
        "math"
      ],
      "type": "string",
      "description": "Research field (e.g. ai, security, systems, ee, energy) - see the field enum for the full list"
    },
    "query": {
      "type": "string",
      "description": "Keyword, matched against short/full name"
    },
    "ccf_rank": {
      "enum": [
        "A",
        "B",
        "C"
      ],
      "type": "string",
      "description": "CCF rank"
    },
    "per_page": {
      "type": "integer",
      "default": 10,
      "maximum": 100,
      "minimum": 1,
      "description": "Items per page, max 100"
    },
    "core_rank": {
      "enum": [
        "A*",
        "A",
        "B",
        "C"
      ],
      "type": "string",
      "description": "CORE rank"
    },
    "qualis_rank": {
      "type": "string",
      "description": "QUALIS rank"
    },
    "updated_since": {
      "type": "string",
      "description": "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."
    },
    "conference_date_end": {
      "type": "string",
      "description": "Conference date until (YYYY-MM-DD)"
    },
    "submission_date_end": {
      "type": "string",
      "description": "Submission deadline until (YYYY-MM-DD)"
    },
    "conference_date_start": {
      "type": "string",
      "description": "Conference date from (YYYY-MM-DD)"
    },
    "submission_date_start": {
      "type": "string",
      "description": "Submission deadline from (YYYY-MM-DD)"
    }
  }
}
    arguments 92 lines
  • get_conference unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "integer",
      "description": "Conference id"
    }
  }
}
    arguments 12 lines
  • list_conferences unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ranking"
  ],
  "properties": {
    "page": {
      "type": "integer",
      "default": 1,
      "minimum": 1,
      "description": "Page number, 1-based"
    },
    "ranking": {
      "enum": [
        "cfp",
        "past_cfp",
        "ccf",
        "core",
        "qualis",
        "most_viewed",
        "most_tracked",
        "most_attended",
        "most_competitive",
        "upcoming",
        "past",
        "trending",
        "cp_index"
      ],
      "type": "string",
      "description": "cfp=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 / core_rank / qualis_rank); cp_index=every conference ordered by the Conference Partner Index, our own 0-100 score - the only list here that covers the whole catalogue instead of the fifth of it that CCF / ICORE / QUALIS rate; each row carries cp_index with its confidence, and https://www.myhuiban.com/ranking has the method; most_viewed/most_tracked/most_attended=popularity; most_competitive=lowest acceptance rate; upcoming/past=by conference date; trending=most viewed in the last 30 days"
    },
    "per_page": {
      "type": "integer",
      "default": 20,
      "maximum": 100,
      "minimum": 1,
      "description": "Items per page, max 100"
    }
  }
}
    arguments 40 lines
  • get_journal unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "integer",
      "description": "Journal id"
    }
  }
}
    arguments 12 lines
  • get_researcher unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "integer",
      "description": "Researcher (user) id"
    }
  }
}
    arguments 12 lines
  • list_journals unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "ranking"
  ],
  "properties": {
    "page": {
      "type": "integer",
      "default": 1,
      "minimum": 1,
      "description": "Page number, 1-based"
    },
    "ranking": {
      "enum": [
        "cfp",
        "ccf",
        "highest_if",
        "most_viewed",
        "most_tracked",
        "all"
      ],
      "type": "string",
      "description": "cfp=special-issue calls for papers; ccf=CCF list; highest_if=highest impact factor; most_viewed/most_tracked=popularity; all=all journals"
    },
    "per_page": {
      "type": "integer",
      "default": 20,
      "maximum": 100,
      "minimum": 1,
      "description": "Items per page, max 100"
    }
  }
}
    arguments 33 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/1f574d69928d15c6/badge.svg)](https://brick.blue/agent/1f574d69928d15c6)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.