CyberQuant MCP Server

MCP server for CyberQuant data sharing platform that enables AI assistants to directly query and analyze financial data using CSV output for token efficiency.

Current trust snapshot

Canonical machine links

Own this MCP?

Claim ownership, prove control with a GitHub, DNS, HTTP, MCP metadata, or email-domain challenge, revalidate now, publish a badge, configure monitoring, and unlock a verified server profile.

1. Claim

unclaimed

Start owner claim

with GitHub, DNS, or HTTP challenge instructions.

2. Revalidate

POST /v1/servers/slb-cn/cyberquant-mcp/revalidate

Verified owners get priority queueing after proof succeeds.

3. Badge

Verified by MCP Verify - score n/a - last checked never

Claim this badge to verify ownership and add evidence.

4. Monitor

Pick plan + alerts

Continuous Verify plan is self-serve: choose a tier, configure watches, add authenticated validation, trigger revalidation, and use the badge.

Paid profile

Verified Server Profile

Add verified publisher identity, security metadata, evidence packs, badge customization, and owner analytics without buying a better score.

[![Verified by MCP Verify](https://verify.sentinelsignal.io/badge/slb-cn/cyberquant-mcp.svg)](https://verify.sentinelsignal.io/servers/slb-cn/cyberquant-mcp)

MCP TrustOps

TrustOps turns this report into operational controls: freshness SLAs, authenticated validation, semantic benchmarks, policy exports, alert subscriptions, badges, cost/compliance metadata, and runtime routing. Fresh trusted index decisions stay separate from long-tail inventory so stale scores do not masquerade as current evidence.

MCP Runtime hosting

Verify Hosted MCP turns a trusted server report into a managed remote MCP endpoint with GitHub deployment provenance, sandbox policy, encrypted secrets, release history, rollback, and audit/usage events.

Production readiness class

Evidence confidence

Recommended for

Client compatibility verdicts

Client compatibility only means the server shape can work with a client. Production trust decision and write-action publishing are evaluated separately so a client-compatible server can still be blocked for production.

Why compatibility is limited by client

Verdict traces

Publishability policy profiles

Compatibility fixtures

Authenticated validation sessions

Public validation is free. Authenticated validation is paid and proves scoped behavior, write-action safeguards, and authenticated tool execution.

Public server reputation

Incident & change feed

No incidents or changes recorded yet.

Capabilities

• OAuth: ✕
• DCR/CIMD: ✕
• Prompts: ✕
• Homepage: https://glama.ai/mcp/servers/j6kvdk6rz4
• Docs: none
• Support: https://github.com/slb-cn/cyberquant-mcp
• Icon: none
• Remote endpoint: https://glama.ai/mcp/servers/j6kvdk6rz4
• Server card: none

Security posture

Agent Commerce & Payment Readiness - Beta

Beta assessment. Verify separates commerce-adjacent context from observed payment execution. Usage, billing, pricing, card, wallet, or meter terms alone do not make a server payment-capable. This is not a certification of safety, compliance, or fraud prevention.

Warnings

No commerce-specific warnings generated.

Evidence

Recommended operator fixes

• No commerce-specific fixes suggested.

Tool capability & risk inventory

No tool inventory available from the latest validation run.

Write-action governance

Status detail: No write-action governance evidence is available yet.

Action-controls diff

Need at least two validation runs before diffing action controls.

Why this score?

Algorithmic score breakdown

No score components recorded yet.

Compatibility profiles

Connector URL: https://glama.ai/mcp/servers/j6kvdk6rz4
# No OAuth metadata detected.
# Server: slb-cn/cyberquant-mcp

{
  "mcpServers": {
    "cyberquant-mcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://glama.ai/mcp/servers/j6kvdk6rz4"]
    }
  }
}

smithery mcp add "https://glama.ai/mcp/servers/j6kvdk6rz4"

curl -sS https://glama.ai/mcp/servers/j6kvdk6rz4 -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Actionable remediation

Point loss breakdown

No current score penalties are recorded.

Validation diff

Need at least two validation runs before diffing changes.

Tool snapshot diff & changelog

Need at least two validation runs before building a tool changelog.

Connector replay

Transport compliance drilldown

Issues: none

Request association

Utility coverage

Benchmark tasks

Registry & provenance divergence

Active alerts

• Server has never been validated (high)
  No live validation evidence exists yet for this entry.

Aliases & registry graph

Alias consolidation

Install snippets

Connector URL: https://glama.ai/mcp/servers/j6kvdk6rz4
# No OAuth metadata detected.
# Server: slb-cn/cyberquant-mcp

{
  "mcpServers": {
    "cyberquant-mcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://glama.ai/mcp/servers/j6kvdk6rz4"]
    }
  }
}

smithery mcp add "https://glama.ai/mcp/servers/j6kvdk6rz4"

curl -sS https://glama.ai/mcp/servers/j6kvdk6rz4 -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Agent access & tool surface

Claims & monitoring

Alert routing

Maintainer analytics

Maintainer response quality

Maintainer annotations

No maintainer annotations have been recorded yet.

Maintainer rebuttals & expected behavior

No maintainer rebuttals or expected-behavior overrides are recorded yet.

Latest validation evidence

No validation run available yet.

Raw evidence view

{
  "checks": {},
  "failures": {},
  "remote_url": "https://glama.ai/mcp/servers/j6kvdk6rz4",
  "server_card_payload": null,
  "server_identifier": "slb-cn/cyberquant-mcp"
}

Known versions

• No versions recorded.

Validation history

Validation timeline

No validation timeline is available yet.

Recent validation runs