Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Marketcaper MCP

REMOTE · MARKETCAPER.COM · SCANNED SEP 21

Cited market comparisons and heatmap images for AI agents.

Available components

+4 this week 83 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 853 tokens (~170/item across 5 items; 4 tools + 1 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 Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Install

How do I install the Marketcaper MCP server?

Marketcaper MCP is a hosted endpoint at https://marketcaper.com/api/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 · marketcaper.com

# add to Claude Code
claude mcp add --transport http com-marketcaper-mcp 'https://marketcaper.com/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-marketcaper-mcp": {
      "url": "https://marketcaper.com/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-marketcaper-mcp": {
      "type": "http",
      "url": "https://marketcaper.com/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-marketcaper-mcp]
url = "https://marketcaper.com/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-marketcaper-mcp": {
      "type": "remote",
      "url": "https://marketcaper.com/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-marketcaper-mcp --url 'https://marketcaper.com/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-marketcaper-mcp:
    url: "https://marketcaper.com/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-marketcaper-mcp": {
      "Transport": "http",
      "Url": "https://marketcaper.com/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-marketcaper-mcp -t streamable-http -u 'https://marketcaper.com/api/mcp'
// mcp.json
{
  "mcpServers": {
    "com-marketcaper-mcp": {
      "type": "http",
      "url": "https://marketcaper.com/api/mcp"
    }
  }
}

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

Changelog

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.

  • 21 Sept 26 +1

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

  • 19 Sept 26 +1

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

  • 17 Sept 26 +1

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

  • 15 Sept 26 +1

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

  • 12 Sept 26 +1

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

  • 10 Sept 26 +1

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

  • 8 Sept 26 +1

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

  • 6 Sept 26 +1

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

Diagnostics

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 21 Sept 2026 · Probed https://marketcaper.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=marketcaper.com CN=YE1,O=Let's Encrypt,C=US 10 Sept 2026 9 Dec 2026 ECDSA 256 ECDSA-SHA384 5b66a36657f617bb135577cfff81e05031d
SANs: *.marketcaper.com, marketcaper.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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 marketcaper.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
marketcaper.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
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://marketcaper.com/api/mcp Verified 200
http (plaintext) http://marketcaper.com/api/mcp HTTPS enforced 301 https://marketcaper.com/api/mcp
MCP tools · 4 exposed · ~683 tokens

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 →

Tool Tokens
compare_assets ~203

Compare two Marketcaper assets and return the live what-if market cap scenario, canonical pair URL, and optional hosted image URL. Hosted images are PNG, generated on demand, share a 10 images/day/IP limit, and may require a longer timeout than the MCP JSON call. Always cite the returned source_url when using the data.

NameTypeReqDescription
asset_astringyesCanonical slug, ticker/code, or supported alias for asset A.
asset_bstringyesCanonical slug, ticker/code, or supported alias for asset B.
include_imagebooleanWhen true, include a hosted Marketcaper export image URL for the pair. Hosted images are generated on demand as PNG, share a 10 images/day/IP limit, and clients should allow up to 20 seconds for the…
response_formatstringOptional output format. Use "json" when a client needs machine-parseable text blocks, especially for Claude artifacts.

No output schema declared.

No examples provided.

compare_assets_pack ~124

Compare two Marketcaper assets and return the same cited comparison data plus a ready-to-publish short post and share payload with the hosted comparison image URL. Always cite the returned source_url when using the data.

NameTypeReqDescription
asset_astringyesCanonical slug, ticker/code, or supported alias for asset A.
asset_bstringyesCanonical slug, ticker/code, or supported alias for asset B.
response_formatstringOptional output format. Use "json" when a client needs machine-parseable text blocks, especially for Claude artifacts.

No output schema declared.

No examples provided.

get_asset_snapshot ~85

Resolve one Marketcaper asset and return its live market cap snapshot. Always cite the returned source_url when using the data.

NameTypeReqDescription
assetstringyesCanonical slug, ticker/code, or supported alias for one asset.
response_formatstringOptional output format. Use "json" when a client needs machine-parseable text blocks, especially for Claude artifacts.

No output schema declared.

No examples provided.

get_stock_heatmap ~271

Return a current Marketcaper stock heatmap summary plus a hosted dark-theme PNG image URL. Supports US or global universes, classic or bubble views, optional sector/category filtering, and capped summary rows. Hosted images share a 10 images/day/IP limit. This is not a bulk feed extraction tool.

NameTypeReqDescription
categorystringOptional sector/category name or slug, such as "Financial Services" or "communication-services". When supplied, the image includes only that category.
metricstringOptional heatmap sizing metric: "marketCap", "volume", or "turnover". Defaults to "marketCap".
response_formatstringOptional output format. Use "json" when a client needs machine-parseable text blocks, especially for Claude artifacts.
timeframestringOptional performance timeframe: "1H", "4H", "1D", "1W", "1M", or "1Y". Defaults to "1D".
universestringOptional stock universe. Use "us" for US top stocks or "global" for global top stocks. Defaults to "us".
viewstringyesRequired heatmap image view. Use "classic" for the sector tile map or "bubble" for the bubble stock heatmap.

No output schema declared.

No examples provided.

Common questions

What is the Marketcaper MCP server?

Marketcaper MCP is listed in the public MCP registry as com.marketcaper/mcp. Cited market comparisons and heatmap images for AI agents. This page covers its hosted endpoint (https://marketcaper.com/api/mcp).

Is the Marketcaper MCP server safe to use?

Marketcaper MCP scores 83 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 Marketcaper MCP server expose?

Marketcaper MCP exposes 4 tools: get_asset_snapshot, compare_assets, compare_assets_pack, get_stock_heatmap. Their descriptions and schemas cost roughly 683 tokens of context every time the server is loaded.

Does the Marketcaper MCP server require authentication?

No. We connected to Marketcaper MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Marketcaper MCP server still maintained?

Marketcaper MCP is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.