GlobalSource Partners MCP Server
REMOTE · WWW.GLOBALSOURCEPARTNERS.COM
Search expert emerging-markets research on economics, politics, policy and sovereign risk.
Available components
Last scanned (16 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Education and Research
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1168 tokens (~292/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Sept 26 0
- “search_research_posts” reworded the description of “published_after” cosmetic
- “search_research_posts” reworded the description of “published_before” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 28 Aug 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://www.globalsourcepartners.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.globalsourcepartners.com | CN=YR2,O=Let's Encrypt,C=US | 13 Sept 2026 | 12 Dec 2026 | RSA 2048 | SHA256-RSA | 6803ef0e28c1194798be96fcb7a311959c2 |
| SANs: www.globalsourcepartners.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.globalsourcepartners.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| globalsourcepartners.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.globalsourcepartners.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.globalsourcepartners.com/mcp | HTTPS enforced | 301 | https://www.globalsourcepartners.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
read_research_author ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| author_uuid | string | yes | The stable UUID of the research author to read. Use an author_uuid returned by another research tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| author_biography_html | string|null | yes | The research author's biography as HTML, if available. |
| author_name | string | yes | The display name of the research author. |
| author_profile_url | string | yes | The URL where this research author's profile can be viewed. |
| author_sectors | array | yes | The visible sectors associated with this research author. |
| author_short_biography | string|null | yes | A short biography or role summary for the research author, if available. |
| author_uuid | string | yes | The stable UUID of the research author. |
No examples provided.
read_research_post ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| post_uuid | string | yes | The stable UUID of the research post to read. Use a post_uuid returned by search_research_posts. |
| Name | Type | Req | Description |
|---|---|---|---|
| post_authors | array | yes | The authors of this research post. |
| post_body_html | string | yes | 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 | yes | The publication timestamp of the research post in ISO 8601 format. |
| post_sectors | array | yes | 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 | yes | 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 | yes | The title of the research post. |
| post_type | string | yes | The type of research post, e.g., 'Report', 'In Brief', 'Presentation', etc. |
| post_updated | string | yes | The most recent update timestamp of the research post in ISO 8601 format. |
| post_url | string | yes | 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 | yes | The stable UUID of the research post. |
No examples provided.
search_research_entities ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results to return. Minimum 1, maximum 50, default 10. |
| query | string | yes | The entity name or approximate entity reference to search for. |
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | yes | The maximum number of matching research entities requested. |
| queried_name | string | yes | The normalized version of the query used to search for research entities. |
| results | array | yes | The matching research entities, ordered by match confidence. |
| total_results_count | integer | yes | The total number of matching research entities found before applying the result limit. |
No examples provided.
search_research_posts ~521
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 timestamp. Provide a complete RFC 3339 timestamp including a timezone, for example 2026-08-01T00:00:00Z. Date-only values such as 2026-08-01 are not accepted. |
| published_before | string | – | Only return posts published before this timestamp. Provide a complete RFC 3339 timestamp including a timezone, for example 2026-08-01T00:00:00Z. Date-only values such as 2026-08-01 are not accepted. |
| research_entity_uuids | array | yes | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | yes | The maximum number of research posts requested. |
| next_cursor | string|null | yes | 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 | yes | The sort order applied to the results. |
| published_after | string | yes | 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 | yes | 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 | yes | The research entities used to filter the search results. |
| results | array | yes | The research posts matching the supplied research entities and filters, ordered according to the requested sort order. |
| total_results_count | integer|null | yes | The total number of matching research posts before pagination was applied. Returned only when count_total_results was requested with true; otherwise null. |
No examples provided.
How do I install the GlobalSource Partners MCP Server server?
GlobalSource Partners MCP Server is a hosted endpoint at https://www.globalsourcepartners.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.globalsourcepartners.com
claude mcp add --transport http com-globalsourcepartners-emerging-markets-resear 'https://www.globalsourcepartners.com/mcp'
What is the GlobalSource Partners MCP Server server?
GlobalSource Partners MCP Server is listed in the public MCP registry as com.globalsourcepartners/emerging-markets-research. Search expert emerging-markets research on economics, politics, policy and sovereign risk. This page covers its hosted endpoint (https://www.globalsourcepartners.com/mcp).
Is the GlobalSource Partners MCP Server server safe to use?
GlobalSource Partners MCP Server scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the GlobalSource Partners MCP Server server expose?
GlobalSource Partners MCP Server exposes 4 tools: search_research_entities, read_research_author, search_research_posts, read_research_post. Their descriptions and schemas cost roughly 899 tokens of context every time the server is loaded.
Does the GlobalSource Partners MCP Server server require authentication?
No. We connected to GlobalSource Partners MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the GlobalSource Partners MCP Server server still maintained?
GlobalSource Partners MCP Server is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the GlobalSource Partners MCP Server server?
VerifyMCP ran 13 checks on GlobalSource Partners MCP Server, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.