GlobalSource Partners MCP Server

com.globalsourcepartners/emerging-markets-research

answering

GlobalSource Partners MCP Server is answering right now. Last checked 13 min ago. It exposes 4 tools.

Search expert emerging-markets research on economics, politics, policy and sovereign risk.

Uptime history 41 hours of history · worst hour 75%

41 hours agonow

98.9%

Uptime 24h

90 of 91 checks

Tools

read from the server

451 ms

Response time

average over 24h

open, no key

Access

streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add emerging-markets-research --transport http https://www.globalsourcepartners.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "emerging-markets-research": {
      "url": "https://www.globalsourcepartners.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.emerging-markets-research]
url = "https://www.globalsourcepartners.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "emerging-markets-research": {
      "url": "https://www.globalsourcepartners.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "emerging-markets-research": {
      "url": "https://www.globalsourcepartners.com/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

research

read_research_author

Read a single research author by author UUID. Use this tool when a user wants profile details for a specific research author returned by another research tool. The response includes author metadata, biography fields, profile URL, and visible sectors associated with the author. Missing, inactive, non-author, and hidden-sector-only authors return a generic not-found error.

read_research_post

Read a single published research post by post UUID. Use this tool after calling search_research_posts and selecting the most relevant result. The response includes post metadata, authors, sectors, body HTML, and a URL. Depending on the authenticated MCP user's permissions, the body HTML and URL may expose either the full research post or teaser content. Missing, unpublished, and hidden-sector posts return a generic not-found error.

search_research_entities

Search research entities by name or approximate name. Use this tool whenever a user refers to an entity by name and a research entity UUID is needed. Results are ranked by match quality and include the research entity UUIDs required by other research tools. When multiple results are returned, review the entity name, description, match type, match confidence, and available research count to determine the most appropriate entity before using its entity_uuid in another tool. This tool only searches existing research entities and does not create or modify data.

search_research_posts

Search published research posts associated with one or more research entities. This tool requires research entity UUIDs. If only entity names are known, first call search_research_entities to obtain candidate research entities and their UUIDs. Use only entity_uuid values copied exactly from search_research_entities results. Never infer, guess, construct, or transform UUIDs from entity names. Use this tool only after selecting the most appropriate research entity from the search_research_entities results. Examples: - To find research about "United States", first call search_research_entities with "United States", review the returned matches, select the most appropriate entity, and then call this tool with the selected entity_uuid. - To find recent research about multiple entities, pass all selected entity_uuid values in research_entity_uuids. - To retrieve the next page of results, pass the previous response's next_cursor as cursor. Results can be filtered by publication date and retrieved using cursor-based pagination.

Endpoints

URL	Transport	State	Latency	Checked
https://www.globalsourcepartners.com/mcp	streamable-http	answering	427 ms	13 min ago

GlobalSource Partners MCP Server — questions

Answers built from our own checks of this server.

What can GlobalSource Partners MCP Server do?

It exposes 4 tools, read directly from the server on our last check. Among them: read_research_author, read_research_post, search_research_entities, search_research_posts. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is GlobalSource Partners MCP Server working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 91 checks got a reply (98.9%), average response time 451 ms. The bar chart above shows every period we have measured.

How do I connect GlobalSource Partners MCP Server?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does GlobalSource Partners MCP Server need an API key?

No. GlobalSource Partners MCP Server completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is GlobalSource Partners MCP Server?

It answers our handshake in 451 ms on average, which is faster than 27% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.