# GlobalSource Partners MCP Server (remote · www.globalsourcepartners.com)

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

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `www.globalsourcepartners.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-globalsourcepartners-emerging-markets-research/www.md), [page](https://verifymcp.io/servers/com-globalsourcepartners-emerging-markets-research/www)

## Channel facts

- Endpoint: `https://www.globalsourcepartners.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1094 tokens (~273/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-globalsourcepartners-emerging-markets-resear https://www.globalsourcepartners.com/mcp
```

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-globalsourcepartners-emerging-markets-resear": {
      "type": "remote",
      "url": "https://www.globalsourcepartners.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-globalsourcepartners-emerging-markets-resear --url https://www.globalsourcepartners.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-globalsourcepartners-emerging-markets-resear:
    url: "https://www.globalsourcepartners.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-globalsourcepartners-emerging-markets-resear": {
      "type": "http",
      "url": "https://www.globalsourcepartners.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 70, +4)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 66, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-07-29 (score 66)

First indexed and scored.

## MCP tools (4)

### `search_research_entities` (~153 tokens)

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.

Input parameters:

- `limit` (integer): Maximum number of results to return. Minimum 1, maximum 50, default 10.
- `query` (string, required): The entity name or approximate entity reference to search for.

Output parameters:

- `limit` (integer): The maximum number of matching research entities requested.
- `queried_name` (string): The normalized version of the query used to search for research entities.
- `results` (array): The matching research entities, ordered by match confidence.
- `total_results_count` (integer): The total number of matching research entities found before applying the result limit.

### `read_research_author` (~105 tokens)

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.

Input parameters:

- `author_uuid` (string, required): The stable UUID of the research author to read. Use an author_uuid returned by another research tool.

Output parameters:

- `author_biography_html` (string|null): The research author's biography as HTML, if available.
- `author_name` (string): The display name of the research author.
- `author_profile_url` (string): The URL where this research author's profile can be viewed.
- `author_sectors` (array): The visible sectors associated with this research author.
- `author_short_biography` (string|null): A short biography or role summary for the research author, if available.
- `author_uuid` (string): The stable UUID of the research author.

### `search_research_posts` (~447 tokens)

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.

Input parameters:

- `count_total_results` (boolean): Whether to include the total number of matching posts. Use false unless the total count is specifically needed. Calculating the total count may increase response time for large result sets.
- `cursor` (string): Pagination cursor returned by a previous response. Use this to retrieve the next page of results.
- `limit` (integer): Maximum number of posts to return. Minimum 1, maximum 50, default 25.
- `order` (string): Sort results by publication time. Use 'published_descending' for newest first or 'published_ascending' for oldest first. Default is published_descending.
- `published_after` (string): Only return posts published after this date and time (ISO 8601 format).
- `published_before` (string): Only return posts published before this date and time (ISO 8601 format).
- `research_entity_uuids` (array, required): One or more research entity UUIDs to search against. This field is required. At least one research entity UUID must be supplied. Do not pass entity names. If the user provides entity names rather…

Output parameters:

- `limit` (integer): The maximum number of research posts requested.
- `next_cursor` (string|null): An opaque pagination cursor. Supply this value in a subsequent request to retrieve the next page of results. Clients should not attempt to interpret or modify the cursor value. If this field is null,…
- `order` (string): The sort order applied to the results.
- `published_after` (string): The effective lower publication timestamp used for the search. If no lower publication date filter was supplied, this defaults to the earliest date from which research is available.
- `published_before` (string): The effective upper publication timestamp used for the search. If no upper publication date filter was supplied, this defaults to the current date and time.
- `research_entities` (array): The research entities used to filter the search results.
- `results` (array): The research posts matching the supplied research entities and filters, ordered according to the requested sort order.
- `total_results_count` (integer|null): The total number of matching research posts before pagination was applied. Returned only when count_total_results was requested with true; otherwise null.

### `read_research_post` (~120 tokens)

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.

Input parameters:

- `post_uuid` (string, required): The stable UUID of the research post to read. Use a post_uuid returned by search_research_posts.

Output parameters:

- `post_authors` (array): The authors of this research post.
- `post_body_html` (string): The HTML body available for this research post. This may be full post content or teaser content depending on the MCP user's permissions.
- `post_published` (string): The publication timestamp of the research post in ISO 8601 format.
- `post_sectors` (array): The sectors associated with this research post. Only clients who are permissioned for these sectors can access the full version of this post; other clients will receive teaser content.
- `post_snippet_notice` (string|null): A notice shown when the returned body contains only teaser or snippet content instead of the full research post. Null when the MCP user can view the full post.
- `post_title` (string): The title of the research post.
- `post_type` (string): The type of research post, e.g., 'Report', 'In Brief', 'Presentation', etc.
- `post_updated` (string): The most recent update timestamp of the research post in ISO 8601 format.
- `post_url` (string): The URL where this research post can be viewed. This may be a full post URL or teaser URL depending on the MCP user's permissions.
- `post_uuid` (string): The stable UUID of the research post.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-globalsourcepartners-emerging-markets-research/www#diagnostics

## Score history

- 2026-08-03: 72
- 2026-08-02: 71
- 2026-08-01: 71
- 2026-07-31: 70
- 2026-07-30: 66
- 2026-07-29: 66

## Links

- Remote endpoint: https://www.globalsourcepartners.com/mcp
- Website: https://www.globalsourcepartners.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-globalsourcepartners-emerging-markets-research/www/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-globalsourcepartners-emerging-markets-research/www/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-globalsourcepartners-emerging-markets-research/www