Skip to content
ResearchCal logo

ResearchCal MCP server

Which MCP servers are ResearchCal's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-24

← Back to ResearchCal

Whose server it is
  • Registry namecom.researchcal/researchcalverified in the MCP registry

The registry name sits under researchcal.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-24
  • Stateanswerschecked 2026-10-24
  • Tools4
  • Server calls itselfResearchCal
  • Protocol version2025-06-18

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 137 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.

Once connected

  • For "find calls for papers in your research field", the likely first call is list_upcoming_deadlines.
  • Parameters are untyped or undescribed in 1 of 4 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 9, the first on 2026-10-24
  • INITE MCP score99 of 100answers 100 · definitions 96 · context 100 · connects 100
  • Answered100% of days9 of 9 daily checks
  • Median first answer124 ms
  • Space in an agent's context≈ 686 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsA · 96 of 100
  • Typed results4 of 4 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 1 of 4

What an agent can do with it

  • can do · find calls for papers in your research field
  • not sure · add conference and workshop dates to your calendar
  • not sure · check submission deadlines beside teaching and meetings

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers4 tools · read 2026-10-24
  • search

    Search upcoming academic conferences, workshops and calls for papers by words in the title, organizer, location or topic. Returns at most 10 events with their ResearchCal page and official source URL.

  • fetch

    Get the public facts of one event by its id from search: dates, location, public deadlines, official and source URLs, and the public calendar feeds that contain it.

  • list_upcoming_deadlines

    List open and announced public submission deadlines in date order. Filter by research field, category key, and date range. Returns at most 20 deadlines per call; use next_offset for the next page.

  • list_calendars

    List the public ResearchCal calendar feeds (ICS) with their subscribe URLs, optionally for one research field.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "researchcal": {
      "type": "http",
      "url": "https://mcp.researchcal.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http researchcal https://mcp.researchcal.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.researchcal.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.