GateCore Marketplace
REMOTE · MCP.GATECOREAI.COM · SCANNED OCT 7
Procure governed AI capabilities: machine-readable price, scope, trust, gateway-delegation terms.
Available components
Recent critical change
Authorization (10 Sept 2026). See the changelog before you install this server.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (procure). See how to fix → View diagnostics → Fail
- 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 Usability56
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 432 tokens (~54/item across 8 items; 8 tools + 0 resources), lean.Pass
- 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 Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
How do I install the GateCore Marketplace MCP server?
GateCore Marketplace is a hosted endpoint at https://mcp.gatecoreai.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 · mcp.gatecoreai.com
claude mcp add --transport http com-gatecoreai-marketplace 'https://mcp.gatecoreai.com/mcp'
{
"mcpServers": {
"com-gatecoreai-marketplace": {
"url": "https://mcp.gatecoreai.com/mcp"
}
}
} {
"servers": {
"com-gatecoreai-marketplace": {
"type": "http",
"url": "https://mcp.gatecoreai.com/mcp"
}
}
} [mcp_servers.com-gatecoreai-marketplace] url = "https://mcp.gatecoreai.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-gatecoreai-marketplace": {
"type": "remote",
"url": "https://mcp.gatecoreai.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-gatecoreai-marketplace --url 'https://mcp.gatecoreai.com/mcp' --transport streamable-http
mcp_servers:
com-gatecoreai-marketplace:
url: "https://mcp.gatecoreai.com/mcp" {
"McpServers": {
"com-gatecoreai-marketplace": {
"Transport": "http",
"Url": "https://mcp.gatecoreai.com/mcp"
}
}
} assistant mcp add com-gatecoreai-marketplace -t streamable-http -u 'https://mcp.gatecoreai.com/mcp'
{
"mcpServers": {
"com-gatecoreai-marketplace": {
"type": "http",
"url": "https://mcp.gatecoreai.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 30 Sept 26 0
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- 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
- 13 Sept 26 +1
- Stability: 0.97 → pass security
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −7
- Authorization: partial → fail ▼ critical
- New tool “authorize_access”, which the server declares destructive security
- New tool “complete_access”, which the server declares destructive security
- Tool “procure” is now declared destructive security
- Schema quality: 267 → 432 ▼ functional
- New tool “request_listing_access” functional
- “procure” added an optional parameter “procurement_id” cosmetic
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Sept 26 0
- “procure” added an optional parameter “request_id” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
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 8 Oct 2026 · Probed https://mcp.gatecoreai.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.gatecoreai.com | CN=YE2,O=Let's Encrypt,C=US | 9 Aug 2026 | 7 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5a0ef3ab3af1c3a995f2ae103f749fdc839 |
| SANs: mcp.gatecoreai.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.gatecoreai.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| gatecoreai.com. | absent | 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=31536000 |
| content-security-policy | default-src 'none'; frame-ancestors 'none'; base-uri 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.gatecoreai.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.gatecoreai.com/mcp | HTTPS enforced | 308 | https://mcp.gatecoreai.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 →
authorize_access Authorize Governed Access ~59
Authorize signed access to a governed listing. Purpose is forwarded unchanged when present; policy at the gateway decides whether the declared purpose is allowed.
| Name | Type | Req | Description |
|---|---|---|---|
| listing_id | string | yes | – |
| max_price_cents | – | – | – |
| purpose | – | – | – |
No output schema declared.
No examples provided.
complete_access Complete Governed Access ~61
Hash seller output locally, attest completion with the buyer agent key, and return the terminal signed receipt. Seller output itself is never forwarded or returned.
| Name | Type | Req | Description |
|---|---|---|---|
| outcome | string | yes | – |
| seller_output | string | yes | – |
| ticket | object | yes | – |
No output schema declared.
No examples provided.
discover_listings Discover Marketplace Listings ~62
Discover governed GateCore marketplace capabilities with machine-readable pricing, required scopes, and minimum trust terms. Results preserve the marketplace's organic order.
| Name | Type | Req | Description |
|---|---|---|---|
| max_price_cents | – | – | – |
| min_trust | – | – | – |
| query | – | – | – |
| tags | – | – | – |
No output schema declared.
No examples provided.
get_listing Get Listing Details ~45
Fetch one governed marketplace listing and its machine-enforceable contract terms: price, required scopes, minimum trust, target, and data classification.
| Name | Type | Req | Description |
|---|---|---|---|
| listing_id | string | yes | – |
No output schema declared.
No examples provided.
list_procurements List Procurement Decisions ~21
List procurement decisions for the credential tenant in public modes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
procure Request Governed Procurement ~109
Request governed procurement for a listing. In public full mode, identity comes from the MCP access key, trust comes from GateCore's baseline, and the result is a PROCURE, REVIEW, or DENY decision with gateway delegation when eligible.
| Name | Type | Req | Description |
|---|---|---|---|
| listing_id | string | yes | – |
| max_price_cents | – | – | – |
| procurement_id | – | – | – |
| request_id | – | – | – |
| requester_agent_id | string | yes | – |
| requester_trust | number | yes | – |
| scopes | – | – | – |
No output schema declared.
No examples provided.
request_listing_access Request Listing Access ~39
Submit an idempotent listing-access request for the credential's tenant and agent.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | – |
| listing_id | string | yes | – |
No output schema declared.
No examples provided.
submit_lead Submit Consumer Lead ~36
Submit a consented consumer lead to a supported published listing.
| Name | Type | Req | Description |
|---|---|---|---|
| lead | object | yes | – |
| listing_id | string | yes | – |
No output schema declared.
No examples provided.
What is the GateCore Marketplace MCP server?
GateCore Marketplace is an MCP server listed in the public MCP registry as com.gatecoreai/marketplace. Procure governed AI capabilities: machine-readable price, scope, trust, gateway-delegation terms. This page covers its hosted endpoint (https://mcp.gatecoreai.com/mcp).
Is the GateCore Marketplace MCP server safe to use?
GateCore Marketplace scores 75 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 GateCore Marketplace MCP server expose?
GateCore Marketplace exposes 8 tools: discover_listings, get_listing, procure, authorize_access, complete_access, and 3 more. Their descriptions and schemas cost roughly 432 tokens of context every time the server is loaded.
Does the GateCore Marketplace MCP server require authentication?
No. We connected to GateCore Marketplace without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the GateCore Marketplace MCP server still maintained?
GateCore Marketplace is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.